Customer Journey Mapping

See an experience as the customer experiences it—not as the organisation divides it into channels, teams and systems.

In one minute

A customer journey map is a structured view of how a defined person pursues a defined goal over time. Its columns show stages; its rows show evidence about the experience:

• goals and actions;
• touchpoints and channels;
• questions and expectations;
• emotions and effort;
• pain points and failure risks;
• supporting evidence;
• opportunities, owners and measures.

A map of the current journey is an evidence model. A map of the future journey is a design hypothesis. Keep them separate.

Best for: cross-channel services, onboarding, retention, support, employee services and experiences that cross organisational boundaries.
Avoid when: there is no defined actor and scenario, the team has no customer evidence or the problem is a single known interface defect.

The problem it addresses

Customers experience one journey while organisations manage many local processes. Each team may meet its target and still produce repetition, uncertainty and avoidable effort at the hand-offs.

Journey mapping creates a shared view of the end-to-end experience. The intended output is not a decorative empathy artefact. It is a prioritised set of evidence-backed opportunities linked to operational ownership.

When to use it

Use a journey map when:

• customers move between digital, human and partner channels;
• local improvements have not changed overall satisfaction or completion;
• complaints cluster around hand-offs or waiting;
• a new service needs a target experience;
• teams disagree about what customers actually do;
• you need to connect experience evidence with process change.

The journey should begin when the customer’s goal becomes active, which may be before first contact with the organisation.

When not to use it

Do not use a journey map:

• as an internal process flow with a customer icon added;
• to combine several actors, goals or journeys into one average;
• as a replacement for direct research;
• when current and future states are mixed together;
• when no team owns the opportunities after the workshop;
• to diagnose the technical root cause of an isolated failure.

Use a service blueprint after the journey map when backstage activities, systems and policies must be connected to frontstage experience.

Inputs required

• a named actor or evidence-based segment;
• a specific goal and scenario;
• start and end boundaries;
• interviews, observations and service artefacts;
• behavioural analytics and operational data;
• complaints, support contacts and failure records;
• front-line staff evidence;
• a cross-functional team with relevant process owners.

Step-by-step process

1. Define the decision

State why the map is being created. Examples: reduce onboarding abandonment, redesign a return journey or identify causes of repeat contact.

2. Choose one actor and scenario

Specify the actor’s goal and context. Distinguish user, purchaser, administrator and beneficiary if their journeys differ.

3. Set the boundaries

Define the first event and meaningful end state from the actor’s perspective. Include before and after the core service where they influence success.

4. Collect and label evidence

Use several sources. Label direct observation, participant report, analytics, operational data and team assumption. Do not silently convert an assumption into a customer fact.

5. Build the stage spine

Create 4–8 stages expressed in customer language. Avoid using department names as stages.

6. Add experience layers

For each stage, capture:

• goal;
• action;
• touchpoint;
• question or expectation;
• emotion and effort;
• barrier or risk;
• evidence.

7. Identify moments that matter

Look for high effort, uncertainty, negative emotion, repeated information, delay, channel switching and loss of trust. Mark both severe failures and moments that determine confidence.

8. Frame opportunities

Turn each priority problem into a question or outcome. Avoid jumping directly to a feature.

9. Connect ownership and measures

Assign an owner, first test and expected customer and business measure. Add backstage analysis when the cause spans systems or policies.

10. Create a separate future-state map

Describe the intended experience and the assumptions it depends on. Validate the new journey before treating it as a plan.

Visual model

Text alternative: the customer moves from an active goal through discovery, evaluation, start, use and resolution or renewal. Evidence layers describe the experience at each stage and reveal prioritised opportunities.

Interactive example

Scenario

BrightDesk provides IT support to small businesses. Customers rate the technical fix highly but report low overall satisfaction.

Evidence:

1. The requester submits a web form and receives a ticket number.
2. The form asks for device details that the support agent asks for again.
3. Customers cannot see whether a ticket is waiting for them or for the support team.
4. Median fix time is four hours, but elapsed time reaches two days when a reply is missed.
5. Closure messages describe the technical change but not what the customer should do next.

Your move

Identify two journey stages, one critical pain point and one opportunity measure.

Worked answer

Stages: request help; diagnose and exchange information; confirm resolution.
Critical pain point: responsibility becomes invisible during the information exchange, so customers miss replies and experience unpredictable delay.
Opportunity: make the next required action and owner visible at every update.
Measure: reduce tickets delayed more than one business day by an unanswered request from 24% to below 10%.

The problem is not simply “slow support”: technical work is fast, while the journey loses momentum at a hand-off.

Facilitation notes

• Put evidence directly on the map or link it with IDs.
• Let customers define meaningful stages during research; let the team refine them later.
• Keep emotional curves tied to events and causes.
• Invite front-line staff to challenge impossible future-state ideas.
• Add backstage systems only after the customer view is clear.
• End with no more than three priority opportunities for the first cycle.

Expected output

A useful journey-mapping exercise produces:

• a named actor, scenario and boundary;
• a dated current-state map;
• evidence and confidence labels;
• critical moments, effort and hand-off failures;
• prioritised opportunity statements;
• owners, measures and next tests;
• a separate future-state hypothesis where needed.

Common mistakes

1. Mapping the organisation. Department steps are not the customer journey.
2. Using an invented persona as evidence. A plausible story remains a hypothesis.
3. Mixing journeys. Different goals and roles create contradictory maps.
4. Drawing an unsupported emotion curve. Emotion needs an event and evidence.
5. Stopping at pain points. Opportunities need ownership and measures.
6. Making the future state look current. The distinction affects decisions.

Quality checklist

• One actor, goal and scenario define the map.
• Start and end boundaries follow the customer’s goal.
• Stages use customer language rather than department names.
• Important claims have evidence or an assumption label.
• Emotion and effort are tied to events.
• Cross-channel and cross-team hand-offs are visible.
• Current and future states are separate.
• Priority opportunities have owners, measures and next tests.

Template

Knowledge check

Which statement belongs on a current-state journey map as evidence?

A. “Customers will enjoy the redesigned portal.”
B. “The Operations team approves the request.”
C. “Six of eight observed customers re-entered information after moving from chat to the form.”
D. “Add a progress tracker.”

Answer: C. It describes observed customer behaviour. A is an unsupported future claim, B is an internal process step without customer meaning and D is a solution idea.

Related tools

• Often combined with: Design Thinking, service blueprinting
• Supported by: Jobs to Be Done, customer research
• Followed by: Root Cause Analysis, process redesign and experimentation
• Not to be confused with: a process flow, funnel report or interface sitemap

References

1. Service Design Tools. “Journey Map.” Method overview (opens in a new tab).
2. Nielsen Norman Group. “Customer Journey Map Template.” Template (opens in a new tab).
3. Kalbach, J. Mapping Experiences. O’Reilly Media, 2nd edition, 2020.

Sources reviewed 28 July 2026.