User flow

A user flow follows one person through one task. It starts at an entry point, such as a sign-up link, an invite email or an upgrade prompt, and maps every screen, decision and system response until the task succeeds or fails. Nielsen Norman Group describes flows as the micro view inside a broader user journey: minutes inside one product rather than weeks across channels.

Flows are usually drawn as flowcharts with boxes and decision diamonds, or as wireflows, which combine wireframe screens with arrows showing what each action does.

Why it matters for a SaaS product

Most product friction sits between screens, not on them. A sign-up that asks for a credit card before showing value, an invite that lands a teammate on an empty dashboard, a billing change that needs a support ticket: each looks fine screen by screen and breaks as a flow. Mapping flows shows the extra steps, the dead ends and the missing states before they are built. It is also the fastest way to align product, design and engineering on scope, because every box in the flow is a screen or state someone has to make.

How DesignMe handles it

On product design work we map journeys, navigation, decision points, onboarding steps and the logic between screens before designing UI. We map the core journey first, then work through states, permissions, errors, empty states and loading states, which is where much of the real product quality comes from. On AI MVP cleanup projects, mapping the core flows is how we find the confusing journeys and missing states that demo-built products tend to have.

For Ballogy, a sports training app serving players, coaches and parents, we rebuilt the flows as role-based journeys. Onboarding now opens with a sport picker, player details and a training path, and a profile prefilled with sample data lets users explore real screens before creating a full account.

Example

Say a project management tool loses half its invited teammates before they do anything. Mapping the invite flow shows the email link lands on a generic sign-up page, asks for a new password, then opens an empty workspace with no sign of the project they were invited to. The redesigned flow pre-fills the email, skips the workspace picker and drops the teammate straight into the shared project.

Common mistakes

• Mapping only the happy path. Errors, cancellations and expired links are part of the flow.
• Ignoring roles. Admins, members and guests often need different paths.
• Flows that stop at the screen edge. Emails, notifications and integrations are steps too.
• Drawing flows once. Update them when features change, or they stop matching the product.