Journey Mapping
A visual, end-to-end map of a person’s experience over time, revealing the highs, lows, and gaps that no single moment shows.
The whole experience on one picture, including the silent gaps between touchpoints where the real problems usually hide.
What it is
The whole experience on one picture — including the silent gaps.
A journey map visualizes the complete experience a person has with a product, service, or organization, laid out as a sequence of stages over time, with what they do, think, and feel at each stage. Its power is that it makes the whole experience visible at once. Individual teams each own their slice of an experience and each can make their slice look fine; the journey map is what reveals the friction, the emotional lows, and above all the gaps between touchpoints that no single-moment analysis would ever catch. It turns a fragmented set of interactions into a single, shared, navigable picture an entire organization can stand around and point at.
The signature of a journey map is the emotional line, the rising and falling curve of how the person feels as they move through the experience. More than any other element, that curve is where the insight lives, because the lowest point on it is almost never where a team expects, and it is usually somewhere the team does not own — in the gaps, the handoffs, the silence between one department’s touchpoint and the next.
Crucially, Journey Mapping is not one rigid artifact. It is a modular, flexible method that flexes to the question you are asking. The next sections make that concrete.
The journey
Walk the experience. Click any stage.
As you click across the stages, the emotion line tells its story. Pay attention to where it dips — and look for the orange gap marker, which sits between stages, not at one.
When to deploy it
A synthesis tool for multi-step, multi-touchpoint experiences.
Use Journey Mapping when
- →An experience spans multiple steps, channels, or touchpoints and you need to see the whole arc, not just a single interaction.
- →You suspect the problem lives in the handoffs and gaps between touchpoints rather than in any one of them.
- →You need a shared picture an entire cross-functional team can align around — especially when each team currently only sees their own slice.
- →You are designing a future-state experience and need to see the current-state lows you must fix before you can build the ideal.
Do not lean on it when
- ×The experience is a single screen or one-moment interaction — there is no journey to map.
- ×You need the operational, behind-the-scenes view of how a service is delivered. That is Service Blueprinting (see "Where it ends" below).
- ×You need a fixed phase-by-phase evaluation lens applied consistently across experiences. That is the 5Es Framework (see "Where it ends" below).
- ×You have not done research. A journey map built from assumption is a confident diagram of the team's wishful thinking — worse than no map, because it looks authoritative.
The honest limit: a journey map is only as true as the research behind it. Built from assumption rather than from real people’s experience, it becomes a tidy diagram of what the team wishes happened, which is worse than no map at all because it looks authoritative.
How it works
Six moves, in order.
Set the scope and the subject.
Decide whose journey, over what span, in what state. These choices are the method's modularity — covered in the next section. The decision matters before you draw a single lane: a customer journey map, an experience map, and an emotion map each answer a different question even though they look similar on the surface.
Lay out the stages in sequence.
From before the person engages, through the core experience, to after. Crucially, include the before and after: experiences do not begin at first contact or end at purchase. The bookend stages are where some of the highest-value opportunities live.
Populate the lanes.
For each stage, capture what the person does, thinks, and feels — grounded in real research. Add only the lanes the question needs. More lanes is not more insight; an overloaded map is unreadable and gets ignored.
Draw the emotion line.
Trace the rising and falling curve of how the person feels across the stages. This is the single most important step; the curve is where the insight is. Do not skip it or treat it as decoration.
Find the lows and the gaps.
Identify the deepest emotional dip and — critically — the gaps between stages. The lowest point is often not at a stage at all, but in the silence between departments, between touchpoints, between one team handing off and the next picking up. These gaps are where the highest-value design opportunities hide.
Decide current or future.
A current-state map diagnoses what is. A future-state map designs what should be. Often you build both, the second as the explicit answer to the first. Keeping them as two distinct artifacts makes the gap between the current and the desired experience visible and actionable.
Versions & modularity
One method, dialed many ways. Toggle the swimlanes.
Journey Mapping is not a fixed artifact. Toggle lanes on and off to feel the flexibility directly: a quick three-lane sketch and a deep six-lane analysis are the same method, dialed differently.
Best practices
What good looks like — and what prevents it.
When it goes well
- ✓The emotion line reveals a low the team had genuinely underestimated — often somewhere they were not looking, and usually in a gap rather than at a stage.
- ✓The map exposes handoffs and silences that the individual teams owning each touchpoint could not see on their own.
- ✓It is built from real research: interviews, observation, and real users followed through the actual system — not from the team's assumptions about what happens.
- ✓The before and after stages are included, because the experience does not begin at first contact or end at the transaction.
- ✓The map becomes a shared reference the whole organization points at, not a document one team files away after the project ends.
The mistakes, and how to avoid them
Mapping the idealized process, not the real one.
Teams map how the experience is supposed to go. The value is in mapping how it actually goes, with all its friction, waiting, and silence. If the map looks perfect, it is probably not real.
Leaving out the emotion line.
A journey map without the emotion line is just a process flow. The feeling curve is where the design opportunities live. Without it, the map describes what happens but not whether it matters.
Omitting the gaps between stages.
The lowest point is often between stages, in the silence and the handoffs. A map that only shows what happens at each stage misses exactly where the problem usually is.
Building from assumption.
An unresearched map is a confident diagram of the team's wishful thinking. Ground every lane in evidence — interviews, observation, real users followed through the system.
Adding every lane by default.
More lanes is not more insight. Add only the lanes the question needs. An overloaded map is unreadable, and an unreadable map does not get used.
Logistics
Getting the inputs right, then using them well.
A good journey map is downstream of good research. The richest maps are built from in-depth interviews and from following real people through the actual experience. Plan the research before the mapping session; the map is a synthesis artifact, not a substitute for talking to people.
Getting the inputs
In-depth interviews and contextual observation are the usual primary sources. Aim to follow real people through the complete experience end to end, not just interview them about it afterward — memory flattens the gaps and the silences that matter most.
Running the mapping session
Journey mapping is usually a collaborative workshop. Get the cross-functional team in one room — or one shared digital canvas — so the people who each own a slice of the experience see the whole thing together, often for the first time. The shared "oh, that is what happens after we hand them off" moment is half the value.
Current then future
A common sequence is to build the current-state map first (diagnose), then build a future-state map (design) as the answer. Keep them as two distinct artifacts so the gap between the current experience and the desired one is visible and stays explicit.
Tools
Journey maps are built on whiteboards and sticky notes in person, or on digital collaboration canvases for distributed teams. The tool matters less than the conversation: what matters is that the map is built together, by the people who will use it.
Keeping it alive
A journey map dating from a single project quietly goes stale as the experience changes. The most useful maps are revisited and updated, treated as a living reference rather than a one-time deliverable.
AI and this method
AI can assemble the map in minutes. It still cannot feel the low point for you.
Toggle between modes to see where AI contributes across the journey map — what it accelerates, and what it flattens. Notice what happens to the emotion line.
In-depth example
The same scenario, mapped two ways.
A hospital redesigns its cancer care pathway. The same team, the same experience — once with traditional journey mapping grounded in human research, once using AI to synthesize the map from existing data. The contrast reveals what the two approaches catch and what they miss.
A hospital is redesigning its cancer care pathway, from a patient's first symptom through diagnosis, treatment, and follow-up. Each clinical department believes its own touchpoint works well. The team uses journey mapping to understand the whole experience.
The team builds the map from in-depth patient interviews and by following several real patients end to end through the entire system. They map the full arc: first symptom, GP referral, specialist appointment, test results, treatment, ongoing monitoring, and follow-up. Stages laid out in sequence.
The emotion line is drawn from what patients actually described feeling at each stage. Within any single department, the experience looked acceptable — each had optimized their own moment. But across the arc, the curve told a different story.
The lowest point was not any clinical moment. Not the frightening diagnosis. Not the treatment. It was the silence between departments. A patient would receive a result from one team and then wait — days with no contact, no information, no support — before the next team reached out. The deepest dip on the entire map was the gap, when patients felt abandoned and alone with their fear.
Finding
The insight was invisible to every individual department, because no department owned the gap. It surfaced only because the map spanned the whole journey and because a human had followed real patients into that silence and heard what it felt like.
Result
The redesign targeted the gaps directly: proactive communication, a single point of contact, and support during the waits. The clinical care had never been the problem. The spaces between it were.
Where it ends
Journey Mapping stops here — and what to use instead.
A good journey map knows its own edges. Two neighboring methods add territory Journey Mapping deliberately leaves out. Understanding where to stop is what lets you use all three well, together.
Journey Mapping — the experiencer's side
Journey mapping uses whatever stages fit the real experience: however many, named however the person actually experiences them. It stays strictly on the experiencer's side — their actions, thoughts, and emotions — which keeps it legible, empathetic, and focused on the felt experience rather than the operational machinery behind it.
When to reach for this instead
Use Journey Mapping to see and understand the whole felt experience. Reach for 5Es when you want a standard evaluation lens; reach for Service Blueprinting when you need to understand or redesign the backstage operations that produce the experience.
Frameworks
Where Journey Mapping shows up.
Journey Mapping is one of the most widely used synthesis methods — it appears wherever a framework turns raw research into a picture of the full experience arc.
Note: The Design Sprint typically imports an existing journey map or persona rather than building one fresh in five days, and FDE uses embedded observation rather than workshop-based mapping. These reflect real differences in how the method is used within each framework.
Related methods
What to combine with Journey Mapping.
Sources & further reading
The work behind this method.
Mapping Experiences
James Kalbach (2016)
The definitive reference on journey mapping, experience mapping, and alignment mapping. The best single source on the method's modularity, its different forms (customer journey, experience map, mental model diagram), and how to choose between them.
This Is Service Design Doing
Marc Stickdorn, Markus Hormess, Adam Lawrence, and Jakob Schneider (2018)
Journey mapping within service design practice — including the relationship between journey maps and service blueprints, and the role of both in designing service experiences.
This Is Service Design Thinking
Marc Stickdorn and Jakob Schneider (2011)
The foundational treatment of journey mapping as a service design tool, with the original framing that established much of the method's current vocabulary.