Research

User Journey Map

A visualisation of the end-to-end experience a user has with a product or service — capturing actions, thoughts, emotions, and pain points across every touchpoint.

#user journey map#journey mapping#touchpoints#experience map#customer journey#pain points#emotions

What is it?

A user journey map is a visual representation of the sequence of steps, touchpoints, thoughts, and emotions a user experiences when trying to accomplish a goal with a product, service, or organisation. It spans the full experience — from initial awareness through to post-use — capturing not just what users do, but what they think and feel at each stage. Journey maps make the invisible architecture of an experience visible, enabling teams to identify friction, disconnects, and emotional low points across the entire user lifecycle.

Why it matters

Products are often designed in silos: the sign-up team designs sign-up, the dashboard team designs the dashboard. Journey maps break down silos by visualising the full experience as a user actually encounters it — across departments, touchpoints, and time. They reveal the moments where hand-offs fail, where emotional frustration peaks, and where opportunities to delight users are being missed. They are also one of the most powerful stakeholder alignment tools in UX — a well-made journey map makes abstract user problems tangible and hard to ignore.

Best Practices

  • Ground journey maps in real user research — interviews, diary studies, and observational research. Assumption-based maps are creative writing, not UX research.
  • Choose a specific persona and a specific scenario. A map for "all users doing anything" is too broad to be actionable. "Sarah (freelance designer) booking her first invoice" is specific and useful.
  • Map the full journey — not just the product interaction. Include pre-product stages (awareness, consideration) and post-product stages (advocacy, return).
  • Capture emotions at each stage using a curve or rating. The emotional journey often tells a different story than the action journey.
  • Identify moments of truth — the high-stakes moments where a positive or negative experience has an outsized impact on the overall relationship.
  • Note touchpoints: which channels and interactions are involved at each stage (email, in-app, support, social)?
  • Make the map collaborative — build it with the cross-functional team (product, engineering, support, marketing) to build shared ownership of the experience.
  • Explicitly mark pain points, opportunities, and open questions. A journey map that only documents the current state without insight is a description, not a research tool.
  • Present the journey map in a visual format that non-UX stakeholders can read and emotionally connect with in under 5 minutes.

Common Mistakes

  • Building journey maps from team assumptions rather than real user research — this produces a map of how the team thinks the product works, not how users actually experience it.
  • Mapping only the happy path. Real users encounter errors, confusion, and competing tasks. Maps that only show ideal states miss where the real problems are.
  • Mapping at such a broad level of abstraction that no actionable insights emerge.
  • Creating a journey map as a one-time deliverable that is never referenced again.
  • Forgetting the emotional layer — a technically complete action map with no emotion data misses half the story.
  • Not connecting journey map findings to design decisions, sprint priorities, or product roadmap items.

Checklist

Research & Theory

Experience Mapping (Adaptive Path / Kalbach, 2016)

Jim Kalbach's foundational work on mapping experiences documents how organisations use journey maps to align teams around the customer experience and identify systemic problems across touchpoints.

Why it's relevant

Journey maps work because they externalise the user experience in a format that creates shared empathy — making user problems visible to people who never interact directly with users.

Peak-End Rule (Kahneman, 1993)

Users judge experiences based on the most intense moment and the final moment, not an average. Journey maps show exactly where peaks — positive and negative — occur.

Why it's relevant

Journey maps are the tool that surfaces peaks and endings. Once visualised, teams can deliberately redesign the most emotionally intense moments.

Service Design and Backstage/Frontstage (Shostack, 1984)

Lynn Shostack's service blueprint methodology (a precursor to journey mapping) distinguished between what users see and experience (frontstage) and what the organisation does to deliver it (backstage).

Why it's relevant

Advanced journey maps incorporate backstage systems and organisational processes — revealing that user pain points often originate in internal process failures, not just interface decisions.

Real-World Examples

Airbnb

Mapped the full host and guest journey — from discovering Airbnb to post-stay review — and discovered that the emotional low point for hosts was the period of uncertainty between listing and first booking. This led to the redesign of host onboarding and dashboard messaging.

Bank of America

Journey mapping the mortgage application process revealed that customers experienced severe anxiety during the "waiting" phases between steps. This drove investment in status-update notifications and a transparent tracking interface.

NHS Digital

Mapped patient journeys from symptom onset to treatment for key conditions, revealing that patients visited an average of 4 digital touchpoints before reaching the right service. The map drove a consolidation of entry points through the NHS App.