Customer Journey Map
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.
MCP get_skill({ skillId: "customer-journey-map-cec41a42" })Use this skill with your agent
Create a free account and connect via MCP
## 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)Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Ab Test Analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Cohort Analysis
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Create Prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.