customer-journey-map
# customer-journey-map This Claude Code skill generates comprehensive customer journey maps spanning awareness through advocacy for products, services, or experiences. Use it when asked to visualize user journeys, document touchpoints and pain points, or design experience improvements. The skill captures each stage with associated customer actions, emotions, pain points, and prioritized opportunities, producing structured output suitable for product discovery, UX design decisions, and cross-functional stakeholder alignment workshops.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/customer-journey-map && cp -r /tmp/customer-journey-map/plugins/pm-discovery/skills/customer-journey-map ~/.claude/skills/customer-journey-mapSKILL.md
# Customer Journey Map Skill This skill produces a complete customer journey map covering every stage from awareness through advocacy. Each stage includes touchpoints, customer actions, emotions, pain points, and specific improvement opportunities. Output is ready for use in product discovery, UX design, or cross-functional alignment workshops. ## Required Inputs Ask the user for these if not provided: - **Product or service** being mapped - **Customer persona** — which customer segment is this map for? (be specific — one persona per map) - **Journey scope** — full end-to-end (awareness → advocacy), or a specific phase (e.g. onboarding only)? - **Current state or future state?** — mapping how it works today, or designing how it should work? - **Data sources** — any research, user interviews, support tickets, NPS comments, analytics available? - **Goal of the map** — what decision will this inform? (redesign, prioritisation, stakeholder alignment, new feature) ## Output Structure --- # Customer Journey Map: [Product / Service] **Persona:** [Name — e.g. "Sarah, the overwhelmed HR manager"] **Journey scope:** [Full end-to-end / Onboarding / Purchase / Renewal] **Current or future state:** [Current state / Desired future state] **Prepared by:** [Name / Team] **Date:** [Date] **Based on:** [Research sources — interviews, analytics, support data, assumed/hypothetical] --- ## Persona Summary | | | |---|---| | **Name** | [Sarah] | | **Role** | [HR Manager at a 200-person professional services firm] | | **Goal** | [Reduce time spent on manual employee data management] | | **Frustrations** | [Too many tools that don't talk to each other; always chasing approvals] | | **Tech comfort** | [Moderate — comfortable with SaaS tools but not a power user] | | **Decision power** | [Recommends tools; budget approved by CHRO] | --- ## Journey Overview ``` AWARENESS → CONSIDERATION → DECISION → ONBOARDING → ADOPTION → ADVOCACY [Stage 1] [Stage 2] [Stage 3] [Stage 4] [Stage 5] [Stage 6] ``` **Overall experience rating (current state):** [😤 Frustrating / 😐 Neutral / 😊 Positive] --- ## Stage 1: Awareness *How does the customer first discover the product exists?* **Customer goal at this stage:** [e.g. Realise they have a problem worth solving — or find a solution to a specific pain] | Element | Detail | |---|---| | **Trigger** | [What event makes them start looking? — e.g. Manual process breaks down / peer recommendation / saw ad] | | **Where they are** | [Google search / LinkedIn / conference / colleague conversation / email newsletter] | | **What they do** | [e.g. Searches "automate employee onboarding" / asks peers in HR community / clicks LinkedIn ad] | | **Emotion** | [😤 Frustrated — overwhelmed by manual processes and hoping for a better way] | | **Pain points** | [Overwhelming number of options / hard to know which tools are credible / can't tell what's B2B vs B2C from homepage] | | **Opportunities** | [SEO content targeting the trigger keyword / LinkedIn thought leadership / peer community presence] | --- ## Stage 2: Consideration *The customer is actively evaluating options. What do they do to decide?* | Element | Detail | |---|---| | **Customer goal** | [Narrow down from many options to a shortlist of 2–3] | | **What they do** | [Reads G2/Capterra reviews / watches demo video / downloads comparison guide / asks peers who use something similar] | | **Touchpoints** | [Website / review sites / social proof / demo request flow / sales email] | | **Emotion** | [😕 Anxious — worried about making the wrong choice; past tool purchases haven't delivered] | | **Pain points** | [Pricing not visible on website / demo requires a call before seeing the product / unclear if it works with their existing stack] | | **Opportunities** | [Self-serve demo or interactive product tour / transparent pricing page / ROI calculator / case studies from similar company size] | --- ## Stage 3: Decision *The customer is ready to buy — or not. What makes them commit?* | Element | Detail | |---|---| | **Customer goal** | [Get sign-off from CHRO and justify the decision with a business case] | | **What they do** | [Books sales call / requests security questionnaire / builds internal business case / negotiates contract] | | **Touchpoints** | [AE / sales call / security review / contract / procurement process] | | **Emotion** | [😬 Cautious — doesn't want to be wrong; presenting to leadership adds pressure] | | **Pain points** | [Sales process is slow / security questionnaire takes weeks / contract terms are non-standard and require legal] | | **Opportunities** | [Security FAQ self-serve / standard contract with predictable terms / champion toolkit (slides, business case template) to help them sell internally] | --- ## Stage 4: Onboarding *The customer has bought. Now they need to get value fast.* | Element | Detail | |---|---| | **Customer goal** | [Get the product working and show their CHRO it was a good decision] | | **What they do** | [Receives welcome email / attends kickoff call / configures integrations / invites team] | | **Touchpoints** | [Onboarding email sequence / in-product onboarding checklist / CSM / help centre / integrations marketplace] | | **Emotion** | [😬 Anxious but hopeful — excited about potential but stressed about the setup work] | | **Pain points** | [Setup is more complex than expected / IT required for SSO but IT is slow to respond / generic onboarding doesn't match their use case] | | **Opportunities** | [Role-specific onboarding paths / IT connector with pre-filled request template / quick win email at day 3 (show them one thing that already works)] | **Key moment of truth:** [What single moment in this stage determines whether they'll become an active user or ghost? — e.g. "First time the product saves them 30 minutes on a task they used to do manually"] --- ## Stage 5: Adoption *The customer is using the product. Are they getting consistent valu
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.