journey-mapping
User and customer journey mapping for experience analysis. Creates journey maps with touchpoints, emotions, pain points, and opportunity identification.
What this skill does
# Journey Mapping
Create user and customer journey maps to understand experiences, identify pain points, and discover improvement opportunities. A human-centered complement to process-focused value stream mapping.
## What is a Journey Map?
A **journey map** visualizes a user's experience over time as they accomplish a goal. Unlike process maps (which show what happens), journey maps show **how it feels** from the user's perspective.
| Element | Definition | Purpose |
|---------|------------|---------|
| **Persona** | Who is taking the journey | Focus on specific user type |
| **Phases** | Major stages of the journey | Organize the experience |
| **Touchpoints** | Interactions with your system | Identify contact points |
| **Actions** | What the user does | Understand behavior |
| **Thoughts** | What the user thinks | Understand mindset |
| **Emotions** | How the user feels | Identify emotional peaks/valleys |
| **Pain Points** | Friction and frustrations | Target improvements |
| **Opportunities** | Ways to improve | Prioritize enhancements |
## Journey Types
| Type | Scope | When to Use |
|------|-------|-------------|
| **Current State** | How things are today | Identify problems |
| **Future State** | Desired experience | Design solutions |
| **Day-in-the-Life** | Full day across contexts | Understand broader context |
| **Service Blueprint** | Journey + backstage operations | Design service delivery |
## Workflow
### Phase 1: Preparation
#### Step 1: Define the Journey Scope
```markdown
## Journey Definition
**Journey Name:** New Customer Onboarding
**Persona:** Sarah - First-time SaaS Buyer
**Goal:** Successfully adopt the product and get first value
**Trigger:** Signs up for trial
**End State:** Completes first project successfully
**Time Frame:** First 30 days
```
#### Step 2: Select or Create Persona
```markdown
## Persona: Sarah - First-time SaaS Buyer
**Demographics:**
- Age: 32
- Role: Marketing Manager
- Company: Mid-size B2B
- Tech Savviness: Moderate
**Goals:**
- Streamline team workflows
- Prove ROI to leadership
- Look good to her team
**Frustrations:**
- Limited time to learn new tools
- Past bad experiences with complex software
- Pressure to show quick results
**Quote:** "I need something that works out of the box."
```
### Phase 2: Map the Journey
#### Step 1: Identify Phases
Typical journey phases:
| Domain | Common Phases |
|--------|---------------|
| **Purchase** | Awareness → Consideration → Decision → Purchase |
| **Onboarding** | Sign-up → Setup → First Use → Habit Formation |
| **Support** | Issue → Search → Contact → Resolution → Follow-up |
| **Renewal** | Review → Evaluate → Negotiate → Renew/Churn |
#### Step 2: Map Touchpoints and Actions
For each phase:
```markdown
## Phase: Setup
### Touchpoints
- Welcome email
- Product UI (setup wizard)
- Help documentation
- Onboarding video
### Actions
1. Opens welcome email
2. Clicks "Get Started"
3. Enters company info
4. Invites team members
5. Configures first workspace
```
#### Step 3: Capture Thoughts and Emotions
```markdown
## Phase: Setup - Experience
| Step | Thought | Emotion | Intensity |
|------|---------|---------|-----------|
| Opens email | "Let's see if this is worth it" | Curious, skeptical | Neutral |
| Clicks Get Started | "Okay, here we go" | Hopeful | Slightly positive |
| Company info form | "Why so many fields?" | Frustrated | Negative |
| Invites team | "Easy enough" | Relieved | Positive |
| First workspace | "This is actually nice!" | Pleased | Very positive |
```
#### Step 4: Identify Pain Points
```markdown
## Pain Points - Setup Phase
| Pain Point | Severity | Evidence | Root Cause |
|------------|----------|----------|------------|
| Too many required fields | High | Drop-off data, complaints | Legacy form design |
| Unclear field labels | Medium | Support tickets | Jargon-heavy copy |
| No save-and-continue | High | Abandoned setups | Technical limitation |
| Team invite confusion | Medium | Support volume | Poor UX |
```
#### Step 5: Identify Opportunities
```markdown
## Opportunities - Setup Phase
| Opportunity | Impact | Effort | Priority |
|-------------|--------|--------|----------|
| Progressive disclosure (fewer upfront fields) | High | Low | 1 |
| Save progress functionality | High | Medium | 2 |
| Contextual help tooltips | Medium | Low | 3 |
| Interactive setup tutorial | Medium | High | 4 |
```
### Phase 3: Visualize the Journey
#### Standard Journey Map Format
```text
PHASE: | Awareness | Sign-up | Setup | First Use | Habit
------------|--------------|--------------|--------------|--------------|--------
TOUCHPOINTS | Ads, blog | Landing page | Email, UI | Product | Product
| | pricing page | docs | | email
------------|--------------|--------------|--------------|--------------|--------
ACTIONS | Researches | Compares | Creates | Explores | Daily
| solutions | plans | account | features | usage
------------|--------------|--------------|--------------|--------------|--------
THOUGHTS | "Is there | "Which plan | "This is | "How do I | "This
| a better | is right?" | taking | do X?" | saves
| way?" | | too long" | | time"
------------|--------------|--------------|--------------|--------------|--------
EMOTIONS | 😐 | 🤔 | 😣 | 😕 | 😊
| Neutral | Uncertain | Frustrated | Confused | Happy
------------|--------------|--------------|--------------|--------------|--------
PAIN POINTS | Too many | Pricing | Long form | Feature | None
| options | confusion | No save | discoverability
------------|--------------|--------------|--------------|--------------|--------
OPPORTUN- | Clear | Simpler | Reduce | Better | Celebrate
ITIES | comparisons | pricing | friction | onboarding | wins
```
### Phase 4: Emotion Curve
Visualize emotional highs and lows:
```text
EMOTION
😊 +2 | ___/
😌 +1 | ___/\ /
😐 0 |____/\__/ \ ___ /
😕 -1 | \ / \__ _/
😣 -2 | \________/ \_/
|--Awareness--|--Sign-up--|--Setup--|--First Use--|--Habit--|
↑
Pain Point: Long form
```
### Phase 5: Identify Moments of Truth
**Moments of Truth** are critical interactions that disproportionately impact the overall experience:
| Moment Type | Definition | Example |
|-------------|------------|---------|
| **Zero Moment of Truth (ZMOT)** | Pre-purchase research | Reading reviews |
| **First Moment of Truth (FMOT)** | Initial encounter | Landing page |
| **Second Moment of Truth (SMOT)** | Using the product | First workflow |
| **Ultimate Moment of Truth (UMOT)** | Sharing experience | Referral/review |
```markdown
## Moments of Truth
| Moment | Phase | Current Experience | Desired Experience |
|--------|-------|-------------------|-------------------|
| FMOT | Landing | Overwhelming options | Clear value prop |
| SMOT | First Use | Confusion, need help | Guided success |
| UMOT | Habit | No celebration | Achievement sharing |
```
## Output Formats
### Narrative Summary
```markdown
## Journey Map Summary
**Journey:** [Name]
**Persona:** [Name]
**Date:** [ISO date]
**Analyst:** journey-facilitator
### Journey Overview
[2-3 sentence summary of the end-to-end experience]
### Emotional Journey
- **Highest Point:** [Phase] - [Why]
- **Lowest Point:** [Phase] - [Why]
- **Overall Arc:** [Description]
### Critical Pain Points
1. **[Pain Point]** (Phase: [X]) - [Impact and evidence]
2. **[Pain Point]** (Phase: [X]Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.