journey-mapping

Name: journey-mapping
Author: Productfculty-aipm

70stars33forks

How to install journey-mapping?

productfculty-aipm/pm-copilot-by-product-faculty/journey-mapping

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill journey-mapping

Installs into the current project.

Summary

Use this skill when the user asks to "create a journey map", "user journey map", "map the user experience", "map the customer journey", "end-to-end user flow", "what does the user experience look like", "map the onboarding journey", or wants to visualize the full sequence of step

Files · 1

View on GitHub

SKILL.md

1	# Journey Mapping
2
3	You are creating a user journey map — a visual and narrative representation of the complete user experience from awareness to outcome. Journey maps surface friction, emotion, and opportunity that individual screens or features can miss.
4
5	Framework: Service design principles, Teresa Torres (continuous discovery touchpoints), JTBD (progress map across stages).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` and `context/product/personas.md` to identify the primary persona for this journey. Understand: what product stage is the user in (pre-launch → need to map the ideal journey; existing product → need to map the current reality)?
10
11	## Step 2 — Define the Journey Scope
12
13	Clarify:
14	- Which persona? Primary user from the persona file, or a specific segment?
15	- Which goal? What is the user trying to accomplish in this journey? (e.g., "onboard and activate", "complete their first core task", "renew their subscription")
16	- Which scope? End-to-end from awareness, or a specific phase (e.g., just the onboarding journey)?
17	- Current vs. ideal? Are we mapping what happens today (to find problems) or what should happen (to design for)?
18
19	## Step 3 — Journey Phases
20
21	Identify the major phases of the journey. Adapt to the user's specific flow, but use these as a starting point:
22
23	Awareness: How does the user first learn about the product?
24	Consideration: What research or comparison do they do before trying it?
25	Activation: Their first experience — signup, onboarding, first use
26	Core loop: Regular use — the repeating pattern of value delivery
27	Expansion: Discovering new features or use cases
28	Retention / Renewal: Decision to continue using or subscribe
29	Advocacy / Referral: Sharing with others
30
31	For a specific feature journey (not the full product): adapt phases to the feature's flow.
32
33	## Step 4 — Journey Map Rows
34
35	For each phase, fill in:
36
37	User actions: What does the user actually do? (Steps, clicks, inputs, decisions)
38
39	Touchpoints: Where does the user interact with the product/brand? (In-app, email, Slack, support, etc.)
40
41	Thoughts: What is the user thinking at this step? (Uncertainty, expectation, intent)
42
43	Emotions: What are they feeling? (Use a simple scale: Frustrated → Neutral → Satisfied → Delighted)
44
45	Friction points: What makes this step hard or confusing?
46
47	Opportunities: What could be improved here? What would delight them?
48
49	Metrics available: Is there data for this step? (Conversion rate, time spent, drop-off rate)
50
51	## Step 5 — Emotion Arc
52
53	After completing the rows, draw the emotion arc:
54	- Plot the emotional score (1 = frustrated, 5 = delighted) for each phase
55	- Identify: where are the valleys (worst experiences)? Where are the peaks (delight moments)?
56	- The valleys are your highest-priority improvement opportunities
57	- The peaks are your strengths to protect and build messaging around
58
59	## Step 6 — Opportunity Prioritization
60
61	For each friction point identified:
62	- Which OST opportunity does it map to?
63	- How many users are affected?
64	- How severe is the friction?
65
66	Rank opportunities by: severity × affected users. This gives you a data-driven prioritization of where to invest.
67
68	## Step 7 — Output
69
70	Produce:
71	- Journey map table (phases × rows)
72	- Emotion arc summary (which phases are highest friction)
73	- Top 3 opportunities ranked by impact
74	- One "moment of delight" to protect and amplify
75
76	Offer to save to a Notion page (if connected) or `outputs/journey-map-[persona]-[goal]-[date].md`.

People who liked this also viewed

6 picks

Type

journey-mapping

70stars33forks

View on GitHub

How to install journey-mapping?

productfculty-aipm/pm-copilot-by-product-faculty/journey-mapping

$npx -y skills add Productfculty-aipm/PM-Copilot-by-Product-Faculty --skill journey-mapping

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Journey Mapping
2
3	You are creating a user journey map — a visual and narrative representation of the complete user experience from awareness to outcome. Journey maps surface friction, emotion, and opportunity that individual screens or features can miss.
4
5	Framework: Service design principles, Teresa Torres (continuous discovery touchpoints), JTBD (progress map across stages).
6
7	## Step 1 — Load Context
8
9	Read `memory/user-profile.md` and `context/product/personas.md` to identify the primary persona for this journey. Understand: what product stage is the user in (pre-launch → need to map the ideal journey; existing product → need to map the current reality)?
10
11	## Step 2 — Define the Journey Scope
12
13	Clarify:
14	- Which persona? Primary user from the persona file, or a specific segment?
15	- Which goal? What is the user trying to accomplish in this journey? (e.g., "onboard and activate", "complete their first core task", "renew their subscription")
16	- Which scope? End-to-end from awareness, or a specific phase (e.g., just the onboarding journey)?
17	- Current vs. ideal? Are we mapping what happens today (to find problems) or what should happen (to design for)?
18
19	## Step 3 — Journey Phases
20
21	Identify the major phases of the journey. Adapt to the user's specific flow, but use these as a starting point:
22
23	Awareness: How does the user first learn about the product?
24	Consideration: What research or comparison do they do before trying it?
25	Activation: Their first experience — signup, onboarding, first use
26	Core loop: Regular use — the repeating pattern of value delivery
27	Expansion: Discovering new features or use cases
28	Retention / Renewal: Decision to continue using or subscribe
29	Advocacy / Referral: Sharing with others
30
31	For a specific feature journey (not the full product): adapt phases to the feature's flow.
32
33	## Step 4 — Journey Map Rows
34
35	For each phase, fill in:
36
37	User actions: What does the user actually do? (Steps, clicks, inputs, decisions)
38
39	Touchpoints: Where does the user interact with the product/brand? (In-app, email, Slack, support, etc.)
40
41	Thoughts: What is the user thinking at this step? (Uncertainty, expectation, intent)
42
43	Emotions: What are they feeling? (Use a simple scale: Frustrated → Neutral → Satisfied → Delighted)
44
45	Friction points: What makes this step hard or confusing?
46
47	Opportunities: What could be improved here? What would delight them?
48
49	Metrics available: Is there data for this step? (Conversion rate, time spent, drop-off rate)
50
51	## Step 5 — Emotion Arc
52
53	After completing the rows, draw the emotion arc:
54	- Plot the emotional score (1 = frustrated, 5 = delighted) for each phase
55	- Identify: where are the valleys (worst experiences)? Where are the peaks (delight moments)?
56	- The valleys are your highest-priority improvement opportunities
57	- The peaks are your strengths to protect and build messaging around
58
59	## Step 6 — Opportunity Prioritization
60
61	For each friction point identified:
62	- Which OST opportunity does it map to?
63	- How many users are affected?
64	- How severe is the friction?
65
66	Rank opportunities by: severity × affected users. This gives you a data-driven prioritization of where to invest.
67
68	## Step 7 — Output
69
70	Produce:
71	- Journey map table (phases × rows)
72	- Emotion arc summary (which phases are highest friction)
73	- Top 3 opportunities ranked by impact
74	- One "moment of delight" to protect and amplify
75
76	Offer to save to a Notion page (if connected) or `outputs/journey-map-[persona]-[goal]-[date].md`.

People who liked this also viewed

6 picks

Type