Customer Journey Map:
Definition, Template, and Handoffs

A customer journey map is a visual account of how a customer or user works toward a specific goal with a product or service. It places actions, thoughts, and feelings along a timeline, following the structure described in Nielsen Norman Group’s journey-mapping guide.

The map helps examine the experience across interactions and identify opportunities for improvement. Nielsen Norman Group’s guidance on using journey maps highlights disconnected experiences and unclear ownership as problems the method can address. Finding broken handoffs is one practical use: inspect what happens between steps, then identify the work needed to help customers continue.

What belongs in a customer journey map?#

The core components of a journey map establish whose experience is being mapped, the goal, the stages, the experience within those stages, and the opportunities identified.

Touchpoints and channels add detail to the route. In Nielsen Norman Group’s terminology, a touchpoint is an interaction with the organization, while a channel is the medium through which communication or service delivery happens. Record both the interaction and its medium, rather than listing channels alone.

How to choose customer journey stages#

Name phases after the work customers actually do. Nielsen Norman Group’s account of practitioner methods explains that phases can emerge during research or mapping. Treat a preset lifecycle as a starting framework, then revise it against evidence. Record waiting, repeated steps, and returns to earlier activities wherever the research shows them.

Set the endpoint around the customer goal. The GOV.UK Service Manual’s guidance on the whole user problem explains that a transaction can be part of a larger task, crossing organizational boundaries and online and offline touchpoints. Include the steps needed to understand that task, and mark where another organization becomes responsible.

Keep routes separate when their differences matter. GOV.UK’s experience-mapping method recommends consolidating similar researched routes and creating separate maps when user groups go through significantly different stages and steps. Preserve those differences before summarizing a shared route.

Customer journey map template#

Use phases as columns and the following fields as rows. GOV.UK’s mapping guidance describes a grid of researched stages and activities enriched with needs, touchpoints, channels, thoughts, and feelings. This working template adds evidence and action fields for reviewing handoffs.

Above the grid, fill in:

• Customer group: the people whose experience the map represents.
• Goal: the outcome being pursued.
• Boundaries: the starting point and endpoint.
• Map type: current state or proposed future state.
• Evidence period: when the underlying research and records were collected.
• Map owner: the person responsible for keeping the document current.

Leave unresearched entries marked as unknown. Keep quotes attached to their source; use a paraphrase label for summaries. Add or remove phase columns as the evidence requires. The template is a structure for collecting findings, with no customer observations prefilled.

How to create a customer journey map#

The five-step journey-mapping process described by Nielsen Norman Group moves from scope and stakeholder involvement to existing evidence, a hypothesis map, customer research, and visualization. These are steps for creating the map; customer journey phases describe the customer’s experience.

1. Define the goal, customer group, and scope#

Write the map header before filling the grid. Specify the experience to investigate, its boundaries, and the decision the map will inform. Identify the people who hold evidence about different parts of the route and those who can act on the findings.

Choose the map’s purpose explicitly (Nielsen Norman Group distinguishes current-state evaluation from future-state planning). A current-state map describes the experience being investigated. A future-state map sets out a proposed experience. Label planned changes separately from observations, and preserve the current map for comparison.

2. Gather existing evidence and draft the route#

Collect relevant research, feedback, support records, and behavioral data. The internal-investigation stage of Nielsen Norman Group’s process brings together information held across the organization before drafting a hypothesis map.

Arrange the known steps in order. Label staff assumptions and unanswered questions directly in the draft. Maintain a reference for each finding so that later research can confirm, change, or remove it.

3. Research the experience with customers#

Use methods that recover both actions and their context. Nielsen Norman Group’s research guide recommends qualitative methods that involve talking to or observing users, including:

• Interviews: accounts of experiences, needs, and difficulties.
• Field studies: observation of activity in its actual setting.
• Diary studies: records of actions, thoughts, and feelings over time.

Ask about specific steps and recent experiences. Compare accounts with observations where possible, and investigate gaps in the draft.

Quantitative evidence can supplement those findings. The same research guide explains how surveys and analytics can help assess the frequency and extent of problems. Use behavioral counts alongside qualitative research; the counts alone do not explain a person’s motives or emotional experience.

4. Revise the map and make findings traceable#

Replace assumptions with findings as evidence becomes available. Keep unresolved entries visible, and preserve important differences between routes. GOV.UK recommends reviewing and rearranging a draft map until it accurately reflects the researched experience.

For each important entry, retain the evidence reference, collection date, and whether it describes observed behavior, a reported experience, or an assumption. Use a companion evidence document when those details would make the map difficult to read.

5. Identify opportunities and owners#

List the problems supported by the completed map. Connect each to the affected step, the customer goal, and the evidence. Nielsen Norman Group’s guidance on insights and ownership calls for explicit findings and responsibility for the parts of the journey that need attention.

How to find broken handoffs#

A handoff is the transition from one interaction or responsible party to the next. To examine it, compare what the previous step provides with what the next step requires. Use these questions to guide the evidence review:

• Information: What details must carry forward, and does the next responsible party receive them?
• Instructions: Can the customer identify the next action and where to take it?
• Timing: What wait or confirmation is required before progress can continue?
• Responsibility: Who handles the next step, including unresolved problems?
• Continuity: Does the customer have to repeat information, restart work, or reconcile conflicting messages?

Document the break and its effect separately from the suspected cause. The GOV.UK Service Manual identifies dead ends, confusing or duplicative content, and disconnected online and offline steps as problems whole-journey mapping can reveal. Check the actual records and researched route before assigning any of these labels.

Investigate the service behind the interaction when the cause remains unclear. A service blueprint connects customer touchpoints to people, backstage activities, and supporting processes. Use that view to trace dependencies and information transfers rather than assuming the customer-facing message is the source of the problem.

Turn findings into improvements#

Review the customer consequence, the available evidence, and the work required to address each finding. GOV.UK’s whole-journey guidance distinguishes quicker changes from larger improvements that require coordination across services.

For each selected improvement, create an action record containing:

• Problem: the affected step and the obstacle to the customer goal.
• Evidence: the research or records supporting the finding.
• Proposed change: the specific intervention to investigate or implement.
• Owner and dependencies: who can make the change and whose cooperation is required.
• Outcome measure: the result to check, with a defined population and measurement period.
• Review point: when to assess the change and revisit the map.

Choose the measure to match the finding: task completion, elapsed time, repeated contacts, or the need to repeat information. Record a baseline before assessing a change. Revisit the same customer goal afterward, collect relevant evidence, and update the current-state map to reflect what is now happening. Keep proposed improvements in the future-state version until their implementation and effects have been checked.

Customer journey map vs. other mapping tools#

These views can work together. Nielsen Norman Group describes a user flow as a deeper examination of part of a broader journey. Keep the journey map as the view of the overall customer goal, and attach the more detailed flow or blueprint to the step it helps explain.