What is a User Flow?

A user flow is a visual representation of the sequence of steps a user follows to accomplish a specific goal within a product: the screens they see, the actions they take, the decisions they make, and the branches those decisions create, drawn as a directed diagram from a starting point to an end state. "Sign up with email", "add a team member", "export a report": each is a flow, and each flow shows one task's path through the interface rather than the interface as a whole. Flows are drawn at varying fidelity, from box-and-arrow sketches on a whiteboard to wireflows that combine each step's screen with the connections between them, and they serve design (deciding the path), engineering (specifying the states), and research (testing whether the path works).

Flows, Journeys, and Site Maps

The three artifacts get conflated constantly and answer different questions. A site map or IA diagram shows the structure of the product: what exists and how it's organized, with no user in the picture. A user flow shows one task's path through that structure: what a user does, screen by screen, to reach a goal. A journey map shows the whole experience around and beyond the product: stages, touchpoints, emotions, and pain points across channels and time, of which any given flow is one small stretch. Flows are the most granular and the most testable of the three, which is why they sit at the center of usability work.

Drawing One

1. Start from the user's goal and entry point.
Where does the flow begin (a marketing email, a dashboard button, a deep link) and what does "done" look like? Flows that start at the screen the team is proud of, rather than where users actually arrive, miss the step that loses people.

2. Show decisions, branches, and errors.
Every fork (existing account or new, card declined or accepted, permission granted or denied) is a place the design must handle; flows that show only the happy path describe a product that doesn't exist.

3. Keep one goal per flow.
A diagram that covers three tasks covers none of them clearly.

4. Annotate states and system responses.
What the user sees after each action, including loading, empty, and error states; the flow is a specification as much as a picture.

Testing the Flow

A drawn flow is the team's belief about the path; research checks it against reality. Prototype testing with goal-based scenarios shows whether users follow the intended path, where they branch unexpectedly, and where they stall; in an unmoderated study the recorded sessions overlay actual paths on the designed one, and the recorded reasons explain the divergences (a Ballpark prototype study captures both per task). In production, behavioral analytics does the same at scale: funnel drop-off per step, path analysis showing the routes users really take, and session replays of the abandonments. The gap between the drawn flow and the observed one is the design's to-do list.

The Common Failures

Happy-path-only flows that ignore errors and branches. Flows drawn from the screens rather than from the goal, which reproduce the current design instead of questioning it. Flows that are never tested, so the diagram becomes the evidence. And flows mistaken for journeys, so that a beautifully optimized checkout sits inside an experience that lost the customer two touchpoints earlier.

Where This Leaves You

A user flow is the drawn path of one task through a product: goal to outcome, screen by screen, with its branches and errors. Distinguish it from the site map (structure) and the journey map (experience), draw it from the user's goal, include the unhappy paths, and then test it, because the flow on the whiteboard is a hypothesis and the recorded sessions and funnel data are the result.