Journey Mapping 101: How to Visualise the End-to-End User Experience
A journey map visualises every step a user takes to accomplish a goal — including emotions, pain points, and opportunities. Learn how to create maps that generate genuine team alignment and product direction.
What Is a Journey Map?
A user journey map is a visualisation of a person's process to accomplish a goal — from first awareness through completion, mapped across time with their actions, thoughts, emotions, and pain points. Journey maps are not flowcharts (which model system logic) or wireframes (which model screens) — they model the human experience of interacting with your product or service, including all the moments that happen outside your interface.
Why Journey Maps Matter
- Surface problems that no single team "owns" — the handoffs between design, support, marketing, and engineering where experiences break down.
- Build shared understanding across teams who normally only see their slice of the user journey.
- Identify high-emotion moments (peaks and valleys) that disproportionately shape overall satisfaction.
- Generate a shared vocabulary for talking about user experience across disciplines.
The Seven Components of a Journey Map
- Actor: The specific user persona this map represents. One map, one persona — don't try to generalise across all user types.
- Scenario: The specific goal and context. "Sarah is trying to cancel her subscription" is more useful than "subscription management."
- Journey phases: The high-level stages (Awareness, Research, Decision, Onboarding, Usage, Renewal/Churn).
- Actions: What the user does at each phase — searches Google, opens email, clicks a link, calls support.
- Thoughts: What they're thinking — their questions, assumptions, and uncertainties.
- Emotions: How they feel — plotted on an emotional arc. The emotional valleys are your design opportunities.
- Opportunities: What could make this phase better? What does the team need to do?
Building Your First Journey Map
- Ground it in research: A map built from assumptions is a story, not a tool. Interview users, review support tickets, analyse drop-off data, and run shadowing studies to source the map's content.
- Build collaboratively: Run a journey mapping workshop. Cross-functional participation ensures the map reflects reality, not a single team's perspective.
- Keep it actionable: If every phase shows medium emotions and no clear opportunities, the map is too generic. Push for specificity until clear problem areas emerge.
Key Takeaways
- Journey maps visualise the full human experience, not just the in-app screens.
- Ground maps in research data — assumptions-only maps mislead more than they inform.
- Emotional arcs reveal where experience investment will have the greatest return.
- Collaborative creation builds team empathy more effectively than sharing a finished artefact.
A journey map's seven components: actor, scenario, phases, actions, thoughts, emotions (plotted as an arc), and opportunities.
