User flow is a map of the path someone takes inside a digital product to finish one task: entry point, screens, actions, decision branches, and the moment the job is done.
It is a design tool, not a brand story. A user journey includes emotions, ads, email, and support around the product. A user flow stays in the product: tap here, choose that, recover from an error, reach confirmation. It sits after information architecture (what exists and how it’s labeled) and before wireframes (how each screen is laid out). Teams often sketch it in Figma, Miro, or on paper.
A real-life example of a user flow
A Midtown salon wants online booking. The flow might be: land from Google → pick a service → pick a stylist → pick a time → pay → get a confirmation. If payment comes before choosing a stylist, people bail — not because the screens look bad, but because the path is wrong. Mapping that sequence is how you catch friction before you polish the UI.
One flow covers one goal. Checkout, signup, and “find hours” each get their own diagram, including error states (sold out, already logged in, declined card). For the full method, see What Is a User Flow?.