User Flow

What is a user flow?

A user flow is the set of steps a person takes inside one product to complete a common task, such as signing up, resetting a password or checking out. Nielsen Norman Group describes it as the typical or ideal set of interactions for that task: narrow, short-term, and recorded as user actions and system responses. It is usually drawn as a flow chart or wireflow.

User flow, task flow and user journey

The terms get mixed up. NN/g separates two of them clearly: a user flow covers minutes or hours inside one product, while a user journey is the broader, scenario-based sequence toward a high-level goal, often across channels and over days or weeks, and it includes what the person thinks and feels. NN/g does not define "task flow" as a separate term; it lists task diagrams as one way to draw a user flow. In practice teams use "task flow" for the same thing, so state in your own docs which word you use.

How to map a user flow

1. Pick one goal and one starting point, for example a visitor arriving from search who wants to start a free trial.
2. List the steps and the decisions along the way: each screen, each choice, each system response.
3. Add the unhappy paths: validation errors, expired links, empty states, a declined payment.
4. Mark where people can leave and where the flow can fail on the server side.
5. Sketch it as boxes and arrows, then test it with a UX prototype before building.

A simple example

Password reset: user clicks "Forgot password", enters an email, sees a neutral confirmation, opens the email, clicks the link, sets a new password, lands logged in. The decisions are what happens if the email is unknown, if the link has expired and if the new password is too weak. Each branch is a box in the diagram and a case to test.

Common mistakes

• Drawing only the happy path.
• Mixing several goals into one diagram until nobody can read it.
• Skipping mobile and keyboard use: check the flow against mobile-first design and keyboard navigation order.
• Treating the diagram as finished. Real analytics and user tests show where people actually drop out.

Monitoring a user flow in production

Once a flow is live, a flow that breaks silently costs you signups. Synthetic monitoring replays it on a schedule, from outside, and alerts you when a step fails: see synthetic monitoring, and compare it with real user monitoring, which measures what actual visitors experience. LoadFocus API monitoring offers browser checks (Playwright scripts) and multi-step checks that chain requests, such as a login followed by an authenticated call, on paid plans. For the trade-offs, read synthetic monitoring vs real user monitoring. To see how a flow behaves with many users at once, see the guide on load testing complex user journeys.

FAQ

What is a user flow in UX?

It is the sequence of steps a user takes in a product to complete a specific task, including the decisions and system responses along the way. It is typically drawn as a flow chart or wireflow.

What is the difference between a user flow and a user journey?

Per Nielsen Norman Group, a user flow is narrow and short-term, covering the steps inside one product for a task. A user journey is broader, spans channels and touchpoints over a longer time and includes the user's thoughts and emotions.

Is a task flow the same as a user flow?

NN/g does not treat task flow as a separate term and lists task diagrams as one way to represent a user flow. Many teams use the two words for the same thing.

What tools can I use to draw a user flow?

Any diagramming or design tool works, including whiteboards, flowchart tools and design software. The tool matters less than covering the error and edge paths.

How do I check that a user flow keeps working after release?

Replay it automatically with synthetic browser or multi-step checks, and alert on failures. Pair that with analytics or real user monitoring to see where actual visitors drop out.