home / skills / nickcrew / claude-cortex / user-journey-mapping

user-journey-mapping skill

/skills/user-journey-mapping

This skill helps you map end-to-end user journeys, identify pain points, and reveal emotions across touchpoints to inform improvements.

npx playbooks add skill nickcrew/claude-cortex --skill user-journey-mapping

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
3.8 KB
---
name: user-journey-mapping
description: Create comprehensive user journey maps that identify pain points, opportunities, and emotional states across touchpoints. Use when mapping user experiences or analyzing conversion flows.
keywords:
  - user journey
  - journey map
  - customer experience
  - touchpoints
  - conversion funnel
triggers:
  - journey map
  - user journey
  - customer journey
  - experience map
  - conversion flow
---

# User Journey Mapping

Comprehensive guide to creating user journey maps that reveal pain points, opportunities, and emotional states across the entire user experience.

## When to Use This Skill

- Mapping end-to-end user experiences
- Identifying conversion funnel drop-off points
- Understanding emotional states during key interactions
- Discovering optimization opportunities
- Aligning teams around user perspective

## Quick Reference

| Task | Load reference |
| --- | --- |
| **Research Methods** | `skills/user-journey-mapping/references/research-methods.md` |

## Journey Map Components

### 1. Stages
Define the major phases users go through:
```
Awareness → Consideration → Decision → Onboarding → Usage → Advocacy
```

### 2. User Actions
What the user does at each stage:
- Searches, browses, compares
- Signs up, configures, learns
- Uses features, seeks help
- Shares, recommends, upgrades

### 3. Touchpoints
Where interaction happens:
- Website, mobile app, email
- Support chat, documentation
- Social media, reviews
- In-person, phone

### 4. Emotions
How users feel (use emoticons or scale):
```
😊 Delighted  →  😐 Neutral  →  😤 Frustrated  →  😡 Angry
```

### 5. Pain Points
Where friction occurs:
- Confusion, delays, errors
- Missing information
- Poor feedback
- Technical issues

### 6. Opportunities
Where we can improve:
- Quick wins
- Major improvements
- Innovation opportunities

## Journey Map Template

```markdown
## User Journey: [Persona Name] - [Goal]

### Stage 1: [Stage Name]

**User Goal**: [What they're trying to achieve]

**Actions**:
- [Action 1]
- [Action 2]

**Touchpoints**: [Where interaction happens]

**Emotions**: [😊/😐/😤/😡] - [Why they feel this way]

**Pain Points**:
- [Pain point with impact]

**Opportunities**:
- [Opportunity with potential impact]

**Metrics**: [How we measure this stage]

---
[Repeat for each stage]
```

## Example Journey Map

### E-commerce Checkout Journey

| Stage | Awareness | Cart | Checkout | Payment | Confirmation |
|-------|-----------|------|----------|---------|--------------|
| **Actions** | Browse, compare | Add items, review | Enter details | Pay | Receive |
| **Emotions** | 😊 Excited | 😐 Considering | 😤 Tedious | 😰 Anxious | 😊 Relieved |
| **Pain Points** | Too many options | Price unclear | Too many fields | Security fears | No ETA |
| **Opportunities** | Recommendations | Clear pricing | Autofill | Trust signals | Tracking |

## Best Practices

### Do's
- Base on real user research, not assumptions
- Include both digital and non-digital touchpoints
- Map emotional highs and lows
- Quantify with metrics where possible
- Involve cross-functional stakeholders

### Don'ts
- Don't map the ideal journey - map reality
- Don't focus only on your touchpoints
- Don't ignore competitor alternatives
- Don't skip the "boring" stages
- Don't create and forget - iterate

## Integration with Design

1. **Identify critical moments**: Where do emotions shift?
2. **Prioritize pain points**: Impact × Frequency matrix
3. **Design interventions**: Targeted improvements
4. **Measure success**: Before/after metrics
5. **Iterate**: Journey maps are living documents

## Resources

- [Nielsen Norman Group Journey Mapping Guide](https://www.nngroup.com/articles/journey-mapping-101/)
- [Service Design Tools](https://servicedesigntools.org/tools/customer-journey-map)

Overview

This skill creates comprehensive user journey maps that surface pain points, emotional states, and improvement opportunities across all touchpoints. It helps teams align around the actual user experience and prioritize interventions that improve conversion and retention. Use it to transform research and analytics into action-oriented journey artifacts.

How this skill works

The skill breaks a user experience into stages (Awareness → Consideration → Decision → Onboarding → Usage → Advocacy) and documents user actions, touchpoints, emotions, pain points, opportunities, and metrics for each stage. It synthesizes qualitative research and quantitative data, highlights emotion shifts and friction hotspots, and produces a repeatable markdown template and prioritized recommendations. Outputs support cross-functional handoffs and measurement plans.

When to use it

  • Map end-to-end customer experiences before designing product fixes or experiments
  • Diagnose conversion funnel drop-off points and discover quick wins
  • Align product, design, and engineering teams around user pain and priority
  • Plan onboarding flows and reduce first-time user friction
  • Inform roadmap decisions with user-centered evidence and metrics

Best practices

  • Base maps on real user research and analytics, not assumptions
  • Include both digital and non-digital touchpoints for full context
  • Capture emotions explicitly and mark moments where they shift
  • Quantify impact with metrics (conversion, time-on-task, satisfaction)
  • Involve cross-functional stakeholders and iterate the map regularly

Example use cases

  • E-commerce checkout: identify fields causing abandonment and propose autofill or UI simplification
  • SaaS onboarding: map first 7 days to find features that block activation and design guided flows
  • Support experience: trace support touchpoints to reduce resolution time and improve documentation
  • Marketing-to-product handoff: align acquisition messaging with in-product expectations to lower churn

FAQ

What inputs do I need to create a valid journey map?

Combine qualitative research (interviews, usability tests), quantitative analytics (funnel, drop-off rates), and documented touchpoints like support logs and emails.

How often should a journey map be updated?

Update after major product changes, quarterly for active features, or whenever new research reveals new pain points or behavior shifts.