Mmcp.market

customer-journey-map skill

by deanpeters·deanpeters/Product-Manager-Skills·7.1k stars

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.

A100/100content scan

Is the customer-journey-map skill safe?

Clean: nothing in its files matched our rules. We read 4 files in the folder on 2026-09-28.

No findings.

Install the customer-journey-map skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git /tmp/Product-Manager-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Product-Manager-Skills/skills/customer-journey-map ~/.claude/skills/customer-journey-map
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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:

  1. Key stakeholders: Marketing, sales, product, customer service representatives
  2. Buyer personas: Detailed personas with demographics, psychographics, goals, challenges (reference skills/proto-persona/SKILL.md)
  3. Defined stages: Main stages of your buying process (typically: Awareness, Consideration, Decision, Service, Loyalty)
  4. 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

More skills from deanpeters/Product-Manager-Skills

  • Aacquisition-channel-advisorEvaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
  • Aagent-orchestration-advisorDesign multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
  • Aai-shaped-readiness-advisorAssess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
  • Aaltitude-horizon-frameworkUnderstand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
  • Aansoff-matrixMap evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk.
  • Aautonomous-investigationThe protocol behind every investigation skill. Use when AI research must proceed without you: search-plan gate, Fact/Inference/Assumption labels, confidence stacking, diffable outputs.
  • Abattle-card-builderResearch and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report.
  • Abusiness-health-diagnosticDiagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
  • Acompany-intelResearch a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
  • Acompany-researchCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
  • Acompetitive-analysis-processOrchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card.
  • Acompetitive-intel-watchScheduled delta monitoring against a prior competitive snapshot. Use when tracking competitors on a cadence: material shifts only, cited evidence, battle-card update flags, runs unattended.

All agent skills → · MCP servers