Build a user journey map from research
Builds an evidence-based journey map with stages, actions, thoughts, emotions, pain points and opportunities, marking every assumption. Use after interviews or studies about one segment.
Most journey maps are workshop guesses dressed up as research: tidy stages named after the company's funnel, emotions drawn as a smooth wave nobody measured, and pain points nobody can trace to a person. A useful map follows one segment through one scenario in their own terms, says where each cell came from, and ends in opportunities specific enough to act on.
Build a journey map for ph:persona_or_segment from this research:
- Define the scope: the scenario and goal the journey covers, where it starts (the trigger) and where it ends (goal met or abandoned). If the research covers several scenarios, pick the best-evidenced one and list the others.
- Name 4 to 7 stages from the person's point of view ("Realising the boiler is broken", not "Awareness"). Stages can happen outside the product.
- For each stage, fill these lanes:
- Doing: actions and steps;
- Touchpoints: channels, people and tools involved, including ones the company does not own;
- Thinking: questions and thoughts, as verbatim quotes where the research has them;
- Feeling: an emotion score from -2 to +2 with the emotion named and the evidence for it;
- Pain points: what goes wrong, and why;
- Opportunities: what could change.
- Tag every cell with its source (I3, ticket 1182, survey) or "assumption". Do not fill a cell from imagination without that tag; leave it "no data" if nothing supports it.
- Mark the moments that matter most: where people abandon, where emotion drops lowest, and where a single good experience changes the outcome.
- Turn the top pain points into 3 to 6 "How might we..." opportunity statements, ranked by severity and by how often the research shows them, each linked to the stage and evidence.
- If the research is too thin for a credible map (for example one interview or only opinions about features), say so and either produce a clearly labelled hypothesis map with the research needed to validate it, or ask for more material.
- One persona or segment and one scenario per map. If the research mixes segments whose journeys differ, say so and map only .
- Quotes are verbatim from the research; never invent or tidy them.
- Do not propose solutions in the map itself; solutions belong to the opportunities list, framed as directions, not features.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Scope
Segment, scenario, trigger, end state, sources used.
Journey map
A Markdown table with lanes as rows (Doing, Touchpoints, Thinking, Feeling, Pain points, Opportunities) and stages as columns. Source tags in brackets in each cell.
Emotional curve
One line per stage: stage, score, emotion, evidence. Mark the lowest point and abandonment points.
Opportunities
Ranked "How might we..." statements, each with stage, evidence and why it ranks there.
Evidence gaps
Cells marked "assumption" or "no data", and the research that would fill them.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Design
- category
- UX research
- level
- Intermediate
- made for
- UX researcher, Product / UX / UI designer, Product manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install build-user-journey-map --target claude-codenpx skills add hermes-hq/hodios-dist --skill build-user-journey-map -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-design@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of UX researchSynthesize usability test findings
Turns raw usability session notes into evidence-backed issues rated by severity and frequency, with task results and recommendations. Use after a round of usability sessions.
synthesize-usability-findingsDesign a first-run onboarding flow
Designs a first-run onboarding flow that gets new users to the activation moment fast, using progressive disclosure, skip paths and measurable steps. Use when designing or fixing onboarding.
design-onboarding-flowUX researcher
UX researcher who matches the method to the question, separates what people did from what it means, and protects participants. Use as a partner for planning, running and synthesising research.
ux-researcherAnalyse session recordings and heatmaps
Synthesises notes from session recordings and heatmaps into usability issues with frequency, severity and evidence, keeping observation apart from interpretation, and plans follow-ups.
analyze-session-recordingsBuild evidence-based user personas
Builds UX personas from research notes, grouping participants by behaviour, with goals, pain points and scenarios traced to evidence and assumptions marked. Use after interviews or field research.
build-user-personasDesign a diary study
Designs a diary study with research questions, daily and event prompts, recruitment, incentives, tactics to keep people logging, and an analysis plan. Use to study behaviour over weeks.
design-diary-study