Dean Peters Journey Mapping
What Is It
Visually synthesize and communicate a user’s end-to-end experience through actions, pain points, wins, and opportunities in a phased process.
Why Use It
Quickly create a shared vision of the user’s experience from end-to-end, in a way that is inclusive of all contributors Use storytelling to visualize information in a concise and memorable way to spur collaborative conversation.
When to Use It
When identifying bottlenecks and opportunities in a process to improve the user experience, target specific customers, or make sense of interview data.
How to Do It
- Establish the “why and the “what.” Answer key questions before beginning the process: What goal does this journey map support? Who will use it? Who is it about and what experience does it address? How will it be shared?
- Gather existing research and base this exercise on truthful narratives. This is a qualitative-research process to tell the complete story. Ask about the actions involved, pain points, wins or successes, and opportunities.
- Collaborate with others; the exercise of filling out the journey map (not the output itself) is often the most valuable part of the process. Invite stakeholders to contribute to compiling the data and building the map. This should be a very inclusive activity, with a diverse collection of participants who each bring different perspectives and experiences.
- Synthesize the data before moving on to creating the visual.
- Engage others with the end product and solicit feedback.
Key Concepts
Journey Phases — The sequential stages a user moves through to accomplish a goal, from initial trigger to outcome. Defining clear, mutually exclusive phases prevents the map from becoming an unstructured list and anchors where opportunities live.
Emotional Curve — The plotted highs (wins) and lows (pain points) of the user's emotional state across phases. It reveals the moments that matter most and where intervention will have outsized impact on perceived experience.
Pain Points & Opportunities — Specific friction the user encounters and the corresponding solution spaces those frictions open up. Each pain point should map to a candidate opportunity that can later become a backlog item or hypothesis to test.
Moments of Truth — The critical interactions that disproportionately shape whether a user continues, abandons, or advocates. Identifying them focuses scarce product investment on the touchpoints that determine success or failure.
Evidence-Based Narrative — Grounding the map in real qualitative research rather than internal assumptions. An assumption-driven map manufactures false consensus and produces requirements that solve problems users don't actually have.
Current vs. Future State — Distinguishing the experience as it exists today from an aspirational redesigned experience. Conflating the two hides real friction and lets teams skip past validating today's actual problems.
PM Applications
- Translate raw discovery and interview findings into a synthesized artifact that feeds the problem statement and context sections of a PRD.
- Surface and rank opportunity areas during roadmap reviews so that investment maps directly to validated user pain rather than stakeholder opinion.
- Generate and prioritize backlog items by converting each mapped pain point and opportunity into candidate epics or user stories.
- Anchor OKR planning by tying key results to measurable improvements at specific high-friction journey stages.
- Drive a stakeholder briefing or executive presentation that builds shared understanding and consensus around where the experience is breaking down.
- Pair with funnel or conversion analytics in quarterly reviews to correlate quantitative drop-off with the qualitative reasons behind it.
Benefits
- Creates a one-source visual for a process from a user’s perspective Flexible categories depending on what you’d like to capture Output can be used to tell a story, build consensus or define requirements
Common Pitfalls
- Building the map from internal assumptions instead of real user research, producing a polished artifact that fabricates consensus around problems that don't exist.
- Treating the finished visual as the deliverable rather than the collaborative synthesis, so the team loses the shared understanding that is the real value.
- Mapping an idealized future state while skipping the messy current state, which hides the actual friction the product needs to fix.
- Defining phases too broadly or inconsistently, flattening the map so pain points cluster vaguely and no actionable opportunities emerge.
- Stuffing the map with every persona at once instead of one specific user, creating an averaged journey that reflects no real person's experience.
- Ending at the visual without converting pain points and opportunities into prioritized backlog items, so insights never reach the roadmap.
Combine With
Personas to define the user perspective from which you’d like to view a process Service Blueprint to map out the backstage actions happening behind-the-scenes
Assets
- PDF: Download
- Markdown Template: template.md
Metadata
| Field | Value |
|---|---|
| ITK Phase | UNDERSTAND |
| Difficulty | Advanced |
| Group Size | 4+ people |
| Time Required | 45+ minutes |
| Source | itk.mitre.org |