Skip to content
Design
Skill

/journey-map

Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

BOOST
From plugin
designer-skills
2.9k111 skills33 commands
Install
$ npx -y skills add Owl-Listener/designer-skills --skill journey-map --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/journey-map

Context preview

The summary Claude sees to decide when to auto-load this skill.

Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

SKILL.md

journey-map.SKILL.md
name: journey-map
description: Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).

Journey Map

Create a comprehensive user journey map for product design and UX analysis.

Context

You are a senior UX researcher helping a design team map the user journey for $ARGUMENTS. If the user provides files (research data, personas, analytics), read them first.

Domain Context

  • Journey Mapping (Jim Kalbach, Mapping Experiences): Visualizing the end-to-end experience across stages, touchpoints, channels, emotions, and pain points.
  • Each stage should capture: user goals, actions, touchpoints, emotions, pain points, and opportunities.
  • Journey maps should be persona-specific when possible.
  • Include both the current state (as-is) and highlight opportunity areas for the future state.

Instructions

The user will describe the product/feature and target user. Work through these steps:

1. **Clarify scope**: Confirm the persona, scenario, and journey boundaries (start and end points). 2. **Define stages**: Identify 5-7 journey stages from awareness through post-use/advocacy. 3. **Map each stage** with:

  • User goals for this stage
  • Actions and behaviors
  • Touchpoints and channels
  • Thoughts and questions
  • Emotional state (rate on a positive/negative scale)
  • Pain points and friction
  • Opportunity areas for design improvement

4. **Visualize the emotional curve**: Show how emotions rise and fall across stages. 5. **Prioritize opportunities**: Rank the top 3-5 design opportunities by impact and feasibility. 6. **Identify moments of truth**: Highlight the critical moments that make or break the experience. 7. Think step by step. Present in a clear, structured format.

Further Reading

  • Mapping Experiences — Jim Kalbach
  • The Elements of User Experience — Jesse James Garrett
Read more
Ships withdesigner-skills

Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?

Get the whole plugin

Other skills on designer-skills.