Customer Journey Map Template, With a Worked Example From Research

Which stages and lanes belong in a journey map template?

A journey map template should hold the 5–7 journey stages your user research finds and 8 lanes, so each column shows where one persona actually struggles.

We set the stage count at 5–7 per map, because fewer hides the hard moments and more turns the grid into a user flow. Keep the map scope to one user type and one scenario, as NN/g advises one point of view per map. Our research program sets the persona count at 2–4, each built from user interviews rather than invented in a workshop like a marketing buyer persona.

What are the 7 steps of the customer journey?

No single standard defines a 7-step customer journey; one published 7-stage set is awareness, consideration, decision, purchase, use, loyalty and advocacy.

That set suits a lifecycle customer journey map for a whole brand or product lifecycle; for a software-as-a-service (SaaS) product, the lifecycle journey mapping step of our SaaS UX design process covers the in-product part of a lifecycle, every stage from sign-up to renewal. For product work, stages named from interviews beat it: "Consideration" tells a designer nothing about which screen to change, while "Set shift rules" does.

Current-state, future-state and day-in-the-life maps

A current-state map shows today's journey, a future-state map shows the journey you plan to build, and a day-in-the-life map covers one person's whole working day.

The download is a current-state map by default; a future-state map reuses the grid after research, and a day-in-the-life map suits shift work, where your product's user interface (UI) is one screen among many, such as the picker and dispatcher shifts our researchers shadow for supply chain UI UX design. A circular map draws the stages as a loop, for journeys that repeat, such as a monthly subscription renewal.

What each lane needs

A customer journey map template only saves time if every cell can point to a source:

• Persona and scenario header: the research base line (methods, sessions, dates) lets readers judge the map first.
• Journey stages: named after what participants did, in their order.
• Touchpoints: every screen, email, call and person, since problems often sit between channels.
• Emotion curve: its sharpest highs and lows flag likely moments of truth, where the user forms a lasting opinion and decides to stay or leave; the highs are moments of delight, but check the lowest point first.
• Evidence lane: source and evidence level for every cell, so guesses stay visible.
• Opportunities and owners: one internal owner and one metric each, or nobody acts on them.

The Thinking lane holds thoughts and mindsets as verbatim quotes, never a team summary. Rename the stage columns from your own notes before you write a single cell.

Where does evidence for each journey map lane come from?

Each journey map lane needs its own kind of user research: interviews fill Thinking, contextual inquiry fills Doing and Touchpoints, and analytics and support tickets count pain points.

Kate Kaplan's NN/g guide on when and how to create customer journey maps treats journey mapping as a qualitative-research process and notes that quantitative data alone cannot build the story. Numbers back up a map; they never write it.

Our research program plans an interview count of 10–15 one-hour user interviews per user group. Contextual inquiry means watching people do real work where they do it and asking about it as they go; we set the observation count at 4–6 users, on site, for example at a clinic front desk. Our guide on how to run a contextual inquiry covers the method itself.

The table maps each research source to the lanes it fills and its blind spot; for sample sizes and outputs across 12 studies, see how UX research methods compare on sample size and output.

The evidence lane gives every cell an evidence level from a four-letter key:

• H, heard: said in interviews, with a count such as "9 of 12".
• O, observed: seen during site visits or session recordings.
• M, measured: counted in analytics or support tickets.
• A, assumed: team knowledge nobody has checked yet.

The intro's workshop cell is an A; its research cell is an H and an O. NN/g calls a map built from what a team already knows a hypothesis map, and the hypothesis map vs research map distinction matters: the first plans a study, the second is the deliverable. Session recordings show only the screen, so observed cells about the work around it need site visits; our researchers run those 4–6 sessions in our program's generative fieldwork step (7–15 days). Mark every cell on your map before you book interviews.

How do you fill a customer journey map template in 7 steps?

Fill a customer journey map template in 7 steps, from fixing one persona and scenario through interviews, contextual inquiry and synthesis to a validated map with owners.

These steps answer how to create a customer journey map and how to create a user journey map alike; only the scope in step 1 changes.

1. Frame the scope. One user type, one scenario, 3–5 research questions. Output: a scope sheet.
2. Gather what you have. Pull analytics, support tickets and past studies, then draft a hypothesis map. Output: mostly A cells.
3. Run user interviews. 10–15 one-hour sessions per user group about the last time they did the task. Output: verbatim quotes.
4. Observe with contextual inquiry. Watch 4–6 users do the task where they work. Output: observation notes and workarounds.
5. Tag and cluster. Tag notes in Dovetail, then use affinity mapping, which groups related findings into clusters, to sort them by stage. Output: clusters per stage.
6. Write each lane. Name stages from the clusters, quote verbatims, plot the emotion curve and mark evidence levels. Output: a sourced map.
7. Validate and assign. Walk 2–3 participants or frontline staff through it, validate and refine, then give each opportunity an owner and a metric. Output: a validated map.

In our program, the interviews and contextual inquiry of steps 3 and 4 run in the generative fieldwork step of our 5-step UX research process, and the map comes out of its synthesis and readout step (4–7 days), inside a research timeline of 4–8 weeks. Start with step 2 this week, because a hypothesis map shows which interviews to book.

Customer journey map template, filled in (illustrative)

This customer journey map example is illustrative: a user journey map of one practice manager's first month with a clinic scheduling app, built from invented user research.

It doubles as an example of a user journey map, since it follows one product task; the clinic, the app, the people and every number are made up. Dana manages a 3-site physiotherapy clinic, the scenario is first-time setup, and the research base reads 12 interviews with practice managers and 5 contextual inquiry visits to front desks.

Read the Evidence row first: every opportunity rests on H, O or M evidence, none on an A. The emotion curve bottoms out at stage 4, so swaps are Dana's likely moment of truth. Print the filled example PDF beside your blank copy and compare your lanes row by row.

How do you turn a journey map into decisions, not wall art?

A journey map drives decisions when every opportunity carries one owner, one metric and a date, and the team ranks opportunities by emotion low point and user research evidence.

Our ranking rule weighs how far the emotion curve drops against the evidence level: observed and measured outrank heard, and heard outranks assumed. The table ranks the worked example's top three opportunities with their internal ownership and metric.

Pick each metric from the key performance indicators (KPIs) the owner already reports, so the map's metrics and KPIs need no new dashboard. A journey map is a living document; the FAQ on updates gives our review cadence. For a real case, see how we mapped the Vocable creator journey: the team mapped the full creator journey and designed each screen around a problem heard in stakeholder interviews, across planning, drafting, optimizing and publishing.

A map of mostly A cells cannot settle a priority argument, and when a team disagrees about priorities without shared personas or journey maps, we advise investing in UX research. Put an owner's name in every Opportunities cell before the meeting ends.

Which customer journey map mistakes waste the template?

Six customer journey map mistakes waste the template, and the worst is presenting an assumption-only map as user research, because nobody can then tell guesses from findings.

• Assumed cells sold as research, because the map hides its guesses; the evidence lane shows every A.
• Several personas on one grid, because their emotion curves cancel out; draw one map each.
• Funnel stages on a product task, because "Consideration" names no screen; name stages from clusters.
• An emotion curve with no quotes, because a -2 nobody said is a guess; quote every point.
• Too many lanes, because nobody reads a 14-lane map; keep 8.
• A map never updated, because cells go stale after releases; date the evidence lane.

Before you share a map, check that every quote carries a participant ID, every cell an evidence level and the header a review date; send any map that fails back to the step that owns it.

When should researchers build your customer journey map?

A customer journey map needs user researchers when it must settle a product decision, its users are hard to observe, or most of its cells are still assumed.

The personas and journey maps our research program delivers are 2–4 personas with 1 journey map each, built from 10–15 interviews per user group and contextual inquiry, tagged in Dovetail and presented in a 90-minute readout. The program costs $25,000–$60,000; see what a 4–8 week research program costs and, when comparing providers, how to choose a UX research agency.

Filled from team knowledge alone, a customer journey map template becomes a hypothesis map, and each A cell names a question the evidence table can assign a method to. The proposal can be scoped around those open cells once you send us the hypothesis map you already have. Every project begins with a free consultation and a fixed-scope proposal.

FAQs