# User Flow

A user flow maps the actions, decisions, and system responses involved in completing a specific goal within a product.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/user-flow/>)

## What it means

A user flow represents possible paths from an entry condition to a task outcome. It can use a flowchart or connect screen sketches as a wireflow. A task flow often shows one particular sequence; a broader user flow includes branches. A journey map covers a wider experience across time and touchpoints.

## Why it matters

Individual screens can look complete while leaving a user stranded between them. Mapping transitions exposes missing recovery paths, repeated data entry, permission boundaries, and assumptions about where people start.

## When to use it

Use a user flow when designing or reviewing a task that crosses states or screens. A single screen annotation may be enough for a small change; a service blueprint is more suitable for backstage operational dependencies.

## How it works

1. Identify the user, goal, entry points, and relevant preconditions.
2. Map actions and responses through the main successful path.
3. Add decisions and branches for permissions, unavailable data, errors, and cancellation.
4. Label transitions clearly and identify where state must persist.
5. Walk through realistic scenarios with design and engineering, then test the risky paths.

## A practical example

A team maps password recovery from both the login page and an expired email link. The diagram exposes a loop that sends users back to an unusable link. They add a resend path with clear feedback and test that branch.

## Where it breaks

A flow is a model, not observed proof that people follow the path. Large diagrams become difficult to maintain. It may omit layout, content comprehension, and timing, so connect it to screen details and research where those affect decisions.

## Common mistakes

- Drawing only the successful path.
- Using unlabeled arrows that hide conditions.
- Confusing an organizational process with the user’s goal.

## Sources

1. [User Journeys vs. User Flows](<https://www.nngroup.com/articles/user-journeys-vs-user-flows/>) — Nielsen Norman Group · Professional guidance
2. [Wireflows: A UX Deliverable for Workflows and Apps](<https://www.nngroup.com/articles/wireflows/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Customer Journey Map](<https://wiki.soroush.uk/topic/customer-journey-map/>)
- [Wireframe](<https://wiki.soroush.uk/topic/wireframe/>)
- [Interaction Patterns](<https://wiki.soroush.uk/topic/interaction-patterns/>)
