Journey mapping.

The journey map

Eight lanes across the timeline.

A journey map is a horizontal timeline with a lane for each of these, so the experience reads end to end rather than touchpoint by touchpoint.

1. 01

   Phase

   The major stages (awareness, consideration, onboarding, activation, retention, advocacy). Let them emerge from the user's actual steps.

2. 02

   Steps

   The specific things the user does within each phase.

3. 03

   Touchpoints

   Where the user interacts with the product, brand, or service: web, app, email, support, social, in-person.

4. 04

   Goals

   What the user is trying to accomplish at each step.

5. 05

   Thoughts

   What is going through the user's mind at that point.

6. 06

   Emotions

   The emotional state, often visualized as a curve across the journey.

7. 07

   Pain points

   Where things go wrong: friction and frustration, named specifically rather than as 'frustrating onboarding'.

8. 08

   Opportunities

   Where the experience could improve, feeding the opportunity map.

Bridges to other skills

The research and testing around the map.

A journey map combines research and data. These cover the discovery that feeds it and the methods that zoom into a single point on it.

• Feeds the map

  ux-research

  Generative research supplies the user understanding a map needs. Run it before mapping; a map built without research reflects internal assumptions.

• A single touchpoint

  usability-testing

  Testing one touchpoint or page for task completion is its job. Journey mapping is the wider context that single touchpoint sits inside.

• Funnel optimization

  cro-optimization

  Optimizing a conversion funnel is a narrower, quantitative exercise. The journey map names where the friction is; CRO tests fixes at a specific step.

Frequently asked questions.

What does journey mapping produce?

Three deliverables. A customer journey map (the user-facing view of the experience across phases, with touchpoints, goals, thoughts, emotions, pain points, and opportunities), a service blueprint (the back-stage view of front-stage actions, back-stage actions, and supporting processes that produce that experience), and a synthesized opportunity map (top friction, untapped opportunities, disconnects, quick wins, and strategic bets). The map and blueprint are inputs; the opportunity map is the output that actually drives decisions.

What goes in a journey map?

A horizontal timeline with a lane for each of: phase, steps, touchpoints, goals, thoughts, emotions (often on a curve), pain points, and opportunities. The phases vary by product type (a SaaS trial journey differs from an ecommerce purchase journey), and they should emerge from the user's actual experience rather than be forced onto it. Vague pain points like 'frustrating onboarding' are a failure; name what specifically goes wrong, when, and why.

What is a service blueprint?

The back-stage view that sits below the journey map. It adds front-stage actions (what employees do that the user sees, like a support chat), back-stage actions (what happens behind the scenes, like order fulfillment), supporting processes (the systems, vendors, and infrastructure), and the line of visibility between front-stage and back-stage. It shows where a customer-facing problem originates in a back-stage failure: a user's 'shipping is slow' experience traces to a vendor handoff. A map without the back-stage layer shows symptoms, not causes.

Where do the inputs come from?

Multiple sources of truth. From users: in-depth interviews walking through a recent real occurrence, diary studies, and surveys for scale. From the business: internal interviews with sales, support, and ops, operational data (funnel data, support ticket categories, churn reasons), and a system inventory of touchpoints. Then cross-validate the user's described experience, the data on their actual behavior, and the team's perception of the experience. These three views often disagree, and the disagreements are themselves findings.

How do I keep a journey map from becoming a dead artifact?

Make it drive decisions rather than sit filed in Figma. Map one persona per map (the mid-market and enterprise buyer have different journeys, so do not merge them), include the back-stage layer so it shows causes rather than only symptoms, keep the emotional layer (the 'what' without the 'how it feels' misses the point), name pain points specifically, and translate the opportunity map into specific projects with owners and timelines. Then maintain it: revisit annually or after major changes, because a year-old map describes a year-old user.