Journey maps built on evidence, not guesswork

A customer journey map traces what a customer actually does, thinks, and feels while trying to get something done: opening an account, disputing a charge, returning a product. Done well, it exposes where the experience breaks. Done badly, it is a colorful mural of the company's own funnel: guessed steps, one happy path, business stages instead of customer tasks. The difference is the input. The gold standard is observational research; interviews and diary studies come second; assumptions never qualify.

Why it matters to the business

Companies see themselves generously. Bain's survey of 362 firms found 80% believed they delivered a superior experience while only 8% of their customers agreed, a gap that inside-out maps preserve rather than close. Journeys are also where the money is: McKinsey found journey performance correlates 30-40% more strongly with customer satisfaction than the performance of individual interactions, and in insurance and pay TV a one-point gain in journey satisfaction matched at least a three-percentage-point higher revenue growth rate.

But the map itself earns nothing. Gartner's 2021 survey found 83% of organizations struggle to use journey maps to identify and prioritize CX efforts. In NN/g's survey of over 300 practitioners, maps scored highest as alignment and education tools, which means the value lives in what teams do next.

How to use it

• Fix one actor and one scenario per map; a map of everyone's journey is a map of no one's.
• Build phases, actions, thoughts, and emotions from primary research; 86% of practitioners in NN/g's survey used customer interviews as the core input.
• If you must start from internal assumptions, follow Forrester's rule: label it a hypothesis map and validate with customers before publishing.
• Include branches, failure states, and contextual differences such as disability or language barriers, not just the happy path.
• Pair the map with a service blueprint that ties each customer pain to the backstage process causing it.
• Commission a map only with a named owner and budget for the resulting fix backlog.

Where teams get it wrong

The classic failure is mapping through the business's eyes: awareness-to-advocacy funnels, stages named after internal handoffs, tasks that happen off your platform ignored. A close second is role-playing personas through the journey instead of researching real customers. Personas indicate needs and likely behaviors, but simulating them step by step manufactures fiction with confident formatting.

Ask your team

• Which of our journey maps led to a funded fix in the last six months, and who owns that backlog?
• What primary research sits behind each step on this map, and when was it last validated with customers?
• Where are the failure states on this map? If there are none, what did we skip?

If the customer achieved their task, the journey succeeded, even if you didn't make money yet.