Map one journey from the customer's side

Journey maps have a reputation problem. Many teams have made one: a long poster with stages across the top, a smiley-face curve and a list of pain points, which went up on a wall and slowly faded. The map was accurate. Nothing changed because of it.

The maps that lead to real change tend to share two habits. They describe one specific journey in enough detail to act on, and they come with a second drawing that shows how the company delivers each step.

What a journey map is for

The Nielsen Norman Group defines a journey map as a visualization of the process a person goes through to accomplish a goal. The key word is goal. A journey map starts with what the customer is trying to do, and follows them until it is done, across every channel and team they touch along the way.

For each stage, a good map records:

• what the customer is doing,
• what they are thinking and feeling, ideally in their own words,
• the moments where things go well or badly,
• and the opportunities to make it better.

Take the illustrative journey on our customer experience page. A facilities manager reports a freezer fault. The repair itself goes well. What they remember is the time on hold, the morning without an arrival time, and an invoice that did not match their purchase order. None of those problems belong to the technician who did the repair.

Build it from evidence

The fastest way to get a journey map wrong is to draw it in a workshop with only internal staff. Everyone in the room knows how the process is supposed to work. Customers experience how it actually works.

So start with a handful of customer interviews, walk through the journey with them, and read the support tickets and call notes for that journey. Then sit with the people who serve those customers for a day. The gaps between the three views are where the useful findings are.

Then draw the blueprint behind it

A journey map takes the customer's point of view. A service blueprint takes the company's. Under each stage of the journey, it shows the people, systems and processes involved, including the ones the customer never sees.

In the freezer example, the blueprint would show the call center logging the fault in one system, dispatch working in another, and billing pulling the job into the accounting system without the purchase order, because that field was never passed along. That single missing field explains the bad moment at the end of the journey.

This is why the blueprint matters. The journey map tells you where it hurts. The blueprint tells you why, and who needs to change what.

Make it a working document

A journey map should change as you fix things. Keep it somewhere the team works, not on a wall. Mark each pain point with an owner and a status. When a fix ships, update the map and check whether the numbers for that stage moved.

Where to start

Pick one journey, interview five customers who went through it last month, and sit with one frontline team for a day. You will have enough for a first map and a first blueprint within two weeks. If you want help with either, see our customer experience work.