What it is
A diagram of the steps, decisions, and branches a user moves through to complete a goal, focused on the path rather than screen layout.
When to use it
During Ideate and Prototype, when designing or auditing the route users take to a goal.
Why (value)
Exposes unnecessary steps, dead ends, and missing paths, and aligns the team on the intended journey through the product.
How to run it
- Define the entry point and the goal.
- Map each step and decision along the way.
- Show branches for alternate and error paths.
- Look for redundant steps and gaps.
- Simplify the path to the goal.
Inputs and outputs
- Inputs: Task and goal definitions, system logic.
- Outputs: A user flow diagram with paths and decision points.
Time and effort
Low. An hour or two per flow.
Evidence and limitations
A model of intended behavior, not evidence of actual behavior; analytics or testing reveal the real paths. See Evidence and limitations.
Tips and pitfalls
- Focus on decisions and branches, not pixels.
- Include error and edge paths.
- Validate against real behavior where you can.
Variations
Task flows, wireflows, swimlane flows.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Task flow diagramming — Diagram the single sequence of steps to complete one task, without user-specific branching.
- Wireflows — Combine wireframes with flow arrows to show both screens and the transitions between them.
- Sitemapping — Map the hierarchy and structure of a site or app's pages and sections.
