Customer Journey Mapping

Thinking Tools1.1 Describing the SituationAlso known as Journey Map

From service design and user-experience practice, linked to service blueprinting (G. Lynn Shostack, Designing Services That Deliver, 1984) and spread by Marc Stickdorn and Jakob Schneider (This Is Service Design Thinking, 2010).

Traces a customer's experience across every stage and touchpoint, recording actions, thoughts, feelings, and pain points, to find friction that internal process views miss.

A home insurance claim from the customer's side, and where it hurts most

Select a stage to read what the customer does, where she meets the insurer, and what she thinks. Set how she feels at each stage, 1 to 10: the lowest stage is marked, and that is where the fix belongs. Illustrative.

How she feels, 1 to 10

Notice the damage4
Report the claim3
Adjuster visit6
Wait for a decision2
Get paid7

Lowest moment2, set by Notice the damageReport the claimAdjuster visitWait for a decisionGet paid

Select a stage to read it, or play the sequence.Notice the damage. She shuts off the water, takes photos, and searches her email for the policy number. Touchpoint: the insurer's website. She thinks: am I even covered for this?Report the claim. She calls, waits, and is sent to the app, where she uploads the photos again. Touchpoints: the phone line and the app. She thinks: why did I wait on hold for this?Adjuster visit. The adjuster arrives on time, measures everything, and explains the next steps. Touchpoint: the adjuster in person. She thinks: finally, someone who knows what happens next.Wait for a decision. She checks the app daily; its status reads "in review" the whole time, and her calls go to voicemail. Touchpoints: the app and an unanswered phone. She thinks: they have forgotten me, and the kitchen is still torn up.Get paid. An email approves the claim in full and the money arrives two days later. Touchpoint: email and her bank. She thinks: fine, but I would not go through that again.
  1. Notice the damage. She shuts off the water, takes photos, and searches her email for the policy number. Touchpoint: the insurer's website. She thinks: am I even covered for this?
  2. Report the claim. She calls, waits, and is sent to the app, where she uploads the photos again. Touchpoints: the phone line and the app. She thinks: why did I wait on hold for this?
  3. Adjuster visit. The adjuster arrives on time, measures everything, and explains the next steps. Touchpoint: the adjuster in person. She thinks: finally, someone who knows what happens next.
  4. Wait for a decision. She checks the app daily; its status reads "in review" the whole time, and her calls go to voicemail. Touchpoints: the app and an unanswered phone. She thinks: they have forgotten me, and the kitchen is still torn up.
  5. Get paid. An email approves the claim in full and the money arrives two days later. Touchpoint: email and her bank. She thinks: fine, but I would not go through that again.

An example

A regional home insurer's claims team was hitting every target: water-damage claims settled in 26 days on average, inside the 30-day goal, and nearly all were paid in full. Yet those customers rated the insurer lower than any others, and a fifth did not renew.

The team mapped one segment, homeowners with a first water claim, from the customer's side. They built it from thirty call recordings, the app's logs, and eight interviews with recent claimants, and laid out five stages with what the customer did, where she met the insurer, and what she thought at each. The internal view had flagged hold times as the problem. The map put the low point somewhere else: the three weeks between the adjuster's visit and the decision, when the app read "in review" and calls went to voicemail. The team tested one fix on 200 claims, a text at each step of the review naming the person handling it. Calls to the claims line from that group fell by a third.

Why it works

A company sees its own process: queues, handoffs, and targets, each owned by a team that is meeting its numbers. The customer sees one continuous experience, and her worst moment can sit in a gap no team owns, such as the wait between two well-run steps. Mapping the journey from her side, stage by stage, puts that gap on the page.

Recording what she thinks and feels at each stage, alongside what she does, is what finds it. Actions alone would show a smooth process; the feeling line shows where the experience breaks, and it usually comes down to one or two moments in the whole journey. Building the map from real calls, logs, and interviews keeps it from becoming the team's guess about the customer, which would only reproduce the internal view.

The thinking behind it

G. Lynn Shostack G. Lynn Shostack, a senior vice president at Bankers Trust who wrote on services marketing, introduced the service blueprint in How to Design a Service (1982) and Designing Services That Deliver (1984). The blueprint charts each step of delivering a service and marks the points where it can fail. The journey map is linked to that practice: it keeps the sequence of steps and turns the view around to the customer's side.

Marc Stickdorn Marc Stickdorn, a service design practitioner and educator, edited This Is Service Design Thinking (2010) with Jakob Schneider. The book presents the tools of the field for newcomers, the customer journey map and the service blueprint among them, and it did much to spread the journey map. It is a practitioner's collection, and the map itself has no single originator: it grew out of service design practice.

Jakob Schneider Jakob Schneider, a designer, conceived This Is Service Design Thinking and edited it with Stickdorn: a multi-author introduction to service design that sets out its tools, customer journey maps and service blueprints among them. The book helped spread the journey map, and with it the practice of describing a service in the stages a customer goes through, from first contact to the last, with what happens to her at each one.

How to run it

  1. Pick one segment. Map one kind of customer in one situation, such as a first water claim, since a map of everyone shows no one.
  2. Name the stages from her side. Use the steps the customer would describe, which rarely match the company's departments.
  3. Fill each stage from evidence. Draw on call recordings, logs, support tickets, and interviews with recent customers, and mark anything guessed.
  4. Record actions, touchpoints, thoughts, and feelings. For each stage, write what she does, where she meets the company, what she thinks, and how she feels.
  5. Find the lowest moments. Plot the feeling across the stages and circle the one or two dips.
  6. Test one fix at the low point. Try a change on a small group and measure it against the stage it was meant to improve.

Where it goes wrong

The commonest failure is a map built in a conference room. A team that fills the stages from what it believes customers think produces its own process with a smiley face on it, and the low point lands wherever the team already suspected. If the map surprises no one, check where its contents came from.

A second failure is mapping every segment at once. The stages and feelings of a first-time claimant and a landlord with ten properties differ, and averaging them hides both low points.

The third is a beautiful map that changes nothing. Journey maps often end up on a wall. Tie the map to one fix at the lowest moment, with an owner and a measure, before calling it done.

When to use something else

  • Service Blueprint. When the low point is known and the fix depends on the backstage steps, staff, and systems behind it.
  • Empathy Map. When the need is one picture of what a customer says, thinks, does, and feels, without the sequence of stages.
  • Value Stream Mapping. When the trouble is waste and delay inside the company's own flow of work, seen from the process side.

Where it sits in SOLVE eX

Go to the source

  • Designing Services That Deliver, Harvard Business Review, 1984
  • This Is Service Design Thinking, BIS Publishers, 2010

Back to the catalog