Multi-Step Flows
Breaking a long task into steps, which reduces per-screen load but adds navigation cost and abandonment points.
Definition
A multi-step flow divides a task into sequential screens. It reduces the amount visible at once and allows validation per step, at the cost of extra transitions and more places for the user to leave.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
When splitting helps
- The task has genuinely distinct phases that map to how users think about it.
- Later steps depend on earlier answers, so branching is required.
- The full form is long enough to be intimidating as one screen.
- Progress needs to be saved and resumed across sessions.
Requirements
- Show total steps and current position, using step names rather than only numbers.
- Allow backward navigation without data loss.
- Save progress automatically at each step.
- Validate per step, so errors surface close to where they were made.
- Provide a review step before final submission for anything consequential.
- Manage focus on each transition: move it to the new step heading so screen reader users know the context changed.
In practice
Review before submit
Applications and checkoutA summary of everything entered, with edit links to each step, catches errors before submission and removes the anxiety of committing to something the user can no longer see.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Principles behind this
The reasoning this solution is an application of.
- User Control and FreedomHeuristic
- Goal-Gradient EffectLaw
Visible progress accelerates completion as the end gets closer.
- Zeigarnik EffectLaw
- Decision FatiguePsychology
Often used with
These usually appear in the same screen or the same decision.
- Progress IndicatorComponent
- StepperComponent
- TabsComponent
- Input ValidationPattern
- User FlowTemplate
Alternative approach
A different answer to the same problem, with a different cost.
- Progressive DisclosurePrinciple
One long form with disclosure, or several short steps. The choice turns on whether the parts are genuinely sequential.
Practical example
A worked decision where this was the deciding factor.
- One Long Form or Several Short StepsCase study
- Whether to Require an Account at CheckoutCase study
Related concept
Connected closely enough to change how you apply this.
- PRD to User FlowAI workflow
- User FlowsWorkflow