User journey map

A journey map shows one person’s experience of achieving a goal over time, across every channel involved. Typical rows are the stages, what the person does, what they think, what they feel, the touchpoints, and the pain points.

How it differs from a user flow

A user flow covers one product and one path through it. A journey map covers everything: the search that started it, the phone call, the email, the visit, the follow-up. It usually spans days or weeks rather than minutes.

That wider frame is what makes it useful, because most of the moments that determine whether someone is satisfied happen outside the product.

What it is really for

Making ownership gaps visible. Every department owns its step; nobody owns the sequence. A journey map put on a wall with the failures marked usually shows that the worst moments sit exactly at the handoffs between teams.

That is an organisational finding presented as a design artefact, which is often the only form in which it gets heard.

Where they go wrong

Journey maps built from assumptions rather than research. A map is only as good as the evidence behind each row, and “what they feel” invented in a workshop is decoration.

In practice

Mark the moments where responsibility changes hands. That is where the experience breaks, reliably, and it is the shortest route from map to action.