Home
cd ../playbooks
Product ManagementIntermediate

Customer Journey Map

Build a strategic customer journey map across Awareness → Consideration → Decision → Service → Loyalty — with actions, touchpoints, emotions, KPIs, business goals, and owning teams per stage.

20 minutes
By communitySource
#customer-journey#cx#personas#touchpoints#kpis#cross-functional-alignment

You've got a persona deck, support tickets, and five dashboards — but nobody on your team can agree where customers actually drop off. A journey map forces the conversation: one persona, every stage, emotions attached to metrics, teams attached to stages. The gaps become impossible to ignore.

Who it's for: PMs diagnosing experience breakdowns, CX leaders aligning marketing/sales/support/product, new PMs building empathy with a target segment, PMMs tying messaging to emotional states, Heads of CS preventing post-sale churn

Example

"Map the journey for our B2B SaaS onboarding — from LinkedIn ad through loyalty — with emotions and KPIs per stage" → Full table across 5 stages × 6 rows (actions, touchpoints, experience, KPIs, business goals, teams), pain-point analysis, prioritized opportunities, and a quarterly refresh cadence

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

# Customer Journey Map

Create a comprehensive customer journey map visualizing how customers interact with your brand across all stages—from **Awareness** to **Loyalty**—documenting actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives.

This is not a user flow diagram—it's a strategic artifact that combines customer empathy with business metrics to drive actionable improvements.

## The Mapping Framework (NNGroup + CMU)

**Horizontal (stages):**
- **Awareness:** Customer first learns about your brand
- **Consideration:** Customer evaluates your offering
- **Decision:** Customer makes a purchase
- **Service:** Customer uses the product/service post-purchase
- **Loyalty:** Customer becomes a repeat buyer and advocate

**Vertical (for each stage):**
- **Customer Actions:** What customers do
- **Touchpoints:** Where/how they interact with your brand
- **Customer Experience:** Emotions and thoughts
- **KPIs:** Metrics to measure success
- **Business Goals:** What you're trying to achieve
- **Teams Involved:** Who owns this stage

## What This Is NOT

- **Not a user story map:** Journey maps are broader (all touchpoints, not just product use)
- **Not a service blueprint:** Less detailed on internal processes, more focused on customer experience
- **Not static:** Journey maps evolve as customer behavior changes

## Application

### Step 1: Prepare Prerequisites

Before mapping, ensure you have:
1. **Key stakeholders:** Marketing, sales, product, customer service representatives
2. **Buyer personas:** Detailed personas with demographics, psychographics, goals, challenges
3. **Defined stages:** Main stages of your buying process (typically: Awareness, Consideration, Decision, Service, Loyalty)
4. **Touchpoint inventory:** All places customers interact with your brand

**If missing:** Run discovery interviews, persona definition work, or touchpoint audits first.

### Step 2: Set Clear Objectives

```markdown
## Objectives
- [Goal 1: e.g., "Identify top 3 pain points causing drop-off between Awareness and Consideration"]
- [Goal 2: e.g., "Align marketing and sales on customer motivations at each stage"]
- [Goal 3: e.g., "Understand emotional journey to inform messaging strategy"]
```

**Quality checks:**
- **Specific:** Not "understand customers" but "identify drop-off causes in Consideration stage"
- **Actionable:** Results should inform decisions, not just document observations

### Step 3: Choose a Buyer Persona

Select one persona to focus on (create separate maps for each persona):

```markdown
## Persona
- [Persona name and brief description]
- [Example: "Manager Mike: 35-42, Director of Product at mid-sized B2B SaaS, struggles with data-driven prioritization, values time savings over feature depth"]
```

**Why one persona per map:** Different personas have different journeys. Mixing them creates confusion.

### Step 4: Map Each Stage

For each stage (Awareness, Consideration, Decision, Service, Loyalty), document:

#### Customer Actions
```markdown
### Stage: [Stage Name]

**Customer Actions:**
- [Action 1: e.g., "See LinkedIn ad about product management tools"]
- [Action 2: e.g., "Hear about tool from PM peer at conference"]
- [Action 3: e.g., "Google 'best product roadmap software'"]
```

**Quality checks:**
- **Observable:** You can see or measure this action
- **Specific:** Not "research products" but "Google 'best roadmap software' and read comparison articles"

#### Touchpoints
```markdown
**Touchpoints:**
- [Touchpoint 1: e.g., "LinkedIn Ads"]
- [Touchpoint 2: e.g., "Word-of-mouth at PM conferences"]
- [Touchpoint 3: e.g., "Google organic search results"]
- [Touchpoint 4: e.g., "Review sites (G2, Capterra)"]
```

#### Customer Experience
```markdown
**Customer Experience:**
- [Emotion 1: e.g., "Curious but skeptical—'Is this actually better than spreadsheets?'"]
- [Emotion 2: e.g., "Overwhelmed by options—'Too many tools, how do I choose?'"]
- [Emotion 3: e.g., "Hopeful but cautious—'Could this save me time?'"]
```

**Quality checks:**
- **Authentic:** Use customer quotes from research when possible
- **Emotional:** Capture feelings, not just thoughts
- **Specific:** Not "interested" but "curious but skeptical—worried about setup time"

#### KPIs
```markdown
**KPIs:**
- [KPI 1: e.g., "Brand awareness (measured via surveys)"]
- [KPI 2: e.g., "LinkedIn ad impressions: 100k/month"]
- [KPI 3: e.g., "Organic search traffic: 5k visitors/month"]
- [KPI 4: e.g., "G2 review views: 2k/month"]
```

#### Business Goals
```markdown
**Business Goals:**
- [Goal 1: e.g., "Increase brand awareness among PMs at B2B SaaS companies"]
- [Goal 2: e.g., "Generate 500 qualified leads/month"]
- [Goal 3: e.g., "Position as top 3 roadmap tool in G2 rankings"]
```

#### Teams Involved
```markdown
**Teams Involved:**
- [Team 1: e.g., "Marketing (ad campaigns, SEO)"]
- [Team 2: e.g., "Content (blog posts, comparison guides)"]
- [Team 3: e.g., "Customer Success (case studies, testimonials)"]
```

### Step 5: Visualize the Map

| **Stage** | **Awareness** | **Consideration** | **Decision** | **Service** | **Loyalty** |
|-----------|---------------|-------------------|--------------|-------------|-------------|
| **Customer Actions** | See ad, hear from peers, Google search | Compare features, read reviews, request demo | Free trial signup, test with real data, evaluate ROI | Onboard team, build first roadmap, integrate with Jira | Use daily, recommend to peers, share wins on LinkedIn |
| **Touchpoints** | LinkedIn Ads, conferences, Google, review sites | Website, demo calls, sales emails | Product (free trial), onboarding emails | Product, support chat, knowledge base | Product, community forums, customer success check-ins |
| **Customer Experience** | Curious but skeptical | Excited but overwhelmed by options | Anxious about setup time, hopeful about time savings | Relieved if easy, frustrated if complex | Satisfied and confident, proud of wins |
| **KPIs** | Impressions: 100k/month, traffic: 5k/month | Demo requests: 100/month, trial signups: 50/month | Conversion rate: 20%, time-to-value: <2 hours | Activation rate: 70%, support ticket volume | Retention rate: 85%, NPS: 50, referral rate: 15% |
| **Business Goals** | Increase brand awareness, generate 500 leads/month | Improve lead quality, reduce sales cycle to 30 days | Increase trial-to-paid conversion, optimize onboarding | Reduce churn, improve activation, minimize support costs | Increase LTV, generate referrals, upsell premium features |
| **Teams Involved** | Marketing, Content | Marketing, Sales, Product | Sales, Product, Onboarding | Product, Support, Customer Success | Product, Customer Success, Marketing |

### Step 6: Analyze and Prioritize

Review the map and ask:
1. **Where are the biggest pain points?** (Look for negative emotions + high drop-off rates)
2. **Which stages have the weakest KPIs?** (Prioritize low-performing stages)
3. **Are teams aligned?** (Do teams understand their role in each stage?)
4. **What opportunities exist?** (Where can small improvements create big impact?)

**Prioritization criteria:**
- **Impact:** How much would fixing this improve the customer experience?
- **Feasibility:** How easy is this to fix?
- **Alignment:** Does this support business goals?

### Step 7: Test and Refine

- **Update regularly:** Customer behavior changes—revisit the map quarterly
- **Validate with data:** Use analytics, surveys, and customer interviews to confirm assumptions
- **Track improvements:** After making changes, measure impact on KPIs

## Common Pitfalls

1. **Generic Emotions** — "Customer feels happy" gives no insight. Fix: Be specific — "Relieved that setup took 30 minutes, not 3 hours as feared."
2. **Missing Touchpoints** — Only documenting digital channels. Fix: Include physical, digital, human, and automated.
3. **Internal Perspective** — Mapping what *you* want customers to do. Fix: Validate with customer research, analytics, and support tickets.
4. **No KPIs or Goals** — Actions + emotions but no metrics. Fix: Add measurable KPIs and business goals per stage.
5. **One-and-Done Exercise** — Map created once, never updated. Fix: Review quarterly based on new data, product changes, or market shifts.

## References

- NNGroup, *Customer Journey Mapping* (2016) — Foundational framework
- Carnegie Mellon University, *Product Management Curriculum* — Academic approach
- Chris Risdon & Patrick Quattlebaum, *Orchestrating Experiences* (2018) — Journey mapping for service design
README.md

What This Does

Creates a strategic customer journey map visualizing how one persona interacts with your brand across five stages — Awareness, Consideration, Decision, Service, Loyalty — with six rows per stage (actions, touchpoints, customer experience, KPIs, business goals, teams involved). Identifies pain points, aligns cross-functional teams, and ties emotions to measurable outcomes.

Not a user flow or service blueprint. A strategic artifact combining customer empathy with business metrics.


Quick Start

mkdir -p ~/Documents/JourneyMap
mv ~/Downloads/CLAUDE.md ~/Documents/JourneyMap/
cd ~/Documents/JourneyMap
claude

Provide a persona, objectives, and any existing research (support tickets, analytics, NPS). Claude walks through each stage and produces the full map.


The Six Rows Per Stage

  • Customer Actions — Observable, specific behaviors
  • Touchpoints — All channels (digital + physical + human)
  • Customer Experience — Emotions and thoughts (use real quotes)
  • KPIs — Measurable metrics for this stage
  • Business Goals — Outcome-focused objectives
  • Teams Involved — Cross-functional ownership

Prerequisites Before Mapping

  1. Stakeholders from marketing, sales, product, customer service
  2. Detailed buyer persona (one persona per map)
  3. Defined stages of your buying process
  4. Touchpoint inventory (digital, physical, human, automated)

Missing any of these? Do discovery interviews, persona work, or touchpoint audits first.


Tips & Best Practices

  • One persona per map. Mixing personas creates confusion — build separate maps.
  • Authentic emotions only. Use verbatim customer quotes instead of "customer is happy."
  • Include offline touchpoints. Conferences, word-of-mouth, support calls — not just digital.
  • Outcome-focused goals. Not "run ads" but "increase brand awareness among PMs at B2B SaaS."
  • Review quarterly. Journey maps decay — update based on new research, product changes, market shifts.

Common Pitfalls

  • Generic emotions ("feels happy") that give no actionable insight
  • Only documenting digital touchpoints; missing conferences, referrals, support calls
  • Mapping what you want customers to do, not what they actually do
  • No KPIs or business goals — can't measure success or prioritize
  • One-and-done exercise — map becomes stale as behavior evolves

$Related Playbooks