journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has dep
Profile →npx skills add rampstackco/claude-skills --skill journey-mapping --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Journey Mapping Build journey maps and service blueprints that surface friction, align teams, and identify opportunities. Stack-agnostic. Tool-agnostic. This skill is for mapping the experience. For testing specific touchpoints, use `usability-testing`. For broader generative research, use `ux-research`. For analyzing conversion, use `cro-optimization`. --- ## When to use - Departments have different mental models of the customer experience - Customer experience feels disjointed across touchpoints - Specific friction or drop-off points need diagnosis - Strategic planning needs a shared view of the user - Service design (front-stage and back-stage) needs alignment - New product or feature needs to be designed in context of broader experience ## When NOT to use - Testing a single touchpoint or page (use `usability-testing`) - Generative research before journey mapping (use `ux-research`) - Operational process mapping that doesn't involve users - Funnel optimization (use `cro-optimization`) --- ## Required inputs - Identified user persona or segment to map (one map per segment) - Existing research and data about that segment - Cross-functional access (you cannot map back-stage witho
- When to use
- When NOT to use
- Required inputs
- The framework: 3 deliverables
- 1. Customer journey map
- 2. Service blueprint
- 3. Synthesized opportunity map
- Common phases by product type
- Most products
- SaaS
- Ecommerce
- Service
- Healthcare / high-stakes purchases
- How to gather the inputs
What does the journey-mapping skill do?
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the user experience, or visualize touchpoints and pain points. Triggers on customer journey, journey map, service blueprint, user journey, experience map, touchpoint analysis, friction map, journey audit, end-to-end experience, customer experience map. Also triggers when the team has dep
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill journey-mapping --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.