Customer Journey Mapping
Visualize the end-to-end customer experience - mapping touchpoints, emotions, and pain points across awareness, consideration, purchase, and retention stages.
skill: Customer Journey Mapping category: Product tags: [Customer Journey, UX, Empathy Map, Touchpoints, Product] readingTime: 5
A journey map is only as good as the research behind it. Invented journey maps based on assumptions are as dangerous as no map - they create false confidence. Build from user interviews, session recordings, and support data. The best journey maps reveal handoff problems between teams that no single team can see from their vantage point.
Workflow
- Define the persona and scenarioOne journey map can't represent all users. Focus on one persona in one scenario - the map for 'enterprise buyer evaluating the product' is completely different from 'daily active power user'.
- Map journey stages and touchpointsStages organize the journey into phases the customer experiences sequentially - touchpoints are where they interact with your company in each stage.
- Add emotional arc and pain pointsMapping the customer's emotional state reveals moments of frustration and delight - the frustrations are problems to solve; the delights are moments to amplify.
- Identify opportunitiesThe journey map's value is in revealing where to invest - emotional lows signal the highest-impact problems to solve.
- Share and activate across teamsA journey map that lives in Miro and is never referenced again has no impact. Activation means every team sees which part of the journey they own.
Output Format
Journey map: stages, touchpoints, emotional arc, pain points, and prioritized opportunities with team owners.
Customer Journey: Sarah (Sr. Data Analyst) → First 90 days
Stage | Touchpoints | Emotions | Pain Points | Opportunities
Awareness | Search, G2 | Neutral | Hard to find comparison | SEO comparison pages
Consideration | Trial | Positive → Frustrated | Form too long | Social login
Onboarding | Setup wizard | Frustrated | IT blocker | SSO + SCIM
Adoption | Daily use | Delighted | N/A | Amplify first aha momentExamples
Input
Output
Edge Cases & Gotchas
- Multiple personas, one map - Mapping buyer persona (economic decision maker) and user persona (daily user) on the same map creates confusion - they have different journeys. Map separately, then overlay handoffs.
- Journey map vs. service blueprint - A journey map is from the customer's perspective; a service blueprint adds the behind-the-scenes processes that enable each touchpoint. Build the map first, then extend to a blueprint.
- Assumption-based maps - A journey map built without user research is a hypothesis, not a finding. Label assumptions as '[ASSUMED]' and prioritize validating them before building solutions around them.
- Too much detail - A journey map that tries to capture every micro-interaction becomes unreadable. Focus on the moments that matter most: biggest drops in emotion and highest-frequency touchpoints.
When to Break These Rules
- Use a Jobs To Be Done framework instead of journey mapping when the product is very early and the question is 'what problem are we solving?' rather than 'how do we improve the current experience?'
- Use funnel analytics instead of journey mapping for data-rich products where quantitative drop-off data reveals the problem location - journey maps add context to what analytics reveal.
Reference Files
https://www.nngroup.com/articles/customer-journey-mapping/https://www.interaction-design.org/literature/article/customer-journey-maps