Goal
Map the user journey in a way that directly informs implementation and UX structure.
When to Use
- The journey spans several states or surfaces.
- The team needs to understand user movement before screen design.
- UX work needs clearer context around goals and friction points.
Instructions
- Define the user, trigger, goal, and desired outcome.
- Map the happy path first.
- Add branch points for failure, waiting, permissions, and return paths.
- Note where backend or async events change the experience.
Constraints
- Keep the map tied to a real task.
- Do not turn the journey into generic product theory.
- Make implementation-relevant states explicit.
Output Format
- user and goal
- journey steps
- branch and failure points
- implementation notes
Examples
- "Map the journey for inviting a teammate and getting first value."
- "Show the user path through this report workflow."