UX Encyclopedia

User Journey Map

A user journey map visualizes what one person experiences over time while pursuing a goal in a specific scenario: the stages they pass through, what they do, think, and feel at each stage, where it hurts, and where the product could do better. It is a story told as a table — time runs left to right, and the rows hold the human evidence (actions, thoughts, emotions) that a flow diagram deliberately leaves out.

Working definition for this section: a user journey map covers ONE scenario with your product or service ("Maya files her first expense report"). For the whole relationship with the company (marketing → sales → support → renewal), see Customer Journey Map. For an experience bigger than any product, see Experience Map. NN/g treats "user journey map" and "customer journey map" as interchangeable terms — the split used here is a working convention, not an industry standard (see file 05 for the honest note).

Journey map vs. user flow

Different tools, commonly confused (NN/g, "User Journeys vs. User Flows"):

  • User flow (User Flow): micro, granular, one product — the paths and decisions, no emotional information. Minutes of activity.
  • Journey map: macro, cross-channel, over hours/days/weeks — the actions PLUS the thoughts and feelings around them, including touchpoints outside your product (a phone call, a colleague's advice, a competitor's site).

Rule of thumb: flows answer "what path?"; journeys answer "what is it LIKE?" Use the journey map to decide which pains matter; use flows to redesign the steps that cause them.

When to use one

  • Align a team on where the experience actually hurts — the map turns scattered research findings into one shared picture.
  • Prioritize: pain points with severity, at a stage, tied to evidence, become a ranked opportunity backlog (see 07-process-strategy/ UX Strategy — current-state journey → opportunity backlog).
  • Diagnose cross-channel breaks a single-screen view can't show (email says one thing, app says another).
  • Build empathy in teams far from users — engineers and executives read a journey map; they will not read a research report.

Map the CURRENT state before dreaming a future state: you can't fix what you haven't honestly drawn.

Anatomy (per NN/g Journey Mapping 101)

Five elements, verified against Gibbons's article:

  1. Actor — one persona/user per map, grounded in research data. One point of view per map; blending actors blurs everything.
  2. Scenario + expectations — the situation and goal ("switch mobile plans"), plus what the actor expects to happen. Real or anticipated, but always specific.
  3. Journey phases — the high-level stages that organize the rest.
  4. Actions, mindsets, and emotions — within each phase: what the actor does, what they think (ideally research verbatims), and how they feel — commonly drawn as a single emotion curve rising and dipping across the map.
  5. Opportunities — the "so what": insights, owners, metrics — what the team will change and how it will know it worked.

Most teams add rows for pain points and touchpoints/channels; NN/g's five elements are the core, the extra rows are common practice.

Example: B2B tool, first month (compact form)

Awareness Evaluation Signup First Use Repeated Use Support Renewal
Doing Reads a comparison post a peer shared Watches demo, checks pricing, asks Slack community Creates account, verifies email Imports data, invites teammate Weekly reporting task Files ticket: export is broken Reviews invoice, usage report
Thinking "Could this kill our spreadsheet mess?" "Which tier do we actually need?" "Why does it need my phone number?" "Where do I even start?" "This is faster than the old way" "Did anyone even read my ticket?" "Did we get enough value?"
Feeling Curiosity Hesitation Confusion Confidence (after first import works) Relief Frustration Delight (usage report shows time saved)
Pain Jargon-heavy landing page Pricing page hides per-seat math Phone field feels invasive Empty dashboard, no guidance Occasional slow loads 48h first response Renewal email is invoice-only
Opportunity Plain-language positioning Pricing calculator Make phone optional; say why asked Guided first import (Onboarding Flows) Perf budget on reports Status page + 4h SLA Value-recap email before invoice

The Feeling row is the emotion curve in words: curiosity → hesitation → confusion → confidence → relief → frustration → delight. Plotted as a line, the two dips (Signup, Support) are where the map earns its keep — they tell you where to spend the next sprint.

The evidence rule

A journey map is a research output, not a workshop invention. NN/g is explicit that actions should be "rooted in data" and mindsets drawn from customer verbatims; a map assembled from team guesses is a consensus of assumptions wearing a research costume — the exact anti-pattern named in UX Strategy ("personas/ journeys invented in a workshop with no data"). Sources to draw from: interviews, field studies, support tickets, analytics funnels, session recordings (see UX Research Methods). A workshop is fine for DRAFTING hypotheses — label the draft "assumed" and go validate it before anyone prioritizes from it.

Common mistakes

  • Multiple actors or scenarios on one map — pick one of each.
  • Emotion row filled by vibes ("probably annoyed") instead of quotes and observed behavior.
  • Beautiful poster, no opportunities row — a journey map without a "so what" is wall art.
  • Only mapping your own touchpoints — the actor's journey includes the spreadsheet, the phone call, and the competitor tab.
  • Mapping the future state first and mistaking it for the present.
  • Making it once and never updating it; a stale map misleads with authority.

Checklist

  • One actor, one scenario, expectations stated at the top
  • Phases named from the actor's point of view, not internal org stages
  • Actions, thoughts (verbatims where possible), and emotions per phase
  • Emotion curve drawn; every dip explained by an identified pain
  • Touchpoints/channels noted, including ones you don't own
  • Every claim traceable to a research source (or labeled "assumed")
  • Opportunities row filled, with owner and success metric per item
  • Current state mapped before any future-state map
  • Stored where the team works; revisit date set

Sources

↑↓ to navigate · Enter to open · Esc to close