mcpField
C
customer-journey-map

customer-journey-map

github.com/phurynDesign & UI27.5k3.1k installsUpdated 2w ago
Repository

About customer-journey-map

A skill for product and experience teams to map the end-to-end customer journey. It organizes touchpoints, actions, emotions, and pain points by stage, then identifies critical moments and improvement opportunities.

Key features

  1. 01Define a specific persona with JTBD
  2. 02Map customer experience across journey stages
  3. 03Document touchpoints, actions, emotions, and pain points
  4. 04Identify critical moments and churn triggers
  5. 05Recommend and prioritize experience improvements

Use cases

  1. 01Analyze the experience from awareness through advocacy
  2. 02Use interview, survey, or support data to find friction

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/phuryn/pm-skills --skill customer-journey-map

After installing, type/customer-journey-mapin Claude Code to confirm it loaded.

Details

From the project README

Customer Journey Map

Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.

Context

You are creating a customer journey map for $ARGUMENTS.

If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.

Instructions
  1. Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.

  2. Map the journey stages (adapt to the product):

    StageDescription
    AwarenessHow do they first learn about the product?
    ConsiderationWhat do they evaluate? What alternatives do they compare?
    AcquisitionHow do they sign up or purchase?
    OnboardingFirst experience with the product — time to value
    EngagementRegular usage — building habits
    RetentionWhat keeps them coming back? What might cause churn?
    AdvocacyWhen and why do they recommend the product to others?
  3. For each stage, document:

    • Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
    • User actions: What they do at this stage
    • Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
    • Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
    • Pain points: Friction, confusion, drop-off risks
    • Opportunities: How to improve the experience at this point
  4. Identify critical moments:

    • Aha moment: When the user first experiences core value
    • Moments of truth: Decision points where they commit or abandon
    • Churn triggers: Where users most commonly drop off
  5. Create the journey map table:

    StageTouchpointUser ActionEmotionPain PointOpportunity
  6. Recommend prioritized improvements:

    • Which pain points have the highest impact on conversion or retention?
    • What quick wins can improve the experience immediately?
    • What requires deeper investment but has the biggest payoff?

Think step by step. Save as a markdown document. For visual journey maps, suggest the user create one in Miro or FigJam using this analysis as the foundation.


Further Reading

Comments

Markdown supported