Customer Journey Map Template
A customer journey map template covering stages, touchpoints, actions, thoughts, emotions, pain points, and opportunities — with a product implications section. Free to copy, download, and use. No signup required.
# Customer Journey Map **Persona:** [Name of the persona this map is for] **Scenario:** [What the customer is trying to accomplish — e.g. "Onboarding and getting first value from PMRead"] **Author:** [Name] **Date:** [Date] **Based on:** [N interviews / usability sessions / support data] --- ## Journey Stages > Define 4–7 stages that cover the customer's end-to-end experience. | Stage | [Stage 1] | [Stage 2] | [Stage 3] | [Stage 4] | [Stage 5] | |---|---|---|---|---|---| | **Name** | Awareness | Consideration | Onboarding | First Value | Retention | | **Goal** | [What the customer is trying to do] | | | | | --- ## Touchpoints > Where does the customer interact with your product, brand, or team at each stage? | Stage | Touchpoints | |---|---| | [Stage 1] | [Website, ad, word of mouth, review site] | | [Stage 2] | [Demo, trial signup, pricing page, comparison sites] | | [Stage 3] | [Welcome email, in-app onboarding, docs] | | [Stage 4] | [Core feature, first "aha moment"] | | [Stage 5] | [Email, in-app nudges, support, renewal] | --- ## Actions, Thoughts & Emotions ### [Stage 1: Awareness] **Actions** (what the customer does): - [Action 1] - [Action 2] **Thoughts** (what they're thinking): - "[Quote or paraphrase from research]" **Emotions** (how they feel): 😐 Neutral / 😕 Frustrated / 😊 Hopeful / 😟 Anxious / 😄 Delighted Emotional intensity: ▁▂▃▄▅ [mark the level] --- ### [Stage 2: Consideration] **Actions:** - [Action] **Thoughts:** - "[Quote]" **Emotions:** [Feeling] — Intensity: ▁▂▃▄▅ --- ### [Stage 3: Onboarding] **Actions:** - [Action] **Thoughts:** - "[Quote]" **Emotions:** [Feeling] — Intensity: ▁▂▃▄▅ --- ### [Stage 4: First Value] **Actions:** - [Action] **Thoughts:** - "[Quote]" **Emotions:** [Feeling] — Intensity: ▁▂▃▄▅ --- ### [Stage 5: Retention] **Actions:** - [Action] **Thoughts:** - "[Quote]" **Emotions:** [Feeling] — Intensity: ▁▂▃▄▅ --- ## Pain Points by Stage | Stage | Pain Point | Severity (1–5) | Source | |---|---|---|---| | [Stage] | [Specific friction the customer experiences] | [1–5] | [Interview / support ticket / analytics] | | | | | | --- ## Moments of Truth > The 2–3 moments where the customer's relationship with your product is won or lost. 1. **[Moment name]** — [Stage] — [Why this moment is critical and what determines success] 2. **[Moment name]** — [Stage] — [Description] 3. **[Moment name]** — [Stage] — [Description] --- ## Opportunities | Stage | Opportunity | Priority | Owner | |---|---|---|---| | [Stage] | [What we could do to improve this stage] | High / Med / Low | [Team] | | | | | | --- ## Product & Design Implications | Finding | Implication | Recommended action | |---|---|---| | [Key insight from map] | [What this means for product design] | [What to build or change] | | | | |
How to use this Journey Map template
Map one persona and one scenario at a time
A journey map that tries to cover all users and all journeys covers nothing. Pick your primary persona and their most important job. Create separate maps for meaningfully different journeys.
Ground every row in real research
Journey maps built from assumptions are fiction. Mark each row with its source — interview quote, support ticket, analytics event. If a cell can't be backed by evidence, that's a research gap, not a fact to invent.
Focus on the Moments of Truth
Three moments determine whether a customer stays or churns. Finding and naming these moments is the most valuable output of a journey map. Once identified, instrument them analytically and invest disproportionately in making them excellent.
Use it in cross-functional workshops
A journey map is most valuable when built collaboratively with design, support, and sales in the room. Support knows where customers fail; sales knows where they hesitate; design knows where they get confused. None of these are visible to the PM alone.
Want a Journey Map grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
What's the difference between a customer journey map and a service blueprint?
A customer journey map shows the customer's experience — what they do, think, and feel. A service blueprint goes deeper, mapping the front-stage (customer-visible) and back-stage (internal processes) that deliver that experience. Start with the journey map; build a service blueprint if you need to redesign operations, not just UX.
How many stages should a journey map have?
4–7 stages is the sweet spot. Fewer than 4 is too abstract to be actionable. More than 7 becomes hard to read and usually means you've zoomed in too close to one part of the journey. Common stage patterns: Awareness → Consider → Onboard → Use → Retain, or Discover → Trial → Activate → Adopt → Expand.
Should journey maps be current-state or future-state?
Build current-state first — it documents reality and reveals opportunities. Then build a future-state map to articulate where you're taking the experience. The gap between them is your product roadmap. Never start with future-state alone; it produces aspirational fiction rather than grounded design.
How do I validate a journey map?
Walk through it with 3–5 customers and ask 'does this reflect your experience?' at each stage. You'll quickly discover where the map is wrong or incomplete. Also compare the pain points and moments of truth against your analytics — if a moment of truth isn't measurable, add instrumentation.
Other free templates