SkillAgentSearch skills...

customer-journey-mapping-workshop

Run a customer journey mapping workshop with adaptive questions and outputs

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill customer-journey-mapping-workshop

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Tags

Our assessment of customer-journey-mapping-workshop

customer-journey-mapping-workshop scores 93/100 on our quality scale, 6th of 61 Product Management skills we index (top 10%).

Its SKILL.md is 18 KB long, well organised into 47 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so customer-journey-mapping-workshop is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

customer-journey-mapping-workshop compared with similar skills

All 4 of these similar skills score higher than customer-journey-mapping-workshop; compare them before choosing.

SkillScoreStarsUpdatedFormat
customer-journey-mapping-workshop (this skill)by deanpeters937.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install customer-journey-mapping-workshop?
Run npx skills add deanpeters/Product-Manager-Skills --skill customer-journey-mapping-workshop. The install tabs above show the steps for each supported agent.
Which AI agents does customer-journey-mapping-workshop work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is customer-journey-mapping-workshop safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is customer-journey-mapping-workshop still maintained?
The repository was last updated about 3 months ago, so customer-journey-mapping-workshop is actively maintained.

name: customer-journey-mapping-workshop argument-hint: "[persona] [scenario]" description: Run a customer journey mapping workshop with adaptive questions and outputs. Use when you need to map stages, actions, emotions, pain points, and opportunities for a persona and scenario. intent: >- Guide product managers through creating a customer journey map by asking adaptive questions about the actor (persona), scenario/goal, journey phases, actions/emotions, and opportunities for improvement. Use this to visualize the end-to-end customer experience, identify pain points, and create a shared mental model across teams—avoiding surface-level feature lists and ensuring discovery work focuses on real customer problems, not assumed solutions. type: interactive best_for:

  • "Running a workshop to map an end-to-end customer experience"
  • "Finding pain points across a user's journey"
  • "Aligning teams on the stages, emotions, and breakdowns in an experience" scenarios:
  • "Help me run a journey mapping workshop for new customer onboarding"
  • "Map the experience of a buyer from trial signup to first value"
  • "Facilitate a workshop on the support journey for churn-risk customers" theme: workshops-facilitation estimated_time: "45-90 min"

Purpose

Guide product managers through creating a customer journey map by asking adaptive questions about the actor (persona), scenario/goal, journey phases, actions/emotions, and opportunities for improvement. Use this to visualize the end-to-end customer experience, identify pain points, and create a shared mental model across teams—avoiding surface-level feature lists and ensuring discovery work focuses on real customer problems, not assumed solutions.

This is not a feature roadmap—it's a discovery and alignment tool that uncovers where the experience breaks down and where improvements will have the greatest impact.

Input

Works best with: The persona (actor) and the scenario or goal to map. Also useful: Journey phases you already know, research artifacts, and where you suspect the experience breaks.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The workshop opens with the actor question (Q1) and proceeds one question at a time per the facilitation protocol.

Example invocation: Run a journey mapping workshop: persona is a first-time landlord, scenario is listing and leasing their first property through our app.

Key Concepts

What is a Customer Journey Map?

A journey map (NNGroup) visualizes "the process that a person goes through in order to accomplish a goal." It compiles user actions into a timeline, enriched with thoughts and emotions to create a narrative, then condenses and polishes into a visual artifact.

Five Key Components (NNGroup Framework)

  1. Actor — A specific persona or user whose perspective anchors the map
  2. Scenario + Expectations — The situational context and associated goals
  3. Journey Phases — High-level stages organizing the experience (e.g., discover, try, buy, use, seek support)
  4. Actions, Mindsets, and Emotions — User behaviors, thoughts, and emotional responses throughout phases
  5. Opportunities — Insights identifying where experience can improve

Journey Map Structure

Actor: [Persona Name]
Scenario: [Goal/Context]

Phase 1: Discover → Phase 2: Try → Phase 3: Buy → Phase 4: Use → Phase 5: Support
   ↓                  ↓                ↓               ↓               ↓
Actions:           Actions:         Actions:        Actions:        Actions:
Thoughts:          Thoughts:        Thoughts:       Thoughts:       Thoughts:
Emotions: 😊😐😞    Emotions:        Emotions:       Emotions:       Emotions:
   ↓                  ↓                ↓               ↓               ↓
Opportunities:     Opportunities:   Opportunities:  Opportunities:  Opportunities:

Why This Works

  • Forces conversation: Teams align on shared understanding of customer experience
  • Reveals pain points: Emotions + actions highlight where experience breaks down
  • Prioritizes improvements: Opportunities ranked by impact guide roadmap decisions
  • Human-centered: Focuses on customer perspective, not internal processes

Anti-Patterns (What This Is NOT)

  • Not a service blueprint: Journey maps focus on customer perspective; service blueprints map internal operations
  • Not a user story map: Journey maps support discovery; user story maps facilitate implementation planning
  • Not an experience map: Journey maps target specific users and products; experience maps explore broader human behaviors

When to Use This

  • Starting customer discovery (understanding current experience)
  • Identifying pain points for retention/engagement initiatives
  • Aligning cross-functional teams on customer perspective
  • Prioritizing which problems to solve first

When NOT to Use This

  • When you already understand the customer journey deeply
  • For technical refactoring (no customer-facing journey)
  • As a substitute for user research (maps require research input)

Facilitation Source of Truth

Use workshop-facilitation as the default interaction protocol for this skill.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill asks up to 5 adaptive questions, offering 3-4 enumerated options at each step.

Interaction pattern: Pair with skills/workshop-facilitation/SKILL.md when you want a one-step-at-a-time flow with numbered recommendations at decision points and quick-select options for regular questions. If the user asks for a single-shot output, skip the multi-turn facilitation.


Step 0: Gather Context (Before Questions)

Agent suggests:

Before we create your journey map, let's gather context:

Customer Research:

  • User interviews, discovery notes, support tickets
  • Churn reasons, exit surveys, NPS feedback
  • Analytics data (drop-off points, feature usage)
  • Personas or proto-personas

Product Context:

  • Website copy, product descriptions, positioning
  • Competitor journey maps or reviews (G2, Capterra)
  • Existing journey documentation (if any)

You can paste this content directly, or describe the customer experience briefly.


Question 1: Identify Actor (Persona)

Agent asks: "Who is the actor for this journey map? (Which persona or user segment?)"

Offer 4 enumerated options:

  1. Primary persona — "Your main target customer (e.g., 'small business owner')" (Most common starting point)
  2. Secondary persona — "A secondary user segment with different needs (e.g., 'enterprise admin' vs. 'end user')" (Use if primary persona already mapped)
  3. High-churn persona — "User segment with highest churn rate (e.g., 'trial users who don't convert')" (Good for retention initiatives)
  4. Newly discovered persona — "Emerging user segment from recent research (e.g., 'remote teams' post-COVID)" (Good for market expansion)

Or describe your specific persona.

Adaptation: Use personas from context (proto-personas, JTBD research, etc.)

User response: [Selection or custom]


Question 2: Define Scenario + Goal

Agent asks: "What's the scenario and goal for this journey? (What is the actor trying to accomplish?)"

Offer 4 enumerated options:

  1. First-time use — "New user onboarding, from discovery to activation" (Common for SaaS, apps)
  2. Core workflow — "Recurring task the user does regularly (e.g., 'create invoice,' 'run report')" (Common for established products)
  3. Problem resolution — "User encounters issue and seeks help (e.g., 'forgot password,' 'billing question')" (Good for support/retention)
  4. Upgrade/expansion — "Free user considering paid plan, or existing customer expanding usage" (Good for growth initiatives)

Or describe your specific scenario.

User response: [Selection or custom]

Agent extracts:

  • Actor: [Persona from Q1]
  • Scenario: [Context from Q2]
  • Goal: [What actor is trying to accomplish]

Question 3: Identify Journey Phases

Agent says: "Let's break the journey into high-level phases (typically 4-6 phases from start to end)."

Agent generates 4-6 journey phases based on scenario (Q2).

Example (if Scenario = "First-time use"):

Journey Phases (left to right):

1. Discover — User learns about product
2. Evaluate — User researches, compares alternatives
3. Try — User signs up, starts onboarding
4. Activate — User reaches "aha moment," experiences value
5. Use — User integrates product into workflow
6. Expand — User considers upgrading or inviting team

Agent asks: "Do these phases capture the full journey? Should we add, remove, or rename phases?"

User response: [Approve or modify]


Question 4: Map Actions, Thoughts, Emotions per Phase

Agent says: "Now let's map what the actor does, thinks, and feels in each phase."

Agent generates 3-5 actions, thoughts, and emotions per phase based on context (Step 0) and scenario (Q2).

Example (for Phase 3: "Try — User signs up, starts onboarding"):

Phase 3: Try (Onboarding)

Actions:
- Signs up with email
- Receives welcome email
- Logs in for the first time
- Sees empty dashboard
- Searches for "getting started" guide

Thoughts:
- "This looks promising, but I'm not sure where to start"
- "Do I need to watch a tutorial video?"
- "What's the first step?"

Emotions:
- Curious but uncertain 🤔
- Slightly frustrated (no clear next step) 😕
- Hopeful it will get easier 🙂

Pain Points:
- No onboarding checklist or guided tour
- Empty state doesn't suggest next action
- Too many options in navigation (overwhelming)

Agent repeats for all journey phases, showing full map.

Agent asks: "Does this capture the customer experience accurately? Should we adjust actions, thoughts, or emotions?"

User response: [Approve or modify]


Question 5: Identify Opportunities (Pain Points to Address)

Agent says: "Based on the journey map, let's identify opportunities for improvement—ranked by impact."

Agent generates 5-7 opportunities (pain points with highest emotional intensity or drop-off rates).

Example:

# Opportunities (Ranked by Impact)

## 1. Onboarding lacks guided first steps (Phase 3: Try)
**Pain Point:** Users see empty dashboard, don't know what to do first
**Evidence:** 60% of signups don't complete first action within 24 hours
**Opportunity:** Add interactive onboarding checklist ("Create your first project," "Invite a teammate")
**Impact:** HIGH — Directly affects activation rate

---

## 2. Pricing page is confusing (Phase 2: Evaluate)
**Pain Point:** Users don't understand which plan fits their needs
**Evidence:** High bounce rate on pricing page (70% leave without signing up)
**Opportunity:** Add plan comparison tool or "Which plan is right for me?" quiz
**Impact:** HIGH — Directly affects trial conversion

---

## 3. Support is hard to find (Phase 5: Use)
**Pain Point:** Users encounter issues, struggle to find help
**Evidence:** Support tickets often say "I couldn't find an answer in docs"
**Opportunity:** Add in-app help widget, contextual tooltips
**Impact:** MEDIUM — Affects retention, but fewer users hit this phase

---

## 4. Email confirma

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium