user-journey-mapping
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when improving a customer, employee, partner, or stakeholder experience across a process or lifecycle. Use when applying the User Journey Mapping consulting method and when a user asks for User Journey Mapping, method execution, structured diagnosis, or action planning.
In this repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- deductive-reasoningSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- jobs-to-be-doneSkill
- kano-modelSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- raci-matrixSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- swot-analysisSkill
- systems-thinkingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill to run User Journey Mapping as a practical consulting method, not as a generic framework explanation.
- Very specific: line 25
If an input is missing, do not block automatically.
- Distinctive: line 29
Do not combine unrelated segments, goals, and journeys in one map.
- Distinctive: line 87
Keep wording professional and plain enough that a smart non-specialist can use the output directly.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
User Journey Mapping
Use this skill to run User Journey Mapping as a practical consulting method, not as a generic framework explanation.
Method Notes
- Map one persona or segment through a timeline to accomplish one goal.
- Include actions, touchpoints, thoughts, emotions, pain points, and opportunities.
Required Inputs
Collect or infer these inputs before execution:
- persona or user segment
- journey scope
- known touchpoints
- pain points and evidence
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not combine unrelated segments, goals, and journeys in one map. A journey map needs a defined user, context, goal, and evidence; it is not a substitute for an internal process map.
Adjacent Methods
jobs-to-be-done: why the customer seeks progress.empathy-map: a focused actor snapshot.service-blueprint: backstage processes and systems.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| Define persona and goal | User segment, goal, scenario, start/end points. | Choose one journey for one user type. | Journey scope. |
| Map stages | Timeline, observed steps, channels. | Lay out chronological stages from trigger to outcome. | Journey stage map. |
| Add touchpoints and emotions | User actions, touchpoints, thoughts, feelings, evidence. | Fill each stage with actions, touchpoints, thoughts, emotions, and evidence. | Detailed journey map. |
| Find pain points and moments | Detailed map. | Identify friction, unmet needs, trust moments, and drop-off risks. | Pain point and opportunity list. |
| Prioritize interventions | Pain points, business owners, impact, effort. | Choose changes and validation signals by stage. | Journey improvement plan. |
Output Template
### 1. Persona, Goal, And Journey
Persona / segment:
Goal:
Trigger:
Start / end:
Evidence sources:
### 2. Journey Map
| Stage | Action | Touchpoint | Thought / emotion | Evidence |
|---|---|---|---|---|
| | | | | |
### 3. Moments That Matter
| Stage | Friction / trust moment | Impact | Root evidence | Owner |
|---|---|---|---|---|
| | | | | |
### 4. Intervention And Validation
| Change | Owner | Timing | User signal | Business guardrail |
|---|---|---|---|---|
| | | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:Quality Gate
- Produce the method-specific outputs for Persona, Goal, And Journey, Journey Map, Moments That Matter; do not substitute a generic framework summary.
- Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
- Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
- Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
- State missing inputs and the smallest validation action instead of inventing precision.
- Keep wording professional and plain enough that a smart non-specialist can use the output directly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.