Progress should express what remains, not only what is complete
Aliases: time remaining · remaining work · progress framing · estimated time remaining
What it is
Remaining-work progress helps people estimate how much waiting, attention, or resource remains from this moment to completion, rather than only reporting what happened in the past. Percentages, completed-item counts, and filled bars center completion, but the mid-task decision is “how long remains, can I leave, and can I begin something else?” Time remaining, remaining items, remaining stages, or a recoverable completion notification turn progress into decision information.
Why it happens
Waiting judgments are prospective. Two tasks at 80% imply different choices if one has seconds left and the other has a long finalization. Completed proportion is particularly misleading near the end: a small final unit can take most of the time, or the heaviest half may not begin until 50% is shown. A remaining scope supports attention planning, cancellation, backgrounding, and alternatives. Without it, people infer from bar velocity, producing unstable expectation.
Studying it
Across real durations, nonlinear stages, and backgroundable tasks, compare completion-only, remaining-work, and stage-plus-remaining presentations for waiting decisions, leave-and-return behavior, cancellation, and estimate accuracy. Log the gap between system estimates and actual remaining work, and observe whether people treat unreliable time as a precise promise. Distinguish knowing that work continues from being able to organize action around it: the former needs a moving bar; the latter needs understandable remaining bounds and uncertainty.
Where it stops holding
Remaining time is not always computable, and a false countdown destroys trust quickly. Unstable estimation can use ranges, stages, or qualitative language rather than second-level precision. Brief tasks gain only flicker from remaining copy; uncancellable background work may benefit more from a completion notification. Remaining expression also cannot substitute for explaining failure, pause, or a scope change.
Applying it
- Choose remaining expression from the user’s next decision—time, item count, stage, queue position, or completion notice—rather than defaulting to percentage.
- Use ranges or staged language for uncertainty, and explain changed estimates instead of breaking a precise promise.
- Put cancellation, background continuation, and post-completion actions beside remaining information so people can choose by cost.
- Ask testers mid-task whether they would wait, switch work, or cancel. If they can only stare at fill rate and guess, the progress display lacks useful remainder information.