A stepper shows total steps and current place
Aliases: wizard progress · n of N
What it is
A stepper draws a linear flow as “how many steps in all, which step now”. It gives task scale and current place, not ancestors on a classification tree, and not browsing history. Account opening, checkout, and expense claims — flows that must be finished in order — rely on it for two answers: how long this still is, and what this screen is called inside the stretch.
Why it happens
A linear task has no natural landmarks. People use “how much is left” to decide whether to finish now and whether to go fetch materials first. The total turns an unknown length into estimable work; current place pins this screen in the sequence so a question on step 4 is not mistaken for already being done. Numerals (3/5) and named steps (Shipping address) work together: the numeral estimates time, the name prevents walking into the wrong demand. Dots with no names say it is not over, but not what this step is asking. Names with no total hide whether more pits remain.
The stepper also promises order. Seeing 1–2–3–4, people expect not to skip unfinished earlier steps, and that later content depends on earlier answers. If that promise is decoration — random order is actually allowed, or the total disagrees with the real forms — they prepare materials on the wrong rhythm and discover at the last step that another unseen block must still be filled.
Studying it
Use duration estimates and completion intent: the same flow, comparing a visible total, current name only, and no stepper, measuring error in “how long remains”, mid-flow abandonment, and whether people brought materials this step needed. Independent variables: visibility of the total, whether steps are named. Dependent variables: estimate error, which step abandonment lands on, whether the flow can be retold in order afterwards.
Lab participants know this is a test task, so completion intent is inflated; real drop-off more often happens on the step where the total suddenly looks long.
Where it stops holding
A two-step flow gives the stepper little to say; a title is enough. A truly non-linear task (settings that can be filled in any order) drawn as a stepper fakes a sequence. Long flows that save a draft need a total and also a way to leave; the stepper must not imply “must finish in one sitting”. If progress is cut by field count rather than by perceived stage, step 1 may hold eighty percent of the time and the total lies.
Applying it
- Show total and current name together. The current step is distinguishable on the bar and matches the page title.
- Cut steps by perceived stage (Identity / Address / Confirm), not by internal form pages or API round-trips.
- Make the total visible on entering the flow; do not wait until one step is done to say four remain.
- How to check: hide the body, leave the stepper, and ask how many steps, which step now, and what this step is called. Then “how long remains”; if it cannot be estimated at all, the total is idle. Audit whether the cuts are roughly the same magnitude as actual effort.