Use user-journey-map

Map a customer's end-to-end journey toward an outcome

Map a customer's end-to-end journey toward an outcome — 3–6 stages, each with actions, emotions, pains, and opportunities, plus a rendered Mermaid emotion arc and the ranked pain points design should attack first.

Reach for it when the user wants a journey map, customer experience map, "map the user's path through onboarding", touchpoint analysis, or "where do users feel friction".

Install it

npx skilldrop-cli install user-journey-map                 # Claude Code, your user folder
npx skilldrop-cli install user-journey-map --project       # Claude Code, this repo
npx skilldrop-cli install user-journey-map --ide cursor    # or kiro, codex, antigravity, copilot

It is part of the Product manager pack: --pack product-manager installs it with its neighbours.

Ask for it

Say it the way you would to a colleague. Requests like these route to it:

• "Map the customer journey through our onboarding flow"
• "Where do users feel the most friction in the purchase experience?"
• "Create a journey map for a new user's first week"
• "Turn this pile of user feedback into a customer experience map"
• "Map the touchpoints from trial signup to activation"

Requests like these belong to a different skill, so it shouldn't answer them:

• "Design the screen-by-screen flow for the checkout wizard"
• "Diagram how the order service talks to the payment service"
• "Map our internal ticket-escalation process"

If another skill answers instead, ask for this one by name: "use user-journey-map".

Check what you get

A good result:

• One persona, one outcome, both named in the title. A map for "users" is a map of nothing.
• The evidence level is declared at the top and every pain that deviates from it is tagged individually.
• Stage edges live in the persona's life, not on the product's surface — the trigger precedes the product; the end state is the persona's outcome.
• Every emotion score carries its reason. A bare number row is decoration.
• Opportunities are outcomes, not features. The moment "add a button" appears, the map has started doing design's job without design's process.
• The dips, the peak, and the ending are explicitly marked, and exactly 1–2 opportunities are named as the targets. Ranking is the deliverable.
• The Mermaid renders. Scores 1–5, one section per stage — check syntax before emitting.

See a worked example

• b2b saas onboarding

Use something else when

• Screen-by-screen interaction or flow design — that's below this altitude; the map hands off to it
• Internal/employee process mapping — this skill is outside-in; org-internal flows are a process diagram (architecture-diagrams sequence flows)
• Backstage service wiring behind the touchpoints — reverse-architecture / architecture-diagrams
• A committed feature needing requirements — prd-draft

Where a loop runs it

• Stage gather of the discover loop

Next

• SKILL.md, the instructions the agent reads
• Its page on the site
• Related: architecture-diagrams, prd-draft, reverse-architecture, success-metrics, user-story-splitter

Edit this page on GitHub · View source