Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
A Practical Look at Creating More Usable Enterprise Customer Journeys
Summary
As practitioners, we are often asked to craft Customer Journeys. It’s not uncommon, however, to wonder how impactful these lovingly researched and designed journeys are for the stakeholders they are meant for. Do they contain the right information for Enterprise stakeholders? Do they convey it in a way that is actually useful for the end user of these journeys? How can we feel more confident in the research that underlies these journeys? This session will explore some of the approaches that the gotomedia team has been using when researching and creating customer journeys in order to make them more successful for enterprise stakeholders.
Key Insights
-
•
Persona and journey artifacts must be designed for digital use to ensure wide sharing and frequent use across an enterprise.
-
•
Journeys and personas should focus on the practitioners and users who engage daily, not just on executives requesting them.
-
•
Overwhelming journeys with excessive detail reduces their usefulness; prioritizing key, valuable information improves adoption.
-
•
Traditional linear journey maps struggle to capture cyclical or repeated user behaviors, requiring thoughtful representation.
-
•
Using card sorting tools like OptimalSort in moderated sessions enables richer, more granular journey data than narrative recall alone.
-
•
Journey data can drive segmentation and persona validation, revealing behavioral patterns unrelated to company size.
-
•
Interactive, progressive disclosure journey maps created with simple tools like Keynote improve clarity and usability.
-
•
Content gap analysis aligned to journeys highlights imbalances in marketing and technical content needed by users.
-
•
Diary studies are often impractical for B2B journey research due to long timelines and participant engagement challenges.
-
•
Journey maps should be revisited every 3-12 months as living documents and collaboratively validated by teams, not only leadership.
Notable Quotes
"Unless it’s designed for digital use it’s not going to get widely shared throughout the organization."
"We want to design for actual users, not just the senior VP or CMO who asks for the persona or journey."
"Too often journeys are these beautiful artifacts that no one actually understands or uses."
"We developed a list of 47 common touchpoints for B2B journeys based on extensive past research."
"Users often re-enter the journey process after a pause, but compress previously taken steps when they come back."
"Journey data allowed us to see that solution scale, not company size, better explained buying behaviors."
"We made our journeys interactive to solve the problem of overwhelming detail in static journey maps."
"Most B2B research is done remotely and online, so we needed a tool that was easy to use without in-person facilitation."
"Diary studies have merit for recall issues but are impractical for long, complex B2B buying processes."
"If a journey map is living and used, revisit it every three months to check if it still reflects reality."
Or choose a question:
More Videos
"Operational success cannot always be quantified through numbers; people are messy and complicated."
Amy ThibodeauOpening Keynote: Process and Ambiguity
October 23, 2019
"The difference between the way people talk about how things are done and how they are actually done reveals unconscious assumptions."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Using the inverted pyramid doesn’t mean dumbing down your findings, it means explaining complex issues clearly."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"You can define your own design process, whether it’s Lean UX, Double Diamond, or something custom."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Setting up a repository as a team of one or two is actually the prime time to establish processes like that."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"About 200,000 digital health products exist, but only 1% of 1% have FDA clearance for accuracy."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"Executives like NPS because it’s a simple, quick-to-understand number, even if they don’t fully grasp its nuances."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"I thought I could skip the architecture step, but I ended up with spaghetti code that broke constantly."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"The COP became the beating heart of our project, enabling quick credibility and community excitement."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
