Mara logo

Customer Journey Map

A visualisation of everything a customer does, thinks and feels across the whole relationship with a company, including steps outside the product.

Deliverables & Artifacts

A journey map covers the full arc — noticing a problem, searching, comparing, buying, onboarding, using, renewing, leaving — and records the channels involved at each stage: ads, sales calls, the app, support, invoices. This is what distinguishes it from a user flow, which stays inside the interface and describes one task.

Its purpose is to make handoffs visible. Most bad customer experiences are not caused by a bad screen; they are caused by the gap between two teams that each did their part well. A map earns its keep when it is built from research and shows one thing nobody in the room knew, rather than confirming the process diagram that already existed.

In practice

A healthcare product mapped the clinician journey and found the worst moment was not in the app at all: credentials arrived by post, days after the account was created. Before: onboarding measured from first login. After issuing access at signup, time-to-first-use fell from nine days to under one. The catch — the fix belonged to operations, not design.

Learn more

You may ask

Frequently Asked Questions

How is a journey map different from a user flow?

Scope. A user flow shows the screens and decisions inside one task; a journey map spans channels and time, including everything that happens before someone opens the product and after they close it.

Do we need research to build one?

Yes, or it becomes a diagram of internal assumptions with emotions added. A workshop map is a useful starting hypothesis, but it should be labelled as one until interviews or analytics confirm the stages and the pain points.

Related terms

All terms

Let's talk about your product.

Happy to look at what you're building and say where design would move the needle.

Contact Us