Journey Mapping

Concept of the skill

Journey mapping is the discipline of modeling a person's end-to-end lived experience across touchpoints, channels, and time, so a team can see — and align on — what the user actually goes through rather than what any single screen, diagram, or backlog reveals. A journey map lays the experience out as a timeline of stages (for example Awareness → Consideration → Purchase → Onboarding → Use → Renew) with vertical lanes for what the user is doing, thinking, and feeling, and which touchpoint they are using; an emotional curve rendered along that timeline exposes the peaks and troughs — the "moments of truth" — that disproportionately shape the overall impression. A service blueprint extends the map downward through the line of visibility into the back-stage employees, systems, and support processes that produce each front-stage moment, which matters whenever the experience depends on handoffs the user never sees. The map's credibility comes entirely from being grounded in research synthesis: each pain point and emotional low cites real evidence, stages are named from the user's perspective rather than the business's, and the artifact identifies specific opportunity areas at named stages instead of a generic "improve onboarding." Done well, journey mapping is the only artifact that treats experience as temporal and cross-channel, letting a team invest in the moments that actually decide success.

Concept Card

What it is: A time-ordered model of one actor's lived experience across touchpoints and channels — laying out what they do, think, and feel, against the front-stage interactions and the back-stage processes that produce each moment.

Mental model: Experience is one continuous arc, not a set of isolated screens. A journey map layers actions, thoughts, and an emotional curve over a stage timeline, then (in a service blueprint) extends downward through the line of visibility into the back-stage work and support processes that cause each moment.

Why it exists: To surface where an end-to-end experience helps or fails a person — emotional peaks and troughs, drop-off points, opportunity moments — so a team aligns on the same cross-channel reality and invests in the moments that matter, rather than optimizing individual screens in isolation.

What it is NOT: Not single-interface task decomposition (that is task-analysis), and not service/architecture diagramming. Its unit is a person's moment — including emotion and context — not a UI step or a service call. A flow stripped of the emotional curve, the cross-channel/time span, and the back-stage layer is a task flow, not a journey map.

One-line analogy: Like a film's emotional storyboard rather than a wiring diagram — track how the protagonist feels scene by scene across locations and time, and fix the scenes that lose the audience, not the lighting rig behind them.

Coverage

Journey mapping covers the family of visualizations that lay out a user's experience as a timeline across stages, actions, thoughts, feelings, and touchpoints. The classic customer journey map (Jeff Patton's writing on story mapping is an adjacent influence; NN/g has codified the canonical structure) typically has a horizontal axis of stages (e.g., Awareness → Consideration → Purchase → Onboarding → Use → Renew/Churn) and vertical lanes for what the user is doing, thinking, feeling, and which touchpoint they are interacting with. An emotional curve rendered along the timeline highlights peaks and troughs — the "moments of truth" that disproportionately shape the overall impression.