Zoom out, zoom in – Journeys and flows

A journey map is the whole story of someone’s relationship with your product, told like a story – across channels, over weeks or months, with how they felt mapped alongside what they did. A user flow is the literal, click-by-click path through your actual screens to get one specific thing done, over minutes. One zooms out; one zooms in.

Confusing them is a common, costly mistake – bringing a journey-shaped question (“why do people churn after month two?”) to a flow-shaped artefact (a diagram of the sign-up form) won’t answer it, because the answer probably lives outside the product entirely: in support interactions, pricing confusion, a competitor’s email. The reverse fails just as precisely – “why do people abandon this form?” needs the screen-level view, and a journey map is too far away to see it.

Zoomed out – one user, six weeks

A journey map: channels, time, feeling. Pick a touchpoint to zoom in

Hears about itfriend’s messageSigns upappFirst budget setappCard sync breaksappSupport threademailRenewal decisionbilling

week 1week 6

The whole family, by altitude

• Journey map – highest altitude. Multiple channels (app, email, support call, billing), timeframe of days to months, emotion tracked at every step. Nielsen Norman Group’s definition: a scenario-based sequence of steps toward “a high-level goal with a company or product, usually across channels and over time”.
• User flow – inside one product, one task, minutes not months, no emotion track: steps and system responses.
• Task flow – a user flow stripped to the single ideal path, no branches. Its job is fast alignment on “what’s the happy path” before anyone argues edge cases.
• Screen flow – a flow rebuilt from actual screens or mockups, once structure and visual direction are both settled. The most literal, walkable map – and a late-stage artefact for exactly that reason.

The memory aid that carries the relationship: the journey tells you what to fix; the flow tells you how to fix it. A journey map surfaces the friction point in the relationship; a flow is where that friction gets diagnosed at the level of actual screens.

When each is overkill

A full journey map for a well-understood feature tweak is theatre – that’s a flow-sized question. A flow diagram for a churn problem answers the wrong question precisely. And the failure mode worth watching for in real teams: a beautifully produced journey map presented after the decision was already made. That’s a diagnostic tool demoted to decoration – the tell is that nothing in the map could have changed the decision.