Journey Mapping Template
Reusable structure for mapping any part of a system from user need to validated outcome.
A journey map traces a user's path through the system from an initial need to a resolved outcome. It connects individual features into a coherent narrative and exposes gaps, friction points, and opportunities that are invisible when features are designed in isolation.
The Journey Map Structure
Every journey map contains six sections:
1. Context
A brief description of who the user is, what triggers the journey, and what success looks like.
2. Journey Table
The step-by-step path through the system, including:
- Step number and name
- User action: What the user does
- System response: What the system does in response
- Touchpoint: The specific page, component, or notification involved
- Emotional state: The user's likely emotional state at this step (confident, uncertain, frustrated, satisfied)
- Failure mode: What could go wrong at this step
- Recovery: How the system helps the user recover from failure
3. Critical Moments
The 2-4 steps where the journey is most likely to succeed or fail. These are the points that deserve the most design attention and testing.
4. Validation Checklist
The four-pillar validation applied specifically to this journey's critical moments.
5. Open Questions
Unresolved questions about the journey that need research, testing, or stakeholder input to answer.
6. Linked Artifacts
References to related decisions, personas, principles, and page-tree entries.
Full Markdown Template
# Journey: [Journey Name]
**ID**: JOURNEY-[NNN]
**Persona**: [Link to persona in PERSONAS.md]
**Trigger**: [What initiates this journey]
**Success Outcome**: [What "done" looks like for the user]
**Last Updated**: YYYY-MM-DD
**Status**: Draft | In Review | Validated
## Context
[2-3 sentences describing the scenario. Who is the user?
What do they need? What are the constraints?]
## Journey
| Step | User Action | System Response | Touchpoint | Emotional State | Failure Mode | Recovery |
|---|---|---|---|---|---|---|
| 1. [Name] | [What user does] | [What system does] | [Page/component] | [Emotion] | [What could go wrong] | [How to recover] |
| 2. [Name] | | | | | | |
| 3. [Name] | | | | | | |
| 4. [Name] | | | | | | |
| 5. [Name] | | | | | | |
## Critical Moments
### Critical Moment 1: [Step N — Name]
- **Why this matters**: [Why this step is make-or-break]
- **Design priority**: [What to focus on]
- **Testing approach**: [How to validate this step works]
### Critical Moment 2: [Step N — Name]
- **Why this matters**: [...]
- **Design priority**: [...]
- **Testing approach**: [...]
## Validation Checklist
### Clarity
- [ ] Each step's purpose is obvious to the user
- [ ] Progress through the journey is visible
- [ ] The user always knows what to do next
### Attribution
- [ ] Any data shown during the journey has a clear source
- [ ] Recommendations or suggestions explain their basis
### Reversibility
- [ ] The user can go back to any previous step
- [ ] Partial progress is saved automatically
- [ ] The user can abandon the journey without penalty
### Consistency
- [ ] Each step follows the application's established patterns
- [ ] Terminology is consistent throughout the journey
- [ ] Visual treatment matches the design system
## Open Questions
- [ ] [Question 1]
- [ ] [Question 2]
- [ ] [Question 3]
## Linked Artifacts
- **Decisions**: [DEC-NNN, DEC-NNN]
- **Principles**: [PRIN-NNN]
- **Page Tree**: [Routes involved in this journey]
- **Sprint**: [Sprint(s) that addressed this journey]Worked Example (Skeleton)
A brief skeleton showing the template applied to a "sign-up to onboarded" journey:
| Step | User Action | Touchpoint | Failure Mode | Recovery |
|---|---|---|---|---|
| 1. Discovery | Arrives at landing page | Landing page | Value prop unclear | A/B test headlines |
| 2. Sign-up | Clicks "Start Free Trial" | Sign-up form | Form too long | Reduce to essential fields |
| 3. Verification | Clicks email link | Email not received | Resend option, magic link | |
| 4. First action | Completes guided core feature | Core feature page | Guidance insufficient | Quick-start + detailed options |
Critical moments: Step 2 (highest-intent, friction = abandonment) and Step 4 (the "aha moment" — time-to-value predicts retention).