Skill

Customer Journey Friction Analysis

Map a customer journey end-to-end, surface friction points ranked by impact, and deliver concrete fixes for each.

Goal

Produce a ranked friction point analysis of a customer's end-to-end journey, with each issue paired to a specific, actionable remedy.

Trigger

Invoke when preparing for a CX review, diagnosing conversion drop-off, planning a product sprint, or responding to a spike in churn or support volume.

Steps

  1. 1

    Using your connected tools (for example the CRM account record, support ticket history, product analytics/event data, NPS/CSAT survey results, and call transcripts from recent customer conversations), gather all available signals for $customer_segment. If a tool isn't connected, ask the user to paste representative data such as funnel metrics, survey verbatims, or support logs.

    • At least one behavioral or usage data source is present
    • At least one voice-of-customer source (survey, call, ticket) is present
    • Time range and segment scope are confirmed
  2. 2

    Map the full customer journey into named stages from first awareness through onboarding, activation, core usage, expansion, and renewal/advocacy. For each stage, list the primary action the customer takes, the channel or touchpoint involved, and the success criterion that signals a healthy transition to the next stage.

    • Every stage has a defined customer action and success criterion
    • No major touchpoint category (email, in-app, human) is missing from the map
  3. 3

    For each journey stage, identify friction points by cross-referencing drop-off data, support ticket themes, survey complaints, and call sentiment. A friction point must have at least one measurable signal (e.g., drop-off rate, ticket volume, low CSAT score, repeated escalation topic). Capture both quantitative evidence and a direct customer quote or verbatim where available.

    • Each friction point is tied to a specific stage
    • Each friction point has at least one quantitative signal
    • Verbatim or qualitative evidence is included where available
  4. 4

    Score and rank every friction point by impact using three dimensions: (1) breadth — what percentage of customers hit this friction; (2) severity — how much does it damage conversion, retention, or satisfaction; (3) recurrence — is it a one-time or repeating obstacle. Assign a High / Medium / Low composite impact rating and sort the list from highest to lowest impact.

    • All three impact dimensions are scored for each friction point
    • Final ranking is clearly ordered from highest to lowest composite impact
    • Ranking rationale is documented for the top 3 items
  5. 5

    For each friction point, write a concrete fix that specifies: what change to make, which team owns it (product, CS, marketing, ops), the effort level (quick win vs. multi-sprint), and the expected outcome metric that would confirm the fix worked. Prioritize quick wins that address high-impact friction first.

    • Every friction point has exactly one primary recommended fix
    • Owner and effort level are assigned for each fix
    • A measurable success metric is defined for each fix
  6. 6

    Synthesize the findings into a final output: a ranked friction point table followed by an executive summary of the top 3 issues and their fixes, and a 30-day action plan listing the two or three highest-ROI interventions the team should start immediately.

    • Ranked table covers all identified friction points
    • Executive summary is 3–5 sentences and decision-ready
    • 30-day action plan includes owner, first action, and target metric

Output format

Deliver three sections: (1) a Friction Point Ranked Table with columns for Stage, Friction Description, Evidence, Impact Rating, Fix, Owner, Effort, and Success Metric; (2) an Executive Summary of the top 3 friction points and their fixes in 3–5 sentences; (3) a 30-Day Action Plan listing the 2–3 highest-ROI interventions with owner and first concrete action.

Use it everywhere

Copy this skill into your library to inject it into Claude, ChatGPT, and Gemini — or install your whole library as / slash commands in Claude Code and Cowork.

Get started free →