Stop 04 · Information Architecture & UX StrategyTopics · 3/8

User Flows

In short

Before drawing a single screen, map the paths people take, including the 'what if' moments. User flows catch the forgotten branches, like a failed payment, while they're still cheap to fix.

A diagram showing the path a user takes to complete a specific goal, including decision points and alternate paths — used to plan a flow before designing any actual screens.

The jaadu stands at a fork in a path, pointing down both roads that lead to the same house.

Think of it like this

Directions to your house

When guests ask how to reach your house, you say: 'If you come by metro, take exit 2. If by auto, say the temple landmark. If you get lost, call me.' That's a user flow: one goal, a few branches, every case covered.

Watch it happen

Flow: ordering food when not logged in

Tap 'Checkout'

Logged in?

Yes: Address

No: Phone + OTP

OTP ok: Address

OTP fail: Resend

Pay

Order placed

1/4The flow starts at the user's action and hits a decision: are they logged in?

The big ideas

What you need to know

One goal per flow

Each flow covers one user goal, like 'place an order', from start to finish.

Decisions branch

Diamonds mark decisions like 'logged in?'. Every branch needs an end, even if it's an error.

Plan for failure

Wrong OTP, no internet, payment failed. Flows surface these before they become surprise bugs.

Entry points matter

People arrive from ads, links and notifications, not just the home screen. Map where they come in.

Save yourself the pain

Common mistakes

Oops

Only drawing the happy path where everything works.

Do this instead

Add at least the main error and edge branches. That's where users actually get stuck.

Oops

Jumping straight to high-fidelity screens.

Do this instead

Agree on the flow with boxes and arrows first. Changing a box is cheaper than redesigning ten screens.

Your mission

Map a sign-up flow

~35 min

Quick check

Why add failure branches like 'payment failed' to a user flow?

Go deeper

1Diagram a user flow for a common task (e.g. signing up, checking out) in a product you use.
2Practice including decision points and error/edge-case branches, not just the happy path.
3Learn why a clear user flow makes designing the actual screens much faster.