User Flow Diagram: What It Is and How to Draw One
What a user flow diagram is, how it differs from a task flow and a user journey, and how to draw one in five steps, with a sign-up example.
A user flow diagram shows the steps one person takes to reach one goal in a product: where they enter, each screen or action in order, each decision, and where the flow ends. To draw one, choose a single goal and a single kind of user, list the steps of the successful path, then add a branch for every point where something can go differently.
Teams draw user flows before designing screens, because a missing step costs minutes to fix in a diagram and days to fix in a build.
User flow, task flow and user journey
The three names are often mixed up.
| Shows | Branches | Typical use | |
|---|---|---|---|
| Task flow | The steps of one task, one path | None | Agreeing the basic sequence |
| User flow | One goal, with entry points, decisions and error paths | Yes | Planning screens and logic |
| User journey map | A whole experience across channels and time, with thoughts and feelings | Not usually | Understanding the customer |
A user flow is the one engineering and design both build from. If your diagram has no decisions, it is a task flow; that is a fine start, and the steps below turn it into a user flow.
Step 1: Choose one goal and one user
Write the goal as something the person wants: "create an account", "buy one item", "invite a teammate". Then say who they are and what they already have: a new visitor with no account is a different flow from a returning customer.
One goal, one diagram. A flow that tries to show sign-up, checkout and settings together cannot be read by anyone.
Step 2: Mark the entry points and the end
People do not all arrive at the home page. List where this flow can start: an advertisement, an emailed invitation, a link from inside the product. Each is an entry point.
Then define the end as a state, not a screen: "account exists and the person is signed in". Knowing the end tells you when a branch is finished.
Step 3: Draw the successful path
Lay out the steps in a line, left to right. Use three kinds of shape and stay consistent:
- A screen or page the person sees.
- An action the person takes.
- A decision or check, drawn as a diamond: a choice the person makes, or something the system verifies.
Label each with a few words. "Sign-up form", "Submit details", "Details valid?".
Step 4: Add every branch
This is where a user flow earns its keep. Go back to each decision and each action and ask what else can happen:
- The details are not valid.
- The email is already registered.
- The verification email is never opened.
- The payment is declined.
- The person closes the tab and comes back tomorrow.
Draw a line for each, and follow it until it rejoins the main path or reaches its own end. A check with only its "Yes" line drawn is the most common fault in a user flow, and it is the one that becomes a bug.
Step 5: Review it with design and engineering
Walk through the flow together, one line at a time. Designers will find screens that are missing; engineers will find states the diagram did not consider ("what if the link has expired?"). Add what they find. The flow is finished when nobody can name a case it does not cover.
An example: sign-up
- Landing page, then the sign-up form.
- Details valid? No: show what to fix and return to the form. Yes: send a verification email.
- Link opened? No: offer to resend. Yes: set up the workspace.
- End: the dashboard, signed in.
VamimiAI's user flow diagram maker page shows this flow drawn, with both error paths. You can describe your own flow and ask for the error paths, or attach the requirements document and ask for the flow of one goal.
Mistakes to avoid
- Only the successful path. Without branches it is a task flow, and the hard cases are still undecided.
- Several goals in one diagram. Split it. Link flows by ending one where the next begins.
- Screens with no way out. Every screen needs a line leaving it, even if it is "close".
- Too much interface detail. Button colours and field labels belong in the design. The flow shows what happens, not what it looks like.
- Never updated. When the product changes, change the flow, or the next person plans from a picture of last year's product.
A user flow is a flowchart with a product-specific purpose, so any flowchart tool can draw one. When the question changes from "what does the person do?" to "which system calls which?", a sequence diagram is the better picture.
Questions
What is a user flow diagram?
A user flow diagram is a picture of the path a person takes through a product to reach one goal. It shows the entry point, each screen and action in order, each decision, the error paths and the end state.
What is the difference between a user flow and a user journey?
A user flow covers one goal inside one product and shows its steps and decisions. A user journey map covers a longer experience across several channels and records what the person does, thinks and feels at each stage.
What should a user flow diagram include?
The entry points, the steps of the successful path, every decision with a line for each outcome, the error paths, and a clearly defined end. Keep it to one goal for one kind of user.
When should I create a user flow?
Before designing the screens, and again whenever the logic changes. It is the cheapest place to find a missing step or an unhandled error.
How detailed should a user flow be?
Detailed enough that a designer knows which screens are needed and an engineer knows which cases to handle. Leave out visual detail such as layout and wording.