research methods
Customer journey mapping
What is a customer journey map, and how is it different from a user journey?
A customer journey map charts the whole relationship a person has with a brand over time and across channels - from first awareness through consideration, purchase, onboarding, support and (you hope) loyalty - plotting their actions, thoughts and emotions at each stage. It zooms out from a single task to the end-to-end experience, exposing the emotional highs and lows the rest of the organisation rarely sees joined up.
Also known as: customer journey map, customer journey mapping, journey map, experience map
The demo
One customer, the whole relationship - from first hearing of you to (hopefully) loyalty. Click each stage to see how they feel, and watch the curve reveal where it all goes wrong.
What this demo shows (text version)
A customer journey is plotted across lifecycle stages - awareness, consideration, purchase, onboarding, support and loyalty - with an emotion curve showing how the person feels at each. Clicking a stage reveals their action, thought and feeling there. The curve rises with an exciting purchase, then dips sharply at onboarding, where marketing has handed over to the product and the person is left confused, before support slowly recovers it.
That dip is the point. A customer journey map zooms out from any single task to the whole relationship across channels, and its emotion curve exposes the valleys - usually at the handoffs between teams that no one department sees end to end. It differs from a user journey (which maps one task in one product) by its lifecycle scope, and it's most useful, built from real research, as a shared map for fixing those low points.
A customer journey map is the wide-angle view: the full lifecycle across every touchpoint and channel, not one task in one product. Its job is to surface the emotional lows - the "valleys", often at handoffs between teams - where people drop out, and to give a whole organisation one shared picture of an experience that's usually owned in disconnected pieces. Map it from real research, and act on the dips.
Plotted as one curve, the journey told a story a feature-by-feature view never could: a confident start, then a sharp emotional dip right where marketing hands over to the product, and support left to rescue it. That valley - invisible to any single team - is exactly where the experience is won or lost, and exactly what a journey map is for.
The difference from a user journey is scope. A user journey (or user flow) maps the steps of a specific task inside a product; a customer journey map zooms out to the entire relationship - pre-purchase marketing, the buying decision, delivery, onboarding, support, renewal - across every channel and over weeks or months. One is a task lens; the other is a lifecycle lens.
Its signature is the emotion curve. Mapping how people feel at each stage reveals the lows - the moments of frustration and the cliff-edges where they abandon - which cluster, tellingly, at the handoffs between teams and systems (sales to product, product to support). Those seams are owned by no one and felt by everyone, which is why no single team spots them.
It's most valuable as an alignment artefact built from evidence. Grounded in real research it gives an organisation one shared, end-to-end view to rally around and prioritise against; invented from assumptions it's a pretty poster that launders guesses. Map the journey that exists, mark the valleys, and turn them into a list of things to fix - not a wall decoration.