Customer Journey Map

A journey map has a standard anatomy, and each row answers a different question.

Across the top run the stages — the phases of the journey in order. A common set is awareness, consideration, purchase, onboarding, use, renewal, though the right ones are whatever the customer actually goes through rather than a template.

Underneath, one row per lens. Actions: what they physically do. Thoughts: what they are trying to work out. Emotions: how they feel, usually drawn as a line. Touchpoints: where the interaction happens — app, email, phone, a colleague. Pain points: what goes wrong. And often opportunities: what could be done about it.

The rows matter because they surface different problems. Actions alone give you a flowchart. Emotions alone give you sympathy with no mechanism. Read together, they show where a feeling was produced by which touchpoint, which is the thing you can act on.

Not every moment in a journey carries the same weight. A few interactions do most of the work of deciding whether someone stays, and they are frequently not the ones receiving the most attention.

The emotion curve is how you find them. Plot how the customer feels across the stages and look at where the line turns — the sharp drops and the sharp recoveries. Those turning points are moments of truth: interactions that disproportionately shape how the whole relationship is remembered.

They are rarely evenly distributed. One map found the steepest drop not at sign-up, which the team had been optimising for a year, but at the first invoice — where a surprise charge arrived with no warning email.

This kind of moment is invisible in funnel data, and that is the important part. Nobody dropped out at the invoice. They simply stopped trusting the product and left two months later, at which point the churn was attributed to something else entirely.

The practical use is prioritisation. Effort spent at a moment of truth is worth several times the same effort spent on a stage where nothing much is being decided — and a journey map is the cheapest way to find out which is which, because the alternative is inferring it from behaviour that happens months downstream.

A journey map that ends as a poster has failed. The output is not the diagram; it is a short list of changes that would not have been obvious without it.

Getting there is mostly a matter of turning observations into owned work. For each significant pain point, name the moment, the evidence that it is real, the change you would make, and one person accountable for it. Pain points with no owner are decoration, and there is usually one per map that everyone agrees about and nobody schedules.

Prioritise by the emotion curve rather than by how easy something is to fix. The steepest drop is where the leverage is, even when the shallow dips have tidier solutions.

And expect the highest-value fixes to be unglamorous. One map identified a surprise charge as the sharpest drop in the journey; the fix was a scheduled email a week beforehand. No redesign, no new screen, no engineering quarter. It simply removed a surprise, and it moved retention more than the sign-up work that had occupied the previous year.

The test of whether a map was worth making is blunt: did anything get built, or unbuilt, that would not have otherwise? If the answer is no, you produced an artefact, and the next one will be harder to get people to attend.