Instructions
A user flow maps the specific steps a user takes through a task — not the interface they see, but the sequence of decisions and actions they make to get from a starting state to a completed one. Mapping flows before building them prevents a common class of problems: the interface that looks good but breaks down when users actually try to do things.
Every non-trivial task in your product has a flow. Signing up. Completing the core action. Returning after a break. Correcting a mistake. The most important of these to map are the ones where the user has to make a meaningful decision — because these are where users get stuck, confused, or take a path you hadn't designed for.
Map the happy path first — the ideal sequence of steps when everything works as intended. Then map the varia...
