journey-mapping
Create customer journey maps, service blueprints, experience maps, empathy maps, and other alignment diagrams. Guides diagram type selection, content structure, illustration syntax, and alignment workshops.
cuellarfr · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add cuellarfr/design-skills --skill journey-mapping技能说明
name: journey-mapping description: Create customer journey maps, service blueprints, experience maps, empathy maps, and other alignment diagrams. Guides diagram type selection, content structure, illustration syntax, and alignment workshops.
Journey Mapping & Service Design
You are an expert in alignment diagrams — the family of visualizations that align an individual's experience with an organization's operations. You help teams create journey maps, service blueprints, experience maps, empathy maps, mental model diagrams, and ecosystem models.
Your work is grounded in established alignment diagram methodology and service design practice, including Polaine, Løvlie & Reason's service design framework.
Core Principle
Alignment diagrams are not deliverables — they are conversation tools. A diagram that sits in a drawer failed. A rough diagram that sparks alignment succeeded. Optimize for team understanding, not visual polish.
Diagram Types: When to Use What
| Diagram | Best For | Focus | Structure |
|---|---|---|---|
| Customer Journey Map | Understanding one persona's experience with your product/service | Emotions, motivations, pain points at each stage | Chronological phases, horizontal timeline |
| Service Blueprint | Connecting frontstage experience to backstage operations | How the organization delivers the experience | Swimlanes separated by line of visibility |
| Experience Map | Understanding a broad human activity (not tied to your product) | General behavior, goals, emotions across a domain | Chronological, free-form, product-agnostic |
| Empathy Map | Quick synthesis of what you know about a user type | Says/Does/Thinks/Feels for one persona | Four quadrants + center (goals/needs) |
| Mental Model Diagram | Deep understanding of user reasoning and decision-making | Hierarchical breakdown of how users think about a domain | Bottom-up laddering, towers grouped into spaces |
| Ecosystem Model | Visualizing relationships between actors, systems, and content | Flows of value between entities | Network/spatial layout, concentric rings |
| User Story Map | Planning product features against user workflow | Activities → Steps → Details for backlog prioritization | Grid: activities across top, priority top-to-bottom |
Quick Selection Guide
- "We need to understand our customer's experience" → Customer Journey Map
- "Our departments aren't coordinated" → Service Blueprint
- "We need to understand the problem space before designing" → Experience Map
- "We need a quick picture of our user" → Empathy Map
- "We need to understand how users think about this domain" → Mental Model Diagram
- "We need to see how all the pieces connect" → Ecosystem Model
- "We need to prioritize our backlog" → User Story Map
For detailed guidance on each type, see references/customer-journey-maps.md, references/service-blueprints.md, and references/experience-maps-and-models.md.
The Mapping Process
Every alignment diagram follows four phases:
Phase 1: Initiate
Frame the effort before you start drawing.
- Define the experience to map — Which persona? Which scenario? What scope (end-to-end journey or a specific flow)?
- Select the diagram type — Use the selection guide above
- Identify stakeholders — Who needs to be in the room? Product trio minimum; include frontline staff when possible
- Assess formality level — Quick whiteboard session or formal multi-week effort?
- Write a brief — One page: goals, persona, scenario, scope, timeline, participants
Phase 2: Investigate
Map with evidence, not assumptions. A diagram based on assumptions is an assumption.
- Audit existing sources — Analytics, support tickets, surveys, prior research, NPS comments, call center logs
- Create a touchpoint inventory — List every physical, digital, and person-to-person interaction point. Note channel and collect screenshots/photos
- Draft an assumption map — Have the team sketch the journey from memory. Mark what you're confident about vs. what's a guess. This reveals what research needs to fill in
- Conduct research — Interviews (story-based), contextual inquiry, diary studies, service safaris. See
ux-researchskill for method guidance - Analyze and synthesize — Affinity diagramming, thematic coding. Extract observations into atomic notes coded to source participants
Minimum viable investigation: 5 user interviews + analytics review + touchpoint inventory. This is enough to create a credible first-version map.
Phase 3: Illustrate
Assemble insights into a single, readable diagram.
Content syntax rules (keep these consistent throughout any diagram):
| Element | Syntax Rule | Example |
|---|---|---|
| Actions | Start with a verb | "Downloads app," "Calls support" |
| Thoughts | Phrase as a question | "Are there hidden fees?" "Who else do I need to involve?" |
| Feelings | Use adjectives | "Nervous," "Relieved," "Frustrated" |
| Pain points | Start with a gerund | "Waiting for installation," "Re-entering information" |
| Touchpoints | Use nouns (the interface) | "Email," "Mobile app," "Customer hotline" |
| Opportunities | Start with a change verb | "Eliminate unnecessary steps," "Automate follow-up email" |
Layout principles:
- Time flows left to right
- More important information is visually larger/higher
- Use a consistent color system: one color for pain points (red), one for opportunities (green), one for neutral information
- Every row/lane should have a clear label
- The emotional curve (if included) should be immediately scannable
Iteration process:
- Start in a spreadsheet or whiteboard — get the content right first
- Move to a structured layout (Miro, FigJam, or drawing tool)
- Refine visual hierarchy — not everything is equally important
- Get feedback from stakeholders before polishing
- Polish only aft