A user flow is a diagram of the path a user takes through a product to complete one specific task, showing entry points, screens, actions, decisions and outcomes in sequence. In UX design, user flows translate goals and research findings into a concrete interaction structure before wireframes or visual design are produced.
A user flow answers a narrow question: how does a person get from point A to goal B in this interface, and what can happen on the way. It is task-focused and product-focused, which distinguishes it from a broader user journey. Flows expose missing steps, dead ends, unnecessary screens and error paths early, when changes still cost little.
Elements and notation of a user flow
Most user flows use a simplified flowchart notation. There is no single mandatory standard, but teams usually agree on a small set of shapes so that designers, developers and product managers read diagrams the same way.
| Element | Typical shape | Meaning |
|---|---|---|
| Entry point | Rounded rectangle or circle | Where the flow starts, such as an email link or search result |
| Screen or page | Rectangle | A distinct view the user sees |
| Action | Arrow label or small box | What the user does, such as tap or submit |
| Decision | Diamond | Branch by user choice or system condition |
| System process | Rectangle with marker | Background step such as payment authorization |
| End state | Rounded rectangle | Goal reached or flow abandoned |
Each flow should state its persona or user type, goal and entry point at the top. A flow for a returning customer who is already signed in differs substantially from a flow for a first-time visitor arriving from an advertisement, even if both end at the same confirmation screen.
Types of user flows and levels of fidelity
User flows vary in fidelity, from quick sketches of steps to detailed diagrams that include actual screen thumbnails. The right level depends on the project stage and on who needs to read the diagram.
| Variant | Content | Best stage |
|---|---|---|
| Task flow | Single linear path without branches | Early concept, simple tasks |
| Branched user flow | Decisions, alternatives and errors | Interaction design and specification |
| Wireflow | Wireframe thumbnails connected by arrows | Mobile and multi-screen interfaces |
| Screen flow | High-fidelity screens in sequence | Handoff and stakeholder review |
| Written flow | Numbered list of steps | Quick alignment, documentation |
A practical rule is one goal per flow. When a diagram tries to show registration, purchase and account recovery together, it becomes a site map in disguise and loses its value. Separate flows can reference each other at clearly marked connection points.
User flow compared with related UX artifacts
User flows are frequently confused with other UX design deliverables. The difference lies in what each artifact describes: the structure of content, the sequence of interaction or the full experience including emotions and offline touchpoints.
| Artifact | Focus | Scope | Typical question |
|---|---|---|---|
| User flow | Steps to complete a task | One task within the product | How does the user finish this? |
| User journey | Experience over time, including emotions | Many channels and phases | What does the user feel and need? |
| Information architecture | Structure and labeling of content | Whole product | Where does content live? |
| Site map | Hierarchy of pages | Whole product, no sequence | Which pages exist? |
| Wireframe | Layout of one screen | Single view | What is on this screen? |
These artifacts work together. Research and personas define who the user is, a journey map identifies the moments that matter, information architecture organizes content, and user flows then specify the interaction path that wireframes and prototypes later realize.
Creating a user flow step by step
A useful user flow starts from evidence about real goals, not from the existing screen inventory. Analytics, interviews, support tickets and usability testing reveal where users enter, what they try to achieve and where they fail.
- Define the user and the goal, for example a new customer who wants to book a first appointment.
- List realistic entry points, such as the home page, a search result, a reminder email or a deep link.
- Map the happy path, the shortest successful sequence of screens and actions.
- Add decisions and alternative paths, including signed-in and guest states.
- Add error and edge cases, such as invalid input, unavailable options, timeouts and back navigation.
- Review with developers and test with users, then simplify steps that add no value.
Teams often measure a flow by the number of steps and decisions on the happy path. Fewer steps are not automatically better, because splitting a long form into clear stages can reduce cognitive load, but every step should have a reason the user would recognize.
Common mistakes in user flows
Flaws in user flows usually appear as gaps between the diagram and reality. The table connects typical symptoms to causes and remedies.
| Symptom | Likely cause | Fix |
|---|---|---|
| Users abandon at an unexpected step | Only the happy path was designed | Map errors, empty states and exits |
| Developers ask many questions at handoff | Decisions and system states missing | Add conditions and system processes |
| Diagram becomes unreadable | Several goals in one flow | Split into one flow per goal |
| Flow ignores how users actually arrive | Single assumed entry point | Document every realistic entry point |
| Design looks logical but fails testing | Flow based on assumptions | Validate with usability testing |
The simple explanation
A user flow is like directions for getting somewhere inside an app or website. It shows where a person starts, which screens they pass, which choices they make and where they end up, for example with a booked ticket or a paid order.
Drawing these directions before building anything helps a team spot wrong turns and dead ends early. If the map shows that someone must pass eight screens to change a password, the team can fix that on paper instead of after launch.
How it is used in practice
A design team for a regional clinic group is redesigning online appointment booking. Analytics show that many visitors start booking but fewer than half finish. The team maps the current user flow for a new patient arriving from a search result and finds eleven steps, including forced account creation before the patient can see available times.
The redesigned flow lets the patient choose a service and time first, then enter details, with account creation offered as an optional step after confirmation. Error paths for fully booked days and expired sessions are added explicitly. Usability testing with eight participants shows that all of them complete the new flow, and the team hands developers a branched flow with every decision documented.