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

Task Flows

In short

Some things have one right way to do them, like paying a shopkeeper. A task flow maps that single straight path step by step, so you can count the steps and cut the extra ones.

A simpler, more linear version of a user flow, mapping a single specific task step by step without branching — useful for straightforward, well-defined actions.

The jaadu stirs a small pot of noodles on a stove with a timer nearby.

Think of it like this

Making Maggi

Boil water, add noodles, add tastemaker, wait two minutes, eat. No branches, no decisions, just a fixed order. A task flow is a recipe like this: one task, one path, every step in sequence.

Watch it happen

Task flow: pay a shop with UPI

Scan QR

Amount

UPI PIN

Success

1/4Open the app and scan the shop's QR code. The shop name appears so you know it's the right one.

The big ideas

What you need to know

Linear by design

Task flows skip branches. They show the expected path for one well-defined task.

Count the steps

Writing every step out makes extra ones obvious. Each removed tap saves time for every user.

Task vs user flow

User flows cover choices and branches for a goal. Task flows zoom into one straight sequence.

Save yourself the pain

Common mistakes

Oops

Adding steps that only exist because of how the backend works.

Do this instead

Design steps around the user's task. Push system-only steps behind the scenes.

Oops

Removing a step users need for confidence, like a confirmation.

Do this instead

Cut friction, not reassurance. Security and confirmation steps often earn their place.

Your mission

Trim a task

~25 min

Quick check

When is a task flow a better choice than a full user flow?

Go deeper

1Diagram a task flow for a simple, single-path action (e.g. resetting a password).
2Learn when a task flow is sufficient versus when you need a fuller user flow with branches.
3Compare a task flow and a user flow for the same feature to see the difference in complexity.