What it is
A visual map of the end-to-end experience across touchpoints, channels, and time, showing actions, thoughts, emotions, and pain points at each stage of a defined scenario.
Why use it
Journey maps expose experience gaps invisible from one touchpoint, align teams around the user's experience, and give a shared basis for prioritizing.
Use this when
- You have research to synthesize into a shared experience view
- The team must align on the current experience before scoping
- The initiative spans several touchpoints, channels, or teams
- A communication artifact is needed to build empathy
You may not need this when
- The scope is one isolated interaction
- A recent, validated map of this scenario exists
- Research is too thin: the map would rest on assumptions
Dependencies — what you need
- Synthesized research to ground the map
- A defined scenario, persona, or segment
- Cross-functional participation to validate
- Collaboration tools (e.g., FigJam, Miro)
People involved
- Design
- Research
- Product
- Engineering
- Customer Success / Support
Typical outputs
- A current-state map, each cell marked evidence or assumption
- Pain points and friction by stage
- An optional emotional arc, only if participants rated each stage
- Opportunity areas, as hypotheses
Template
Journey Mapping template
A fill-in structure for running this method: what to prepare, what to do, what to record, and how to read the result.
How AI can help
AI as augmentation — not replacement
- Draft stages and touchpoints from research notes
- Pull thoughts and feelings only from quoted excerpts, with sources
- Find patterns and contradictions across stories
- Suggest opportunities from pain points, as hypotheses
AI prompt
A prompt for any AI assistant. It works only from material you paste in, keeps assumptions apart from findings, and leaves the decisions to you.