Skip to content

rampstackco/claude-skills / skills/journey-mapping

journey-mapping

Verified

Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has departmental views of users but no shared map of what the experience actually feels like.

FileKindSize
README.mdmarkdown356 B
SKILL.mdskill md9.8 KB
references/journey-map-template.mdmarkdown6.7 KB

references/journey-map-template.md

View on GitHub
# Journey Map Template

Fillable journey map and service blueprint template. Customize phases to fit the specific product or service.

---

## Map metadata

**Persona / segment mapped:** [Specific persona. Not "users" - "First-time buyers in the 25-40 age range exploring B2B project management tools."]

**Time horizon mapped:** [Pre-purchase to first 90 days? Full lifetime? Specific feature?]

**Map version:** [X.Y]

**Last updated:** [YYYY-MM-DD]

**Owner:** [Person or team]

**Source data:** [Interviews, surveys, support tickets, analytics. List with counts.]

---

## Map structure

| Phase | Step | Touchpoint | Goal | Thoughts | Emotion | Pain points | Opportunities |
|---|---|---|---|---|---|---|---|

---

## Phase 1: [Phase name, e.g., Awareness]

### Step 1.1: [Step name, e.g., Encounters problem]

**Touchpoint:** [Where this happens. Could be offline. "Conversation with peer." Or online: "LinkedIn post."]

**Goal:** [What the user is trying to accomplish at this step]

**Thoughts:**
- "[Specific thought, ideally a real quote from research]"
- "[Specific thought]"
- "[Specific thought]"

**Emotion:** [Emotional state, ideally from a defined set: confused, hopeful, frustrated, curious, anxious, confident, etc.]

**Emotional intensity:** [1 to 5, for plotting on the emotional curve]

**Pain points:**
- [Specific pain, with evidence]
- [Specific pain, with evidence]

**Opportunities:**
- [Specific improvement opportunity]
- [Specific improvement opportunity]

**Time spent at this step:** [Minutes / hours / days / weeks - average and range]

---

### Step 1.2: [Step name]

[Repeat structure]

---

## Phase 2: [Phase name, e.g., Consideration]

### Step 2.1: [Step name, e.g., Searches for solutions]

**Touchpoint:** [e.g., Google search, then 4 to 6 vendor websites]

**Goal:** [Build a shortlist of options that could fit]

**Thoughts:**
- "[Quote]"
- "[Quote]"

**Emotion:** [State]

**Emotional intensity:** [1 to 5]

**Pain points:**
- [Specific pain]
- [Specific pain]

**Opportunities:**
- [Opportunity]

**Time spent:** [Range]

---

### Step 2.2: [Step name]

[Repeat]

---

## Phase 3: [Phase name, e.g., Decision]

[Repeat structure]

---

## [Continue with phases relevant to the journey...]

---

## Emotional curve

Plot the emotional intensity across the journey. The curve typically reveals the moments of highest joy and highest frustration.

```
Emotion
intensity
   5 │
   4 │     ●
   3 │   ●   ●     ●
   2 │ ●       ● ●   ●
   1 │           ●     ●
     └──────────────────────
       1.1  2.1  3.1  4.1
        Phase / Step
```

[Document the emotional curve in your visual tool. Note the peaks (highest joy) and troughs (highest frustration). These are the most strategic points in the journey.]

---

## Service blueprint layers

For each phase, document the back-stage view.

### Phase 1: [Phase name]

**Front-stage actions** (employees in user view):
- [Action]
- [Action]

**Back-stage actions** (employees behind the scenes):
- [Action]
- [Action]

**Supporting processes** (systems, tools, vendors):
- [Process / system]
- [Process / system]

**Lines of visibility issues:**
- [Where back-stage failures cause front-stage problems]

---

### Phase 2: [Phase name]

[Repeat]

---

## Disconnects and gaps

The most valuable findings often come from comparing layers.

### Front-stage / back-stage disconnects

| Issue | Front-stage symptom | Back-stage cause |
|---|---|---|
| | | |
| | | |

### Internal team perception vs user reality

| Internal belief | User reality | Gap |
|---|---|---|
| | | |
| | | |

### Touchpoint / message inconsistencies

| Touchpoint A says | Touchpoint B says | Confusion result |
|---|---|---|
| | | |

---

## Persona context (for reference)

A reminder of who this map represents.

**Persona:** [Name and one-line description]

**Demographics:**
- Age range:
- Role / job:
- Company size or context:
- Geography:
- Tech savviness:

**Goals:**
- [Primary goal]
- [Secondary goal]
- [Secondary goal]

**Frustrations:**
- [Frustration]
- [Frustration]

**Behavior patterns:**
- [Pattern]
- [Pattern]

**Quote that captures them:**
> "[Quote from a research participant who exemplifies this persona]"

---

## Data sources

Document where the map's claims come from. Builds credibility and traceability.

| Claim | Source | Evidence |
|---|---|---|
| [Pain point at step 2.1] | 8 of 10 interviews | [Quote samples] |
| [Behavior at step 1.2] | Analytics: 73% drop-off | [Funnel data] |
| [Emotion at step 3.1] | Survey, 45 responses | [Score data] |

---

## Opportunity map

The output that drives action.

### Critical friction (fix soon)

| Friction | Phase / step | Evidence | Recommended action | Effort | Owner |
|---|---|---|---|---|---|
| [Specific] | | | | S/M/L | |
| [Specific] | | | | S/M/L | |

### Quick wins (low effort, meaningful impact)

| Opportunity | Phase / step | Recommended action | Effort | Impact |
|---|---|---|---|---|
| [Specific] | | | S | M |

### Strategic bets (high effort, transformative)

| Opportunity | Phase / step | Recommended action | Effort | Impact |
|---|---|---|---|---|
| [Specific] | | | L | H |

### Cross-team alignment opportunities

[Issues that require multiple teams to coordinate, not single-team fixes.]

- [Issue, teams involved, recommended approach]
- [Issue, teams involved, recommended approach]

---

## Action plan

Specific projects from the opportunity map.

### Immediate (next 30 days)

- [ ] [Action] - [Owner]
- [ ] [Action] - [Owner]

### Near-term (60 to 90 days)

- [ ] [Action] - [Owner]
- [ ] [Action] - [Owner]

### Strategic (next 2 to 4 quarters)

- [ ] [Action] - [Owner]
- [ ] [Action] - [Owner]

---

## Re-mapping schedule

Journey maps decay. Schedule re-mapping:

- **Triggering events:** Major product launch, new persona segment, significant business model change, drop in NPS or retention
- **Default cadence:** Annual review, with light updates quarterly

---

## Workshop outputs

Use this map in stakeholder workshops. Capture outputs:

**Workshop 1: Validation**
- Date:
- Attendees:
- Findings validated:
- Findings disputed:
- New findings surfaced:

**Workshop 2: Prioritization**
- Date:
- Attendees:
- Top opportunities agreed:
- Decisions made:
- Open questions:

---

## Companion artifacts

Often produced alongside a journey map:

- **Persona document.** Detailed persona that this journey map represents.
- **Quote library.** Direct user quotes organized by phase. Powerful in stakeholder presentations.
- **Highlight reel video.** 5 to 10 minute compilation of user moments mapped to journey phases.
- **Service blueprint.** Detailed back-stage map (this template includes a layer; a full blueprint deserves its own document).
- **Opportunity backlog.** All opportunities, scored and queued for execution.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall