Customer Journey Mapping

Why Journey Maps Matter

From Siloed to Holistic

Without Journey Map:
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Marketing│ │ Product  │ │ Support  │
│  Focus   │ │  Focus   │ │  Focus   │
└──────────┘ └──────────┘ └──────────┘
     │            │            │
     ▼            ▼            ▼
  Fragmented view of experience

With Journey Map:
┌─────────────────────────────────────┐
│         User's Complete             │
│         Journey                     │
│  ┌─────┬─────┬─────┬─────┬─────┐  │
│  │Aware│Consd│Purch│Onboard│Use │  │
│  └─────┴─────┴─────┴─────┴─────┘  │
│       Seen by all teams           │
└─────────────────────────────────────┘

Benefits

Strategic:

• Aligns teams around user needs
• Identifies gaps in experience
• Reveals innovation opportunities
• Prioritizes initiatives

Tactical:

• Highlights friction points
• Shows where to focus research
• Guides design decisions
• Measures experience improvements

Types of Journey Maps

1. Current State Map

Purpose: Document existing experience

Focus: What currently happens
Use: Identify pain points, quick wins
Data: User research, analytics, support tickets
Output: Baseline understanding

2. Future State Map

Purpose: Envision ideal experience

Focus: What should happen
Use: Strategic planning, vision setting
Data: Innovation workshops, best practices
Output: North star experience

3. Day in the Life

Purpose: Understand broader context

Focus: User's entire day, not just product use
Use: Identify unmet needs, new opportunities
Data: Diary studies, ethnography
Output: Contextual understanding

4. Service Blueprint

Purpose: Show frontstage and backstage

Focus: User actions + organizational processes
Use: Operational improvements, service design
Data: Cross-functional input
Output: Complete service view

See also: [Service Blueprinting](/articles/service-blueprint)

Anatomy of a Journey Map

Core Components

┌───────────────────────────────────────────────────────┐
│  LENS: Persona + Scenario + Expectations              │
├───────────────────────────────────────────────────────┤
│                                                       │
│  PHASE 1 → PHASE 2 → PHASE 3 → PHASE 4 → PHASE 5     │
│                                                       │
├───────────────────────────────────────────────────────┤
│  ACTIONS: What is the user doing?                    │
│  ──────────────────────────────────────────────────  │
│  THOUGHTS: What are they thinking?                   │
│  ──────────────────────────────────────────────────  │
│  EMOTIONS: How are they feeling? 😊😕😤😃            │
│  ═══════════════════════════════════════════════════ │
│  TOUCHPOINTS: Channels and interactions              │
│  ──────────────────────────────────────────────────  │
│  PAIN POINTS: Frustrations and barriers              │
│  ──────────────────────────────────────────────────  │
│  OPPORTUNITIES: Ideas for improvement                │
│                                                       │
└───────────────────────────────────────────────────────┘

Detailed Components

1. The Lens

Persona: Who is this journey about?
Scenario: What situation are they in?
Expectations: What do they anticipate?
Goals: What are they trying to achieve?

2. Phases

High-level stages of the journey:
• Awareness: Discovering the need
• Consideration: Evaluating options
• Purchase: Making the decision
• Onboarding: Getting started
• Usage: Regular use
• Support: Getting help
• Renewal/Advocacy: Continuing/expanding

3. Actions

Specific steps users take:
• Search for solution online
• Compare pricing options
• Sign up for free trial
• Invite team members
• Configure settings
• Run first report

4. Thoughts

User's internal monologue:
• "Is this secure enough?"
• "How does this compare to Competitor X?"
• "Can I import my existing data?"
• "What if I need help?"

5. Emotions

Emotional journey (charted):
😊 High ──────────────────────┐
    │          ╱╲            │
    │    ╱╲   ╱  ╲    ╱╲     │
    │   ╱  ╲ ╱    ╲  ╱  ╲    │
    │──╱────╳──────╳╱────╲───│
    │       ╱      ╱          │
😞 Low ──────────────────────┘
    Phase1  Ph2   Ph3   Ph4

6. Touchpoints

Channels of interaction:
• Website
• Mobile app
• Email
• Support chat
• Phone call
• Social media
• In-store/physical

7. Pain Points

Problems users encounter:
• Can't find pricing
• Confusing navigation
• Slow load times
• Unclear error messages
• Too many steps
• Missing features

8. Opportunities

Potential improvements:
• Add live chat to pricing page
• Simplify checkout process
• Create getting started guide
• Add progress indicators
• Provide templates

Creating a Journey Map

Step 1: Define Scope

Questions to answer:
□ Who is the persona?
□ What is the scenario?
□ What are the boundaries?
□ What are the goals?

Example:
"Sarah the Marketing Manager 
purchasing analytics software 
for her team of 5"

Step 2: Gather Research

Qualitative:

• User interviews
• Contextual inquiry
• Diary studies
• Support ticket analysis
• Sales call recordings

Quantitative:

• Analytics (funnels, paths)
• Survey data
• Heatmaps
• Session recordings
• Usage metrics

Step 3: Create Affinity Map

Organize research findings:

Sticky notes by phase:
┌─────────┬─────────┬─────────┬─────────┐
│ Awareness│ Consider│ Purchase│ Onboard │
├─────────┼─────────┼─────────┼─────────┤
│ • Finds │ • Reads │ • Signs │ • Gets  │
│   via   │   reviews│  up     │   email │
│   search│ • Compares• Enters │ • Clicks│
│ • Sees  │   3     │   cc    │   link  │
│   ad    │   options│ • Gets  │ • Stuck │
│         │         │   welcome│   on    │
│         │         │   email │   step 3│
└─────────┴─────────┴─────────┴─────────┘

Step 4: Sketch the Journey

Draft version (low-fidelity):

Phases:   Search → Compare → Sign up → Setup → First use

Actions:  Google → Reviews → Form    → Config → Import

Thoughts: "Best?"→ "Price?"→ "Safe?" → "Help?"→ "Works?"

Emotions:  😐     →  😕     →  😰    →  😤    →  😊

Pain pts:  ────   →  ────   →  Too   →  No    →  Success!
                         long    guide

Step 5: Refine and Visualize

Digital tools:

• Figma / FigJam
• Miro
• Mural
• Lucidchart
• Smaply
• UXPressia

Structure:

Top: Persona photo, name, scenario
Middle: Timeline with phases
Rows: Actions, thoughts, emotions, touchpoints
Bottom: Pain points, opportunities

Step 6: Validate and Share

Validation:
□ Review with actual users
□ Check with customer-facing teams
□ Verify with data
□ Get stakeholder input

Sharing:
• High-resolution image
• Interactive digital version
• Printed for workshops
• Presentation summary

Journey Map Templates

Simple Map (B2C)

┌─────────────────────────────────────────────────────┐
│ Persona: Busy Parent Shopping Online               │
│ Goal: Buy birthday gift in under 10 minutes        │
├─────────────────────────────────────────────────────┤
│                                                     │
│ DISCOVER    BROWSE      DECIDE      BUY      RECEIVE│
│                                                     │
│ Search      Filter      Read        Enter    Track │
│ Google      options     reviews     info     order │
│             products                        status │
│                                                     │
│ "Need      "So        "Is this     "Hope   "Will   │
│  gift"      many..."   good?"      secure"  arrive?"│
│                                                     │
│ 😊          😕          😐          😰       😊      │
│                                                     │
│ [Phone]    [Website]   [Website]   [App]    [Email]│
│                                                     │
│ PAIN: Too  PAIN: No    PAIN: Not   PAIN:    PAIN:  │
│ many ads   filtering   sure of     Hidden   No     │
│            by price    quality     fees     updates│
│                                                     │
│ OPP:       OPP:        OPP:        OPP:    OPP:    │
│ Gift       Price       Reviews     Show     SMS    │
│ guide      slider      with        total    notif  │
│            photos                  upfront          │
└─────────────────────────────────────────────────────┘

Detailed Map (B2B)

┌──────────────────────────────────────────────────────┐
│ Multiple swimlanes for:                              │
│ • User actions                                       │
│ • Frontstage (visible) interactions                  │
│ • Backstage processes                                │
│ • Support systems                                    │
│ • Emotional state                                    │
└──────────────────────────────────────────────────────┘

Using Journey Maps

For Design Decisions

Before designing new feature:
□ Where does it fit in the journey?
□ What phase pain point does it address?
□ How does it affect adjacent touchpoints?
□ What emotions should it create?

For Prioritization

Opportunity scoring:
• Impact on pain points (1-5)
• Frequency of issue (1-5)
• Feasibility to fix (1-5)
• Strategic alignment (1-5)

Priority = Impact × Frequency × Alignment / Complexity

For Alignment

Cross-functional workshops:
• Journey mapping sessions
• Pain point prioritization
• Solution brainstorming
• Roadmap planning

Maps create shared understanding
across marketing, product, sales, support

Common Mistakes

1. Assuming Instead of Researching

❌ "I know what users do"
❌ Based on internal assumptions
❌ No user validation

✅ Based on real user research
✅ Validated with actual customers
✅ Updated with new insights

2. Too Much Detail

❌ Every micro-interaction mapped
❌ 20+ phases
❌ Information overload

✅ Focus on key phases
✅ Highlight critical moments
✅ Summarize at right level

3. Static Document

❌ Created once, never updated
❌ Hung on wall, ignored
❌ No follow-up action

✅ Living document
✅ Revisited quarterly
✅ Drives action items

4. Internal Focus

❌ Map shows internal processes
❌ Focus on company goals
❌ Business-centric language

✅ User-centric perspective
✅ User's language
✅ User's goals and emotions

Advanced Techniques

Ecosystem Maps

Show related journeys:
• Primary journey: Purchasing
• Secondary: Support, Returns
• External: Competitor experience
• Adjacent: Related products

Multi-Persona Maps

Compare journeys side-by-side:

          │ Novice User │ Expert User │
──────────┼─────────────┼─────────────┤
Onboarding│ Longer,     │ Skip,       │
          │ guided      │ self-serve  │
──────────┼─────────────┼─────────────┤
Support   │ Chat-heavy  │ Self-help   │
──────────┼─────────────┼─────────────┤
Features  │ Basic only  │ Advanced    │

Quantified Journey Maps

Add data to journey:
• Drop-off rates at each phase
• Time spent at each step
• CSAT/NPS by touchpoint
• Revenue at each stage
• Support ticket volume