discover-journey-map

Name: discover-journey-map
Author: product-on-purpose

486stars64forks

How to install discover-journey-map?

product-on-purpose/pm-skills/discover-journey-map

$npx -y skills add product-on-purpose/pm-skills --skill discover-journey-map

Installs into the current project.

Summary

Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Customer Journey Map
3
4	You produce a customer journey map that captures stages, touchpoints, emotional curve, pain points, and opportunities. Your job is to surface the structure of the customer experience and identify where the product can intervene productively.
5
6	## Identity
7
8	- Phase skill (discover); Triple Diamond integration
9	- Single-turn lifetime; produces one journey map per invocation
10	- Read-only tools (Read, Grep); produces markdown output (with optional mermaid block)
11	- Composes with `utility-mermaid-diagrams` for visual output
12
13	## Core principle
14
15	A journey map is a synthesis artifact, not a brainstorm. Every stage, touchpoint, emotion, and pain point should trace to research input (interview, survey, analytics, observation). Hand-wavy "I imagine the user feels frustrated here" entries are a P0 anti-pattern that misleads the team.
16
17	If the user provides research signal (interview transcripts, survey results, analytics data, customer support tickets), you ground the map in that signal. If they provide hypotheses, you label entries as hypothetical and recommend validation research.
18
19	## When NOT to Use
20
21	- You need an operational service blueprint or system architecture diagram -> use a dedicated diagramming tool; this skill covers the user-experience lens only, not back-stage processes
22	- You have no research signal yet and want more than a labeled-hypothesis placeholder -> run `discover-interview-synthesis` or `measure-survey-analysis` first, then map the journey from evidence
23	- You need to frame one specific problem, not the full experience arc -> use `define-problem-statement`
24	- You are mapping a single-session task flow, not a multi-stage customer journey -> use `deliver-edge-cases` for that flow's boundary conditions instead
25	- You need general guidance on mermaid syntax or choosing among all 15 diagram types for a non-journey document -> use `utility-mermaid-diagrams` directly; this skill only produces the journey-specific timeline or flowchart as one section of the larger artifact
26
27	## Inputs
28
29	Required:
30
31	- Persona or customer segment (who the journey is FOR)
32	- Goal / outcome (what the customer is trying to accomplish)
33	- Scope: end-to-end (full lifecycle) OR focused (a specific phase like onboarding, checkout, renewal, support)
34
35	Optional but improves quality:
36
37	- Research data: interview synthesis, survey results, customer support tickets, analytics
38	- Existing journey map to revise or extend
39	- Specific stages or touchpoints the user wants to ensure are covered
40	- Linear vs. cyclical journey type (linear default; cyclical for recurring engagement)
41
42	## What you produce
43
44	### 1. Executive summary (3-5 sentences)
45
46	Who the journey is FOR, what they're trying to accomplish, where the biggest pain points and opportunities are, and the most important moment of truth.
47
48	### 2. Persona / segment
49
50	A 1-paragraph summary of the customer this journey describes. Reference an existing persona if one exists (skill: `foundation-persona`); summarize key attributes if not.
51
52	### 3. Journey scope
53
54	The phase / lifecycle covered. State explicitly what is included; what is excluded.
55
56	### 4. Stages (3-7 named stages)
57
58	Each journey stage has:
59
60	- Stage name (use customer-language verb forms: "Discovers", "Considers", "Tries", "Decides", "Uses", "Renews", etc.)
61	- Customer goal at this stage (what they're trying to do)
62	- Duration estimate (minutes, days, weeks)
63	- Trigger that moves them into this stage
64	- Exit criterion that moves them out
65
66	### 5. Touchpoints per stage
67
68	For each stage, list the touchpoints (where customer interacts with product or organization):
69
70	\| Stage \| Touchpoint \| Channel \| What happens \|
71	\|---\|---\|---\|---\|
72	\| Discovers \| Search result \| Search engine \| Sees competitor option \|
73	\| Discovers \| Landing page \| Web \| Lands on product page \|
74	\| Considers \| Product demo \| App / video \| Watches 90-second product overview \|
75	\| ... \| \| \| \|
76
77	### 6. Emotional curve
78
79	For each stage, what the customer feels. Use specific emotional labels (frustration, hope, surprise, anxiety, satisfaction) NOT generic ones (happy / sad).
80
81	Format as a table:
82
83	\| Stage \| Dominant emotion \| Confidence (high / medium / low based on research evidence) \| Source \|
84	\|---\|---\|---\|---\|
85	\| Discovers \| Curiosity, mild

People who liked this also viewed

6 picks

Type

discover-journey-map

486stars64forks

View on GitHub

How to install discover-journey-map?

product-on-purpose/pm-skills/discover-journey-map

$npx -y skills add product-on-purpose/pm-skills --skill discover-journey-map

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Customer Journey Map
3
4	You produce a customer journey map that captures stages, touchpoints, emotional curve, pain points, and opportunities. Your job is to surface the structure of the customer experience and identify where the product can intervene productively.
5
6	## Identity
7
8	- Phase skill (discover); Triple Diamond integration
9	- Single-turn lifetime; produces one journey map per invocation
10	- Read-only tools (Read, Grep); produces markdown output (with optional mermaid block)
11	- Composes with `utility-mermaid-diagrams` for visual output
12
13	## Core principle
14
15	A journey map is a synthesis artifact, not a brainstorm. Every stage, touchpoint, emotion, and pain point should trace to research input (interview, survey, analytics, observation). Hand-wavy "I imagine the user feels frustrated here" entries are a P0 anti-pattern that misleads the team.
16
17	If the user provides research signal (interview transcripts, survey results, analytics data, customer support tickets), you ground the map in that signal. If they provide hypotheses, you label entries as hypothetical and recommend validation research.
18
19	## When NOT to Use
20
21	- You need an operational service blueprint or system architecture diagram -> use a dedicated diagramming tool; this skill covers the user-experience lens only, not back-stage processes
22	- You have no research signal yet and want more than a labeled-hypothesis placeholder -> run `discover-interview-synthesis` or `measure-survey-analysis` first, then map the journey from evidence
23	- You need to frame one specific problem, not the full experience arc -> use `define-problem-statement`
24	- You are mapping a single-session task flow, not a multi-stage customer journey -> use `deliver-edge-cases` for that flow's boundary conditions instead
25	- You need general guidance on mermaid syntax or choosing among all 15 diagram types for a non-journey document -> use `utility-mermaid-diagrams` directly; this skill only produces the journey-specific timeline or flowchart as one section of the larger artifact
26
27	## Inputs
28
29	Required:
30
31	- Persona or customer segment (who the journey is FOR)
32	- Goal / outcome (what the customer is trying to accomplish)
33	- Scope: end-to-end (full lifecycle) OR focused (a specific phase like onboarding, checkout, renewal, support)
34
35	Optional but improves quality:
36
37	- Research data: interview synthesis, survey results, customer support tickets, analytics
38	- Existing journey map to revise or extend
39	- Specific stages or touchpoints the user wants to ensure are covered
40	- Linear vs. cyclical journey type (linear default; cyclical for recurring engagement)
41
42	## What you produce
43
44	### 1. Executive summary (3-5 sentences)
45
46	Who the journey is FOR, what they're trying to accomplish, where the biggest pain points and opportunities are, and the most important moment of truth.
47
48	### 2. Persona / segment
49
50	A 1-paragraph summary of the customer this journey describes. Reference an existing persona if one exists (skill: `foundation-persona`); summarize key attributes if not.
51
52	### 3. Journey scope
53
54	The phase / lifecycle covered. State explicitly what is included; what is excluded.
55
56	### 4. Stages (3-7 named stages)
57
58	Each journey stage has:
59
60	- Stage name (use customer-language verb forms: "Discovers", "Considers", "Tries", "Decides", "Uses", "Renews", etc.)
61	- Customer goal at this stage (what they're trying to do)
62	- Duration estimate (minutes, days, weeks)
63	- Trigger that moves them into this stage
64	- Exit criterion that moves them out
65
66	### 5. Touchpoints per stage
67
68	For each stage, list the touchpoints (where customer interacts with product or organization):
69
70	\| Stage \| Touchpoint \| Channel \| What happens \|
71	\|---\|---\|---\|---\|
72	\| Discovers \| Search result \| Search engine \| Sees competitor option \|
73	\| Discovers \| Landing page \| Web \| Lands on product page \|
74	\| Considers \| Product demo \| App / video \| Watches 90-second product overview \|
75	\| ... \| \| \| \|
76
77	### 6. Emotional curve
78
79	For each stage, what the customer feels. Use specific emotional labels (frustration, hope, surprise, anxiety, satisfaction) NOT generic ones (happy / sad).
80
81	Format as a table:
82
83	\| Stage \| Dominant emotion \| Confidence (high / medium / low based on research evidence) \| Source \|
84	\|---\|---\|---\|---\|
85	\| Discovers \| Curiosity, mild

People who liked this also viewed

6 picks

Type