User Journey Mapping
Definition
Describe the user's path from trigger to completed outcome. A journey should reveal decisions, handoffs, dependencies, and moments where complexity appears for the user or system.
Questions To Ask
- What starts the journey?
- What does the user know before starting?
- What steps must happen in order?
- Where does the user wait, decide, correct, or abandon?
- What confirms completion?
Existing Project Comparison
- Compare existing navigation, routes, pages, and tests to the intended journey.
- Identify screens without a journey step and journey steps without a screen.
- Find pass-through screens that add work without changing the user's state.
- Check whether the journey exposes internal implementation details.
Suggestive Plan
- Write the happy path as 5 to 9 steps.
- Add key decisions and handoffs.
- Mark user-visible state changes.
- Mark system-visible state changes.
- Note missing, redundant, or unclear steps.
Example
Patient scheduling journey: request appointment, choose time window, enter contact details, confirm preferences, receive slot proposal, accept slot, get confirmation.
Vocabulary
- Journey: ordered path from trigger to outcome.
- Trigger: event that starts the journey.
- State change: meaningful change in user or system status.
- Handoff: transfer of responsibility between users, modules, or systems.
- Happy path: expected successful journey.
Expected Outcome
Produce a journey map with ordered steps, triggers, decisions, states, handoffs, and gaps to feed action breakdown.
1---2name: user-journey-mapping3description: Map the steps a user takes to reach the desired app outcome. Use when turning users and outcomes into workflows, auditing existing screens, or finding missing transitions before feature breakdown.4---56# User Journey Mapping78## Definition910Describe the user's path from trigger to completed outcome. A journey should reveal decisions, handoffs, dependencies, and moments where complexity appears for the user or system.1112## Questions To Ask1314- What starts the journey?15- What does the user know before starting?16- What steps must happen in order?17- Where does the user wait, decide, correct, or abandon?18- What confirms completion?1920## Existing Project Comparison2122- Compare existing navigation, routes, pages, and tests to the intended journey.23- Identify screens without a journey step and journey steps without a screen.24- Find pass-through screens that add work without changing the user's state.25- Check whether the journey exposes internal implementation details.2627## Suggestive Plan28291. Write the happy path as 5 to 9 steps.302. Add key decisions and handoffs.313. Mark user-visible state changes.324. Mark system-visible state changes.335. Note missing, redundant, or unclear steps.3435## Example3637Patient scheduling journey: request appointment, choose time window, enter contact details, confirm preferences, receive slot proposal, accept slot, get confirmation.3839## Vocabulary4041- Journey: ordered path from trigger to outcome.42- Trigger: event that starts the journey.43- State change: meaningful change in user or system status.44- Handoff: transfer of responsibility between users, modules, or systems.45- Happy path: expected successful journey.4647## Expected Outcome4849Produce a journey map with ordered steps, triggers, decisions, states, handoffs, and gaps to feed action breakdown.
harsh817