customer-journey-map
Create a customer journey map across stages, touchpoints, actions, emotions, and metrics
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill customer-journey-mapInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of customer-journey-map
customer-journey-map scores 93/100 on our quality scale, 198th of 1,153 Content & Media skills we index (top 18%).
Its SKILL.md is 15 KB long, well organised into 37 sections with 9 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.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so customer-journey-map 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 foundOur 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-map compared with similar skills
All 4 of these similar skills score higher than customer-journey-map; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| customer-journey-map (this skill)by deanpeters | 93 | 7.1k | 3mo ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install customer-journey-map?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill customer-journey-map. The install tabs above show the steps for each supported agent. - Which AI agents does customer-journey-map 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-map 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-map still maintained?
- The repository was last updated about 3 months ago, so customer-journey-map is actively maintained.
Skill content
View source on GitHubname: customer-journey-map argument-hint: "[persona] [scenario]" description: Create a customer journey map across stages, touchpoints, actions, emotions, and metrics. Use when diagnosing a broken experience or aligning a team on the full customer flow. intent: >- Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives. type: component theme: workshops-facilitation best_for:
- "Mapping the full customer experience across all touchpoints"
- "Aligning cross-functional teams on the end-to-end customer journey"
- "Identifying pain points and opportunities by stage with measurable KPIs" scenarios:
- "I need to map the customer journey for our B2B SaaS onboarding experience from signup to first value"
- "Create a journey map for a PM leader evaluating our skills repo — from discovery through loyalty" estimated_time: "20-30 min"
Purpose
Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPIs, business goals, and teams involved at each stage. Use this to identify pain points, align cross-functional teams, and systematically improve the customer experience to achieve business objectives.
This is not a user flow diagram—it's a strategic artifact that combines customer empathy with business metrics to drive actionable improvements.
Input
Works best with: The customer (persona or segment) and the scenario or goal the journey covers. Also useful: Known stages, touchpoints, pain points, supporting research, and the business objective behind the map.
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 skill asks for persona and scenario first — a journey map without a specific actor and goal turns into a generic funnel diagram.
Example invocation: Map the journey for a mid-market ops manager going from free trial to paid rollout across their team.
Key Concepts
The Customer Journey Mapping Framework
Adapted from NNGroup's framework and Carnegie Mellon's PM curriculum, a customer journey map documents:
Horizontal structure (stages):
- Awareness: Customer first learns about your brand
- Consideration: Customer evaluates your offering
- Decision: Customer makes a purchase
- Service: Customer uses the product/service post-purchase
- Loyalty: Customer becomes a repeat buyer and advocate
Vertical structure (for each stage):
- Customer Actions: What customers do
- Touchpoints: Where/how they interact with your brand
- Customer Experience: Emotions and thoughts
- KPIs: Metrics to measure success
- Business Goals: What you're trying to achieve
- Teams Involved: Who owns this stage
Why This Works
- Empathy-driven: Centers on customer emotions, not just actions
- Cross-functional alignment: Shows which teams affect which stages
- Metric-focused: Ties customer experience to measurable outcomes
- Gap identification: Makes pain points and opportunities visible
- Actionable: Clear KPIs and goals enable prioritization
Anti-Patterns (What This Is NOT)
- Not a user story map: Journey maps are broader (all touchpoints, not just product use)
- Not a service blueprint: Less detailed on internal processes, more focused on customer experience
- Not static: Journey maps evolve as customer behavior changes
When to Use This
- Understanding customer experience across all touchpoints (not just product)
- Aligning cross-functional teams (marketing, sales, product, support)
- Identifying pain points and prioritizing improvements
- Onboarding new team members to customer perspective
- Auditing the end-to-end customer experience
When NOT to Use This
- For deep product-specific workflows (use story mapping instead)
- Before defining personas (need to know who you're mapping)
- As a one-time exercise (journey maps require ongoing updates)
Application
Use template.md for the full fill-in structure.
Step 1: Prepare Prerequisites
Before mapping, ensure you have:
- Key stakeholders: Marketing, sales, product, customer service representatives
- Buyer personas: Detailed personas with demographics, psychographics, goals, challenges (reference
skills/proto-persona/SKILL.md) - Defined stages: Main stages of your buying process (typically: Awareness, Consideration, Decision, Service, Loyalty)
- Touchpoint inventory: All places customers interact with your brand (website, social, email, store, support, etc.)
If missing: Run discovery interviews, persona definition work, or touchpoint audits first.
Step 2: Set Clear Objectives
Define what you want to achieve:
## Objectives
- [Goal 1: e.g., "Identify top 3 pain points causing drop-off between Awareness and Consideration"]
- [Goal 2: e.g., "Align marketing and sales on customer motivations at each stage"]
- [Goal 3: e.g., "Understand emotional journey to inform messaging strategy"]
Quality checks:
- Specific: Not "understand customers" but "identify drop-off causes in Consideration stage"
- Actionable: Results should inform decisions, not just document observations
Step 3: Choose a Buyer Persona
Select one persona to focus on (create separate maps for each persona):
## Persona
- [Persona name and brief description]
- [Example: "Manager Mike: 35-42, Director of Product at mid-sized B2B SaaS, struggles with data-driven prioritization, values time savings over feature depth"]
Why one persona per map: Different personas have different journeys. Mixing them creates confusion.
Step 4: Map Each Stage
For each stage (Awareness, Consideration, Decision, Service, Loyalty), document:
Customer Actions
What customers do at this stage:
### Stage: [Stage Name, e.g., Awareness]
**Customer Actions:**
- [Action 1: e.g., "See LinkedIn ad about product management tools"]
- [Action 2: e.g., "Hear about tool from PM peer at conference"]
- [Action 3: e.g., "Google 'best product roadmap software'"]
Quality checks:
- Observable: You can see or measure this action
- Specific: Not "research products" but "Google 'best roadmap software' and read comparison articles"
Touchpoints
Where/how customers interact with your brand:
**Touchpoints:**
- [Touchpoint 1: e.g., "LinkedIn Ads"]
- [Touchpoint 2: e.g., "Word-of-mouth at PM conferences"]
- [Touchpoint 3: e.g., "Google organic search results"]
- [Touchpoint 4: e.g., "Review sites (G2, Capterra)"]
Quality checks:
- Comprehensive: Include both digital and physical touchpoints
- Specific: Not "social media" but "LinkedIn Ads," "Twitter mentions," etc.
Customer Experience
Emotions and thoughts customers have:
**Customer Experience:**
- [Emotion 1: e.g., "Curious but skeptical—'Is this actually better than spreadsheets?'"]
- [Emotion 2: e.g., "Overwhelmed by options—'Too many tools, how do I choose?'"]
- [Emotion 3: e.g., "Hopeful but cautious—'Could this save me time?'"]
Quality checks:
- Authentic: Use customer quotes from research when possible
- Emotional: Capture feelings, not just thoughts
- Specific: Not "interested" but "curious but skeptical—worried about setup time"
KPIs
Key performance indicators for this stage:
**KPIs:**
- [KPI 1: e.g., "Brand awareness (measured via surveys)"]
- [KPI 2: e.g., "LinkedIn ad impressions: 100k/month"]
- [KPI 3: e.g., "Organic search traffic: 5k visitors/month"]
- [KPI 4: e.g., "G2 review views: 2k/month"]
Quality checks:
- Measurable: Can you track this?
- Stage-appropriate: Awareness KPIs differ from Decision KPIs
Business Goals
What you're trying to achieve at this stage:
**Business Goals:**
- [Goal 1: e.g., "Increase brand awareness among PMs at B2B SaaS companies"]
- [Goal 2: e.g., "Generate 500 qualified leads/month"]
- [Goal 3: e.g., "Position as top 3 roadmap tool in G2 rankings"]
Quality checks:
- Outcome-focused: Not "run ads" but "increase brand awareness"
- Aligned with stage: Don't expect conversions at Awareness stage
Teams Involved
Who owns this stage:
**Teams Involved:**
- [Team 1: e.g., "Marketing (ad campaigns, SEO)"]
- [Team 2: e.g., "Content (blog posts, comparison guides)"]
- [Team 3: e.g., "Customer Success (case studies, testimonials)"]
Quality checks:
- Cross-functional: Multiple teams usually touch each stage
- Specific roles: Not just "marketing" but "marketing (ad campaigns, SEO)"
Step 5: Visualize the Map
Create a table or visual diagram:
| Stage | Awareness | Consideration | Decision | Service | Loyalty | |-----------|---------------|-------------------|--------------|-------------|-------------| | Customer Actions | See ad, hear from peers, Google search | Compare features, read reviews, request demo | Free trial signup, test with real data, evaluate ROI | Onboard team, build first roadmap, integrate with Jira | Use daily, recommend to peers, share wins on LinkedIn | | Touchpoints | LinkedIn Ads, conferences, Google, review sites | Website, demo calls, sales emails | Product (free trial), onboarding emails | Product, support chat, knowledge base | Product, community forums, customer success check-ins | | Customer Experience | Curious but skeptical | Excited but overwhelmed by options | Anxious about setup time, hopeful about time savings | Relieved if easy, frustrated if complex | Satisfied and confident, proud of wins | | KPIs | Impressions: 100k/month, traffic: 5k/month | Demo requests: 100/month, trial signups: 50/month | Conversion rate: 20%, time-to-value: <2 hours | Activation rate: 70%, support ticket volume | Retention rate: 85%, NPS: 50, referral rate: 15% | | Business Goals | Increase brand awareness, generate 500 leads/month | Improve lead quality, reduce sales cycle to 30 days | Increase trial-to-paid conversion, optimize onboarding | Reduce churn, improve activation, minimize support costs | Increase LTV, generate referrals, upsell premium features | | Teams Involved | Marketing, Content | Marketing, Sales, Product | Sales, Product, Onboarding | Product, Support, Customer Success | Product, Customer Success, Marketing |
Step 6: Analyze and Prioritize
Review the map and ask:
- Where are the biggest pain points? (Look for negative emotions + high drop-off rates)
- Which stages have the weakest KPIs? (Prioritize low-performing stages)
- Are teams aligned? (Do teams understand their role in each stage?)
- What opportunities exist? (Where can small improvements create big impact?)
Prioritization criteria:
- Impact: How much would fixing this improve the customer experience?
- Feasibility: How easy is this to fix?
- Alignment: Does this support business goals?
Step 7: Test and Refine
- Update regularly: Customer behavior changes—revisit the map quarterly
- Validate with data: Use analytics, surveys, and customer interviews to confirm assumptions
- Track improvements: After making changes, measure impact on KPIs
Examples
See examples/sample.md for a full customer journey map example.
See examples/meta-product-manager-skills.md for a meta dogfoo
Truncated for display — read the full file on GitHub.
Related Skills
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
