User Flow
A user flow is the step-by-step path a person takes to accomplish something in your product — from landing to booked, or from signup to first success. Mapping it reveals every step where someone might get confused or drop off.
Why does a user flow matter to your business?
Every extra step in a flow loses some people. Mapping the flow before building shows where friction hides — an unnecessary field, a confusing choice, a dead end — so it can be removed before it costs you customers. It is cheaper to fix on paper than in code.
At Nabee, user flows are part of the design work that happens before screens are polished, and because one team carries them into the build, the agreed flow is the one that ships.
A concrete example
Toree's booking flow — choose a teacher, pick a time, confirm, pay — is a user flow. Getting the order and count of steps right is what makes booking feel effortless instead of like a chore.
Related terms
Common questions
- How is a user flow different from a wireframe?
- A user flow maps the path across screens; a wireframe lays out a single screen. They work together.
- Why map flows before building?
- Because removing a confusing step on paper is far cheaper than discovering it after the product is built and losing users to it.
- Do simple sites need user flows?
- Even a contact or signup flow benefits from being mapped. Anything with multiple steps benefits more.