What it is
A hybrid of wireframes and flow diagrams: each screen is a wireframe and arrows show the transitions and decisions between them, capturing both layout and behavior in one view.
When to use it
During Prototype, for flows where screen-to-screen behavior matters as much as individual layouts.
Why (value)
Communicates interaction sequences that static wireframes miss, without the overhead of a clickable prototype.
How to run it
- Identify the flow and its key screens.
- Wireframe each screen at low fidelity.
- Connect screens with arrows for actions and transitions.
- Note decision points and alternate paths.
- Review the end-to-end flow for gaps.
Inputs and outputs
- Inputs: Task flows and screen requirements.
- Outputs: A wireflow showing screens and transitions.
Time and effort
Low. A few hours for a flow.
Evidence and limitations
A design artifact, not evidence. See Evidence and limitations.
Tips and pitfalls
- Best for flow-heavy, low-branching interactions.
- Keep screens low-fidelity.
- Show decision points explicitly.
Variations
Screen-flow diagrams, annotated task 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
- Wireframing — Lay out structure and content priority without visual design to focus on function.
- User flow diagramming — Diagram the paths a user takes through a product to reach a goal.
- Task flow diagramming — Diagram the single sequence of steps to complete one task, without user-specific branching.
