User Flow
A user flow is the typical or ideal sequence of steps a user takes to complete a specific task within a single product, such as signing up, resetting a password or checking out. It maps each screen, decision point and system response along that path, usually as a flowchart, so teams can design and review the task before building it.
How User Flows Work
A user flow has a clear entry point (where the user starts, for example a "Forgot password" link), a goal (the task is done), and the steps in between. Each step is either a user action, a system response or a decision that branches the path, such as "Is the email address registered?" Good flows also show the unhappy paths: errors, expired links, empty states and the way back from each.
Flows are drawn at different levels of detail. A simple flowchart uses boxes and arrows. A wireflow combines wireframe-style screen layouts with flowchart arrows, which suits apps where a few screens change based on what the user does.
Why User Flows Matter
A user flow is a useful bridge between requirements and interface behavior. Drawing the path exposes missing screens, dead ends, redundant steps and decisions nobody has specified yet. Each step and branch usually maps to one or more functional requirements, so the flow becomes a checklist that design, engineering and QA can review together. If you want to go further, read about turning UX research into functional requirements.
User Flow Example
A team designs password reset for a web app. The flow starts at the login screen, where the user selects "Forgot password" and enters an email address. A decision follows: if the address is registered, the system sends a link; if not, it shows the same neutral confirmation so attackers cannot discover which accounts exist. The user opens the link, and a second decision checks whether it has expired. A valid link leads to a new-password screen and then to a signed-in dashboard. An expired link leads back to the request screen with an explanation. Mapping it this way surfaced two cases nobody had specified: what happens if the user requests several links, and where they land after resetting.
User Flow vs. Journey Map
A user flow zooms in on one task inside one product, usually completed in minutes. A journey map zooms out to a broader goal that can span days or weeks and several channels, such as email, sales calls and support, and it records the person's thoughts and emotions as well as their actions.