Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Customer Journey Map Generator

agent product skill risk: low

Customer Journey Map Generator

Create an end-to-end customer journey map for a given product by defining a specific persona, mapping stages from awareness to advocacy, and documenting touchpoints, user actions,…

SKILL 1 file

SKILL.md
---
name: customer-journey-map
description: "Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey."
---
## 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):

   | Stage | Description |
   |---|---|
   | **Awareness** | How do they first learn about the product? |
   | **Consideration** | What do they evaluate? What alternatives do they compare? |
   | **Acquisition** | How do they sign up or purchase? |
   | **Onboarding** | First experience with the product — time to value |
   | **Engagement** | Regular usage — building habits |
   | **Retention** | What keeps them coming back? What might cause churn? |
   | **Advocacy** | When 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**:

   | Stage | Touchpoint | User Action | Emotion | Pain Point | Opportunity |
   |---|---|---|---|---|---|

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

- [User Journey Mapping 101](https://www.productcompass.pm/p/user-journey-mapping-101)
- [Funnel Analysis 101: How to Track and Optimize Your User Journey](https://www.productcompass.pm/p/funnel-analysis)
- [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques)
- [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate)

INPUTS

$ARGUMENTS REQUIRED

The product, service, or company for which the journey map is created

e.g. a B2B SaaS analytics platform

REQUIRED CONTEXT

  • $ARGUMENTS (product or service description)

OPTIONAL CONTEXT

  • interview transcripts
  • survey data
  • analytics
  • support tickets
  • existing journey maps
  • product URL

TOOLS REQUIRED

  • web_search
  • file_search

ROLES & RULES

Role assignments

  • You are creating a customer journey map for **$ARGUMENTS**.
  1. If the user provides files, read them first.
  2. Use web search to understand the product if a URL is provided.
  3. Use a specific persona with JTBD, not a generic user.

EXPECTED OUTPUT

Format
markdown
Schema
table · Stage, Description, Touchpoint, User Action, Thoughts & questions, Emotion, Pain Point, Opportunity
Constraints
  • include persona definition
  • map all specified stages
  • document touchpoints, actions, thoughts, emotions, pain points, opportunities per stage
  • identify aha moments, moments of truth, churn triggers
  • include journey map table
  • recommend prioritized improvements
  • suggest Miro/FigJam for visuals

SUCCESS CRITERIA

  • Define a specific persona
  • Map all journey stages with required columns
  • Identify aha moments, moments of truth, and churn triggers
  • Recommend prioritized improvements

FAILURE MODES

  • May produce generic personas instead of specific JTBD-based ones.
  • May fail to adapt stages when product context is missing.

CAVEATS

Dependencies
  • User-provided files (interview transcripts, survey data, analytics, support tickets, or existing journey maps)
  • URL if provided for web search
Missing context
  • Desired output length or level of detail
  • Specific product or industry details beyond $ARGUMENTS placeholder
Ambiguities
  • Stage list is presented as fixed but instruction says 'adapt to the product' without guidance on when or how to adapt.

QUALITY

OVERALL
0.86
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.90
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add an explicit placeholder for output length or depth (e.g., 'executive summary vs. detailed report').
  • Clarify whether the persona should be invented from $ARGUMENTS or extracted from provided files.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT