What is a User Flow?
A user flow is a diagram that shows the path a user takes through your product to complete a specific goal. It starts with an entry point (landing page, notification, deep link), moves through a series of screens and interactions, and ends with a completed action or outcome.
User flows use simple shapes: rectangles for screens, diamonds for decision points, arrows for transitions. The simplicity is intentional. Anyone on the team should be able to read a user flow without training.
Why User Flows Matter
User flows expose complexity that mockups hide. A mockup shows what one screen looks like. A user flow shows how that screen connects to every other screen in the sequence. When you map the full flow, you discover that your "simple" checkout process has 7 steps and 3 decision points.
For PMs, user flows are a communication tool. They align engineering, design, and QA on the expected behavior before anyone writes code or pushes pixels. Disagreements about flow are cheap to resolve on a whiteboard, expensive to resolve in code.
How to Create User Flows
Start with the user's goal. "User wants to create and share a report." Work backward from the completed goal to the entry point.
Map every step. Include screens, actions (click, type, swipe), system responses (loading, confirmation), and decision points (does the user have an account?). Do not skip "obvious" steps since they often contain hidden friction.
Identify branches. What happens if the user is not logged in? What if they have no data? What if the action fails? Each branch is a path you need to design and engineer.
Simplify. After mapping the current flow, look for steps to eliminate or combine. Every step is a place where users can drop off. Fewer steps means higher completion rates.
User Flows in Practice
When Airbnb redesigned their booking flow, they mapped every user flow from search to confirmed reservation. The mapping revealed that guests encountered 8 screens between finding a listing and completing payment. They reduced this to 5, significantly improving conversion.
Stripe used user flow diagrams to design their checkout integration. By mapping the flows for different merchant configurations (subscription, one-time, usage-based), they identified patterns that could be abstracted into a single, flexible API.
Common Pitfalls
- Only mapping the happy path. Error states, edge cases, and alternative paths need flows too. They represent a significant portion of user experience.
- Too much detail. A user flow is not a technical architecture diagram. Focus on the user's perspective, not system internals.
- Mapping flows in isolation. Flows intersect. The onboarding flow leads to the dashboard flow, which leads to the creation flow. Map the connections.
- Not validating with users. User flows are hypotheses about behavior. Test them with prototypes to verify that users follow the expected path.
Related Concepts
User flows connect to wireframes (detailed screen design), customer journey maps (broader experience mapping), and information architecture (structural organization). They inform user stories and are validated through prototypes and usability testing.