WorkflowCraft conventionFoundational
User Flows
Map the decisions, states and exits before drawing screens, because most missing work hides in the branches nobody drew.
Definition
A user flow shows the sequence of steps, decisions and system states required to complete a task. It is a thinking tool first and a communication artefact second, and its main value is exposing the states a screen-led design silently omits.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
On this page
What a flow must contain
- The entry points, all of them. Most tasks can be started from more than one place.
- Each decision the person makes, with the options available at that moment.
- Each decision the system makes, including validation, permission and availability.
- The states that are not screens: loading, empty, partial, expired, offline.
- The failure branches, with what happens to work in progress.
- The exits, including abandonment and what is preserved.
Three levels, three uses
| Level | Shows | Use it for |
|---|---|---|
| Task flow | One path through one task, no branches | Aligning on the happy path quickly. |
| User flow | Decisions, branches and states | Finding the work nobody has scoped. |
| Service or journey map | Steps across channels and time, including offline | Problems that leave the product: delivery, support, billing. |
Drawing them
Do
- Use one shape per meaning and say what the shapes mean on the diagram itself.
- Name each step as a verb the person performs.
- Show error and empty branches at the same weight as the success path.
- Keep the flow at one level of detail. Two levels on one canvas becomes unreadable.
Do not
- Do not draw only the happy path and call the rest edge cases. They are most of the build.
- Do not put screen thumbnails in a flow meant for decisions. It turns into a sitemap.
- Do not maintain a flow nobody reads. If it has stopped being used, it has stopped being true.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Related concept
Connected closely enough to change how you apply this.
- PRD to User FlowAI workflow
- Empty StatesPattern
- Loading StatesPattern
- Multi-Step FlowsPattern
- IdeationWorkflow
- Problem FramingWorkflow
- WireframingWorkflow