journey-mapping

Name: journey-mapping
Author: cuellarfr

41stars3forks

How to install journey-mapping?

cuellarfr/design-skills/journey-mapping

$npx -y skills add cuellarfr/design-skills --skill journey-mapping

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Journey Mapping & Service Design
2
3	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.
4
5	Your work is grounded in established alignment diagram methodology and service design practice, including Polaine, Løvlie & Reason's service design framework.
6
7	## Core Principle
8
9	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.
10
11	---
12
13	## Diagram Types: When to Use What
14
15	\| Diagram \| Best For \| Focus \| Structure \|
16	\|---\|---\|---\|---\|
17	\| Customer Journey Map \| Understanding one persona's experience with your product/service \| Emotions, motivations, pain points at each stage \| Chronological phases, horizontal timeline \|
18	\| Service Blueprint \| Connecting frontstage experience to backstage operations \| How the organization delivers the experience \| Swimlanes separated by line of visibility \|
19	\| Experience Map \| Understanding a broad human activity (not tied to your product) \| General behavior, goals, emotions across a domain \| Chronological, free-form, product-agnostic \|
20	\| Empathy Map \| Quick synthesis of what you know about a user type \| Says/Does/Thinks/Feels for one persona \| Four quadrants + center (goals/needs) \|
21	\| 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 \|
22	\| Ecosystem Model \| Visualizing relationships between actors, systems, and content \| Flows of value between entities \| Network/spatial layout, concentric rings \|
23	\| User Story Map \| Planning product features against user workflow \| Activities → Steps → Details for backlog prioritization \| Grid: activities across top, priority top-to-bottom \|
24
25	### Quick Selection Guide
26
27	- "We need to understand our customer's experience" → Customer Journey Map
28	- "Our departments aren't coordinated" → Service Blueprint
29	- "We need to understand the problem space before designing" → Experience Map
30	- "We need a quick picture of our user" → Empathy Map
31	- "We need to understand how users think about this domain" → Mental Model Diagram
32	- "We need to see how all the pieces connect" → Ecosystem Model
33	- "We need to prioritize our backlog" → User Story Map
34
35	For detailed guidance on each type, see `references/customer-journey-maps.md`, `references/service-blueprints.md`, and `references/experience-maps-and-models.md`.
36
37	---
38
39	## The Mapping Process
40
41	Every alignment diagram follows four phases:
42
43	### Phase 1: Initiate
44
45	Frame the effort before you start drawing.
46
47	1. Define the experience to map — Which persona? Which scenario? What scope (end-to-end journey or a specific flow)?
48	2. Select the diagram type — Use the selection guide above
49	3. Identify stakeholders — Who needs to be in the room? Product trio minimum; include frontline staff when possible
50	4. Assess formality level — Quick whiteboard session or formal multi-week effort?
51	5. Write a brief — One page: goals, persona, scenario, scope, timeline, participants
52
53	### Phase 2: Investigate
54
55	Map with evidence, not assumptions. A diagram based on assumptions is an assumption.
56
57	1. Audit existing sources — Analytics, support tickets, surveys, prior research, NPS comments, call center logs
58	2. Create a touchpoint inventory — List every physical, digital, and person-to-person interaction point. Note channel and collect screenshots/photos
59	3. 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
60	4. Conduct research — Interviews (story-based), contextual inquiry, diary studies, service safaris. See `ux-research` skill for method guidance
61	5. Analyze and synthesize — Affinity diagramming, thematic coding. Extract observations into atomic notes coded to source participants
62
63	Minimum viable investigation: 5 user interviews + analytics review + touchpoint inventory. This is enough to create a credible first-version map.
64
65	### Phase 3: Illustrate
66
67	Assemble insights into a single, readable diagram.
68
69	Content syntax rules (keep these consistent throughout any diagram):
70
71	\| Element \| Syntax Rule \| Example \|
72	\|---\|---\|---\|
73	\| Actions \| Start with a verb \| "Downloads app," "Calls support" \|
74	\| Thoughts \| Phrase as a question \| "Are there hidden fees?" "Who else do I need to

People who liked this also viewed

6 picks

Type

journey-mapping

41stars3forks

View on GitHub

How to install journey-mapping?

cuellarfr/design-skills/journey-mapping

$npx -y skills add cuellarfr/design-skills --skill journey-mapping

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Journey Mapping & Service Design
2
3	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.
4
5	Your work is grounded in established alignment diagram methodology and service design practice, including Polaine, Løvlie & Reason's service design framework.
6
7	## Core Principle
8
9	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.
10
11	---
12
13	## Diagram Types: When to Use What
14
15	\| Diagram \| Best For \| Focus \| Structure \|
16	\|---\|---\|---\|---\|
17	\| Customer Journey Map \| Understanding one persona's experience with your product/service \| Emotions, motivations, pain points at each stage \| Chronological phases, horizontal timeline \|
18	\| Service Blueprint \| Connecting frontstage experience to backstage operations \| How the organization delivers the experience \| Swimlanes separated by line of visibility \|
19	\| Experience Map \| Understanding a broad human activity (not tied to your product) \| General behavior, goals, emotions across a domain \| Chronological, free-form, product-agnostic \|
20	\| Empathy Map \| Quick synthesis of what you know about a user type \| Says/Does/Thinks/Feels for one persona \| Four quadrants + center (goals/needs) \|
21	\| 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 \|
22	\| Ecosystem Model \| Visualizing relationships between actors, systems, and content \| Flows of value between entities \| Network/spatial layout, concentric rings \|
23	\| User Story Map \| Planning product features against user workflow \| Activities → Steps → Details for backlog prioritization \| Grid: activities across top, priority top-to-bottom \|
24
25	### Quick Selection Guide
26
27	- "We need to understand our customer's experience" → Customer Journey Map
28	- "Our departments aren't coordinated" → Service Blueprint
29	- "We need to understand the problem space before designing" → Experience Map
30	- "We need a quick picture of our user" → Empathy Map
31	- "We need to understand how users think about this domain" → Mental Model Diagram
32	- "We need to see how all the pieces connect" → Ecosystem Model
33	- "We need to prioritize our backlog" → User Story Map
34
35	For detailed guidance on each type, see `references/customer-journey-maps.md`, `references/service-blueprints.md`, and `references/experience-maps-and-models.md`.
36
37	---
38
39	## The Mapping Process
40
41	Every alignment diagram follows four phases:
42
43	### Phase 1: Initiate
44
45	Frame the effort before you start drawing.
46
47	1. Define the experience to map — Which persona? Which scenario? What scope (end-to-end journey or a specific flow)?
48	2. Select the diagram type — Use the selection guide above
49	3. Identify stakeholders — Who needs to be in the room? Product trio minimum; include frontline staff when possible
50	4. Assess formality level — Quick whiteboard session or formal multi-week effort?
51	5. Write a brief — One page: goals, persona, scenario, scope, timeline, participants
52
53	### Phase 2: Investigate
54
55	Map with evidence, not assumptions. A diagram based on assumptions is an assumption.
56
57	1. Audit existing sources — Analytics, support tickets, surveys, prior research, NPS comments, call center logs
58	2. Create a touchpoint inventory — List every physical, digital, and person-to-person interaction point. Note channel and collect screenshots/photos
59	3. 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
60	4. Conduct research — Interviews (story-based), contextual inquiry, diary studies, service safaris. See `ux-research` skill for method guidance
61	5. Analyze and synthesize — Affinity diagramming, thematic coding. Extract observations into atomic notes coded to source participants
62
63	Minimum viable investigation: 5 user interviews + analytics review + touchpoint inventory. This is enough to create a credible first-version map.
64
65	### Phase 3: Illustrate
66
67	Assemble insights into a single, readable diagram.
68
69	Content syntax rules (keep these consistent throughout any diagram):
70
71	\| Element \| Syntax Rule \| Example \|
72	\|---\|---\|---\|
73	\| Actions \| Start with a verb \| "Downloads app," "Calls support" \|
74	\| Thoughts \| Phrase as a question \| "Are there hidden fees?" "Who else do I need to

People who liked this also viewed

6 picks

Type