What is a customer journey map and is it actually useful?
A customer journey map is a visual representation of the stages a person goes through when interacting with a business — what they do, think and feel at each point, across every channel.
What a map typically contains:
Stages, from first awareness through consideration, purchase, onboarding, use and renewal or repeat.
Touchpoints at each stage — the specific interactions: an advert, a search result, a review site, the website, an email, a support call, the product itself.
Actions the customer takes.
Thoughts and questions they have at each point.
Emotions, often plotted as a line showing where frustration peaks.
Pain points and opportunities.
Ownership, which is the part most maps omit and the part that makes them actionable — which team is responsible for each touchpoint.
Why it can be genuinely useful. Organisations are structured by function — marketing, sales, product, support — while customers experience one continuous sequence. The gaps between departments are invisible from inside and highly visible from outside. A journey map is one of the few artefacts that makes those handovers legible, and the most common finding is that the worst experiences occur precisely where responsibility changes hands.
It also creates a shared reference so teams argue about the same thing.
Why most journey maps are useless:
They are invented. A map assembled in a workshop from assumptions documents what the team believes, not what customers do. It then lends those assumptions false authority. Maps should be built from research — interviews, support logs, analytics, session recordings, sales call notes.
They are idealised, showing the intended path rather than the messy real one with its loops, abandonment and returns.
They describe a single mythical customer, when different segments behave very differently.
They are produced once and never updated.
They end at purchase, ignoring the stages where retention is actually decided.
No decision follows. A map that does not change a priority, a budget or a process was a documentation exercise.
A useful test: what will you do differently tomorrow?