process & strategy
User flow
What is a user flow?
A user flow is a map of the path someone takes to complete a task in a product - each screen, action and decision point from start to goal. Drawn out as a diagram of steps and branches, it shows the whole journey at a glance, making it easy to spot unnecessary steps, dead ends and the places people are most likely to drop out.
Also known as: user flow, user flows, flow diagram
Prefer to watch?
Watch the recap 0:59
The demo
Here's the flow for one task - sign up and create a first project - laid out step by step. Walk it, spot the wasted step and the place people bail, then streamline it. The whole journey, visible at once.
What this demo shows (text version)
The task "sign up and create your first project" is drawn as a user flow: a sequence of steps (landing, sign up, verify email, set up profile, create project) with a decision branch and a highlighted drop-off hotspot where many people abandon - here, a mandatory profile-setup step that isn't needed yet. Laid out as a flow, the redundant step and the drop-off are obvious in a way they aren't when you look at each screen alone. A "streamlined" version removes the unnecessary step, shortening the path to the goal.
That's a user flow: a map of the path and decisions a user takes to complete a task, which makes the whole journey visible so you can spot unnecessary steps, dead ends and drop-off and shorten the route. Each extra step is a place to lose someone, so flows are a tool for removing friction, not just documenting it. Design the journey, not only the screens.
Designing screens in isolation hides the journey; a user flow makes the whole path visible so you can fix it. By mapping every step and decision between a user's starting point and their goal, you can see where the flow is too long, where it branches confusingly, where errors trap people, and where drop-off clusters. The goal is usually the shortest sensible path to the goal: each extra step is a chance to lose someone, so a flow is a tool for removing friction and dead ends, not just documenting them. Map the real task end to end, count the steps, and design the journey - not just the individual screens.
Screen by screen, everything looked fine - but laid out as a flow, the wasted steps and the spot where people bail jump straight out. That's what a user flow is for: seeing the whole journey at once, so you can shorten it and remove the dead ends. Every extra step on the path is somewhere you can lose someone, and you can't fix what you can't see.
A user flow charts a specific task from entry point to completion as a sequence of steps, screens and decision branches (often using simple flowchart notation - rectangles for screens/actions, diamonds for decisions). It captures the path and its forks, not the visual design, and is usually built around a goal and a scenario ("a new user signs up and creates their first project").
Its value is making the end-to-end journey visible, which screen-by-screen design hides. Laid out as a flow, problems become obvious: redundant or repeated steps, confusing branches, points with no clear next action, error states with no recovery, and the steps where drop-off concentrates (which analytics funnels then quantify). Each additional step is a point of potential abandonment, so flows are a primary tool for streamlining.
User flows relate to journey maps and task analysis but are narrower and more concrete: a journey map spans the broader experience and emotions across touchpoints, while a user flow is the specific screen-and-decision path for one task. Use flows to design and audit task paths - aim for the shortest sensible route, remove unnecessary decisions and steps, ensure every state has a forward path, and validate the flow against real user behaviour and funnel data.