Journey mapping came into UX practice from service design in the early 2000s, formalised through practitioners like Adaptive Path and Nielsen Norman Group. The core structure is a horizontal timeline broken into stages, with rows showing what the user does, thinks, feels, and encounters at each stage.
There are two useful variants: current-state journey maps document what the experience is now (used for audits and opportunity identification), and future-state journey maps propose what it should become (used for design vision and roadmap alignment). Both are structured the same; they answer different questions.
Products and services are often designed screen-by-screen but experienced flow-by-flow. A checkout might work well as a single form but fail because the user arrives at it from a place of confusion built up over the previous six steps. Journey maps make the cross-screen experience visible, which surfaces problems that page-level analysis misses — and identifies opportunities analytics can't reveal.
During experience audits (mapping the current state to identify pain points), during service design (designing coherent end-to-end experiences), during onboarding or churn work (where the emotional arc matters as much as the functional steps), during cross-team alignment (getting product, marketing, ops and support looking at the same experience).
A journey map for a new SaaS user might have stages: aware → sign-up → onboard → first value → habit → expand. Under each stage, the map records what the user does (specific actions), thinks (questions and doubts), feels (emotional register), and encounters (touchpoints, blockers, moments of delight). Data comes from research: interviews, session recordings, support tickets, analytics funnel drop-off points.
The most useful column is often 'feels', because it exposes where the experience is emotionally hostile even when the functional steps work. A signup flow that completes but leaves users feeling suspicious of the product produces different design work than one that leaves them feeling confident.
Journey maps should be updated when the underlying experience changes materially — not just after research sprints. A stale journey map that no longer reflects the shipped product misleads more than no map at all.
Journey maps complement JTBD (which names the underlying job), personas (which name the user), and empathy maps (which detail per-moment emotional register). They intersect with UX research methods (interviews, session recordings, funnel analysis feed them).
Reviewed 29 September 2026 · Editorial standards