Curatorial essay · 03 of 12

The Honest Lie

Why progress indicators promise more knowledge than software possesses

A progress bar is a measurement, a forecast and a piece of emotional infrastructure—often all at once.

Opening scene

The bar advances rapidly through its first half. At seventy percent it becomes cautious. At ninety-nine it stops. Nothing else changes, yet the final sliver acquires enormous weight. The difference between ninety-nine and one hundred is graphically tiny and psychologically absolute: one means that control may return; the other means the machine still owns the future.

Calling the bar a lie is tempting, but incomplete. Often the program does not know how much work remains. It may discover files as it scans, retry a network request, wait for another process, or complete a final phase whose cost cannot be inferred from earlier phases. The indicator must speak before certainty exists. Its central problem is therefore not dishonesty. It is how to communicate useful confidence without pretending to possess impossible knowledge.

01

Two numbers and a story

Percent done exists only when completed work and total work can be compared.

A determinate progress indicator requires a numerator and a denominator. Counting copied files gives a numerator, but file count is a poor measure when one file is a thousand times larger than another. Counting bytes may improve the estimate until compression, verification or remote processing becomes dominant. Weighting several phases can produce a smoother result, but the weights are based on past runs and may not describe the current machine. Every percentage encodes a model of what counts as work.

The model also needs a story about sequence. An installer might validate, calculate required space, copy files, register components and finalise changes. Microsoft documentation for installer sequence tables treats these as distinct operations, not one uniform stream. If the interface allocates equal visual space to unequal phases, it will sprint and stall. If it allocates historical averages, unusual systems will expose the guess. Smoothness is an aesthetic applied to heterogeneous labour.

02

Evidence without acceleration

Feedback changes tolerance even when it cannot change duration.

Myers' 1985 experiment remains useful because it isolates the experience of feedback. Forty-eight participants encountered a waiting task under different conditions, and 86.1 percent preferred the percent-done version; the paper reported p = .0006. The study does not establish that every bar is effective or that Myers invented the form. It supports a narrower proposition: information about progress can materially improve people's attitude toward a delay that still lasts as long.

The reason is not merely distraction. An indicator helps a person choose. A short remainder may justify staying. A long remainder may permit another task. A stalled value may suggest intervention. The bar turns captivity into planning by offering a forecast, however provisional. When it fails, the injury is correspondingly social. An estimate that repeatedly expands has not only measured poorly; it has caused the person to make poor decisions with their own time.

03

Determinate and indeterminate

Modern standards preserve a distinction that many visual systems blur.

The WHATWG HTML standard distinguishes progress with a known value from progress in an indeterminate state. The same semantic element can represent both, but the states mean different things. A determinate bar claims a measurable fraction. An indeterminate treatment claims only that a task has not finished. Spinning is not a percentage, even when a polished animation makes it feel informative.

Interfaces often move between these states as knowledge changes. A download can be indeterminate until the server discloses a length, determinate during transfer, and indeterminate again during processing. That transition is honest if the labels and semantics change with it. It becomes misleading when designers preserve a confident percentage merely to avoid admitting uncertainty. Uncertainty is not an interface defect. Unlabelled uncertainty is.

04

The politics of the estimate

A remaining-time display allocates responsibility as well as seconds.

A machine saying “three minutes remaining” appears to make a technical forecast, but the message also organises a relationship. It asks the person not to cancel, promises continued activity, and implies that the system deserves three more minutes of trust. When the value becomes four, the system reveals that the earlier confidence was borrowed from the visitor. The emotional response is not irrational. A temporal agreement has been revised without negotiation.

Contemporary queues extend this pattern beyond software. Uploads, deliveries, applications and customer-service systems display stages that may reflect internal work only loosely. Progress becomes institutional speech: an organisation demonstrates that a case exists and asks the person to remain patient. The most ethical indicator is not necessarily the most precise-looking one. It is the one that supports good decisions, reports setbacks, distinguishes activity from animation, and does not convert uncertainty into false certainty for cosmetic calm.

Open bibliography

Records consulted

The essay above is original interpretation, not quotation. These records establish its technical mechanisms, representative figures and historical boundaries.

  1. 01

    ACM · 1985 · paper

    The importance of percent-done progress indicators for computer-human interfaces

    Brad A. Myers' 48-participant experiment: 86.1% preferred the percent-done condition, a result reported with p = .0006. The paper studied rather than invented the progress bar.

  2. 02

    Carnegie Mellon University · 1985 · paper

    The Importance of Percent-Done Progress Indicators (author copy)

    A publicly available author copy of the CHI paper, including experimental procedure, participant counts and the reported preference result.

  3. 03

    WHATWG HTML Standard · living standard · standard

    The progress element

    The modern web platform's distinction between determinate progress and a task whose duration is unknown.

  4. 04

    Microsoft Learn · current · documentation

    Sequence Table Detailed Example

    Documents cost calculation, validation, file operations, registration and finalisation as distinct stages in a transactional installer.

  5. 05

    Nielsen Norman Group · 1993–2024 · paper

    Response Times: The Three Important Limits

    A durable summary of the rough thresholds at which interaction feels immediate, continuous or attention-breaking.

Browse the complete research archive →