A visualization of the steps a user takes to accomplish a goal, including their actions, thoughts, emotions, and pain points at each stage. Journey maps align teams around the user experience and highlight opportunities for improvement across the full arc of an interaction.
Common contexts
- Mapping the end-to-end experience of a first-time user from discovery through activation to identify where motivation drops
- Presenting a cross-channel journey to a leadership team to show that UX problems span more than just the app interface
- Workshopping an updated journey map with customer support and engineering to surface friction points outside the product team's view
Use when
Use a journey map when you need to align a cross-functional team — support, engineering, marketing — around a shared understanding of the user experience before prioritizing fixes.
Avoid when
Don't create a journey map from assumptions alone — an artifact built without user research data becomes a story the team tells itself, not a picture of what users actually experience.
The most valuable thing a journey map does is show teams the moments they don't own — the handoffs and gaps between touchpoints where the experience silently falls apart.
Real-world examples
- Rail Europe's journey map revealed that travellers' biggest pain point was the pre-purchase planning phase — not ticketing — redirecting their product investment from checkout optimisation to a better trip planner.
- A UK bank's cross-functional journey-mapping workshop exposed that opening a business account required 7 separate departmental handoffs; the map became the artefact that aligned legal, ops, and design to reduce it to 2.
- IKEA's journey map of the post-purchase assembly experience identified it as the highest emotional low-point for customers, directly motivating the launch of TaskRabbit assembly services in IKEA stores.