User Flow
Also known as: task flow, UI flow, UX flow
What Is a User Flow?
A user flow is a diagram that maps the path a user takes through a product to complete a specific goal. It shows entry points, each step in the sequence, decision points where paths branch, and the endpoint (successful task completion or exit).
User flows focus on the logic of navigation, not the appearance of screens. They answer the question: what does a user need to do, in what order, to get from point A to point B?
What Does a User Flow Include?
Most user flows are built from a small set of recurring elements.
Entry points — where users begin the flow. A direct link, a notification, or the homepage can all serve as entry points for the same goal.
Steps — each screen, action, or decision a user encounters along the path.
Decision points — moments where the path branches based on a user choice or system condition. A login flow, for example, splits at authentication: verified users proceed, unverified ones are redirected.
End states — successful completion, an error state, or an exit point where users leave the flow.
What Are the Benefits?
Exposes gaps early — mapping a user flow before screens are designed surfaces missing steps, dead ends, and logical inconsistencies before any visual work is done.
Team alignment — developers, designers, and product managers can agree on expected paths before detailed design begins, reducing revision cycles later.
Scope clarity — a documented flow makes it easier to estimate how many screens and states a feature requires.
Testing foundation — defined flows give QA teams and usability researchers a clear framework for what to test and what success looks like.
What Are the Limitations?
No emotional context — a user flow maps steps and decisions, but the emotional layer at each point sits outside what a flow diagram documents. That belongs to experience mapping and qualitative research.
Edge case blind spots — flows built around the ideal path can miss less common but equally valid scenarios users encounter in practice.
Maintenance required — as products change, documented flows become outdated quickly if not updated alongside design decisions.
Where Does a User Flow Fit in the Design Process?
User flows are most useful before wireframing begins. Defining paths first prevents screens from being designed in isolation, without a clear view of how they connect to the broader experience.
They're a standard deliverable in product strategy work, where mapping user paths early helps teams align on scope and identify gaps before any design execution starts.