This interval needs status confirmation, not a progress bar

What it is

From just past one second to still short of ten, people need to know the system is alive, not what percent remains. The right signal in this band is status confirmation: a loading state on the button, a line of “Opening…”, a breathing skeleton. Proof of life is enough. A progress bar is a mismatch here — the total is rarely knowable yet, and a moving percentage forces people to read a number that carries no information.

Omitting the bar is not laziness. At this timescale the bar’s resolution is higher than people need and higher than the system can honestly supply.

Why it happens

During a second-scale wait the question is binary: still going / already dead. Status confirmation answers the binary cheaply, without fake precision. A progress bar answers a continuous question: how far, how long. That question only appears when the wait is long enough for people to start budgeting time — the ten-second band, where attention may leave. Giving a continuous answer early usually means inventing it: the percent is a guessed total, the bar freezes when work stalls, and people then use “progress frozen” as a verdict of death.

Confirmation also has to be light. Heavy feedback (full-screen veil, large spinner, modal) turns a two-second wait into a formal interruption. The thought that confirmation was meant to hold is cut by the modal itself.

Where it stops holding

Downloads, imports and model runs that are known from the start to last minutes, and that have measurable bytes or steps, should not refuse a progress bar just because they are still in the first seconds — they will leave this band quickly and should open on determinate progress. Opening a detail, switching a view, submitting a short form, even if it occasionally hits 3 s, still belongs in the confirmation band. Indeterminate motion that runs too long (still unchanged near ten seconds) makes confirmation fail: “still spinning” is read as hung. That is already outside this leaf’s comfort zone.

Applying it

• For operations of one to several seconds: a loading state on the original control or a single status line. No percentage bar, no remaining-time estimate.
• Confirmation must be glanceable without stealing the content being watched. Prefer in-button indicators, inline marks and local skeletons over modals.
• If the wait may slide past ten seconds, prepare an upgrade from confirmation to a stage note or progress — do not spin until the person leaves.
• How to check: pin opening a detail at 2.5 s. With status confirmation, people should be able to say “it is still opening” and unable to quote a percentage. If they hunt for a bar or call the spinner hung, the confirmation is the wrong weight or the wrong duration.

Related

• Same group: I1.02.1 Within a one-second delay, the user's train of thought stays intact · I1.02.2 Past that point, wait feedback is required
• Nearby: I1.03 Attention-holding ceiling · I2.02 Predictable progress · E6.09 Determinate and indeterminate progress
• Search terms: status confirmation · indeterminate progress · wait feedback