Task Flow explained
A task flow shows the steps a person takes from the start of a specific task to its completion. It usually focuses on one goal and makes the purpose and order of each step visible. A task flow orders the actions required for one job; it can describe what a person does and how the system responds rather than merely naming screens. The starting condition and definition of success should be clear.
Why it matters.
Unnecessary steps, repetition, and dead ends slow people down. Mapping the flow helps teams spot these problems before designing screens. An unnecessary verification or confusing handoff can make a short task difficult. Mapping steps lets teams discuss dependencies and missing states before development.
Let's look at an example.
Think of resetting a password.
Entering an email, opening a link, choosing a new password, and seeing confirmation form a task flow. The path back to sign-in matters too. If the reset link has expired, the person needs a way to request another one. An exception that affects completion belongs in the flow or a clearly linked alternative.
How to apply it.
- 01
Choose one user goal.
- 02
Mark the starting and success states.
- 03
Question whether each step is necessary.
“A clear goal helps you draw a shorter path.