What is a User Flow?

TL;DR

• A user flow maps the path a user takes toward a product goal.
• It can include screens, actions, decisions, branches, and states.
• User flows are more specific than broad user journeys.
• A complete flow should consider important failure and alternate paths.
• Flows help product, design, and engineering discuss behavior before implementation.

What does a user flow look like?

For a card-freeze feature, the simplest flow might be:

Card → Card settings → Freeze card → Confirm → Frozen state

But real product behavior may include additional branches: the card is already frozen, the request fails, the user lacks permission, or a pending transaction still exists.

A useful flow makes those possibilities visible.

What can a user flow contain?

• entry points
• screens or states
• user actions
• decision points
• system responses
• success outcomes
• errors and recovery

User flow vs. task flow

A task flow often describes one straightforward sequence for one task. A user flow can include multiple entry points, branches, and alternate routes.

User flow vs. user journey

A user journey is broader and can include goals, emotions, channels, context, and touchpoints outside one interface.

A user flow usually stays closer to the product interaction itself.

How do you create a user flow?

1. Choose one clear user goal.
2. Identify where the flow can begin.
3. Map the main sequence of actions.
4. Add decisions that change the path.
5. Include important states and system responses.
6. Add failure and recovery paths.
7. Review the flow with design and engineering.
8. Prototype uncertain interactions.

Common user-flow mistakes

Drawing screens before defining the goal

A flow is easier to evaluate when everyone knows what success means.

Mapping only the happy path

Failures, permissions, empty data, and interruptions often contain the expensive gaps.

Making the map unreadably complete

Split large systems into meaningful subflows rather than forcing everything onto one canvas.

Ignoring current product context

New flows have to fit existing navigation, permissions, components, and terminology.

The bottom line

A user flow answers: what sequence of actions and system states takes this user from intent to outcome?

Related terms

Task flow · User journey · Decision point · Edge case

Relevant Figr resource

See practical maps in Figr’s User Flow Examples.