Anxiety in waiting comes from uncertainty, not duration

What it is

Waiting a long time is not what mainly produces anxiety; not knowing how long the wait will be, and not knowing whether the system is still working, is. This is the uncertain wait: a silent stretch with no duration information and no progress indication hurts more than a longer wait whose endpoint is known. It is not the same problem as "slow": slow is about time, this is about the user losing two judgment inputs mid-wait — the expected end and a sign of life — and anxiety grows out of exactly those two gaps.

Why it happens

An uncertain wait traps the user in a decision with no information that repeats every moment: keep waiting, or give up now — and neither option's consequence is visible. Quitting may waste time already invested; staying may mean facing a failure that happened long ago. Silence also reads as a precursor of bad news by default: healthy states speak (streaming text, items appearing one by one), broken states go quiet, so no progress gets interpreted as "is it frozen?" Anxiety accumulates through the explanatory vacuum — whatever explanation the interface withholds, the user supplies with worst-case assumptions. Known duration and visible progress change the structure of that decision rather than making people patient: once the remaining time is known, waiting turns from a gamble into a plan; the user parks the wait alongside their own business (switch windows, check a message, come back), the decision pressure disappears, and tolerance stretches far beyond what the clock alone predicts. The same minute is a burden when unknown and a budget when known.

Studying it

• Threat-uncertainty paradigm: participants wait for an electric shock whose probability is experimentally manipulated; physiological arousal and self-reported stress peak in the maximally uncertain region (roughly a coin flip), not where the outcome is worst — stress tracks the estimated uncertainty, not the value of the outcome. Estimating participants' momentary uncertainty with a learning model predicts the shape of the stress curve.
• Choice experiments on anticipatory dread: offered a choice between an unpleasant event happening sooner versus after a longer delay, with payment allowed to move it earlier, many people pay to get it over with — the waiting period itself generates continuous disutility (dread) rather than merely leading to it, and uncertainty amplifies that per-minute cost.
• Field studies of medical waiting: in high-stakes settings such as preoperative waiting and waiting for diagnostic results, patients who are told the expected duration and what happens next report lower state anxiety than those left uninformed; qualitative interviews on result-waiting repeatedly rank it as the most distressing segment of care, sometimes worse than receiving bad news itself.
• Methodological cautions: this literature mostly involves single, high-stakes waits measured in minutes to weeks; effect sizes do not transfer directly to second-scale UI waits. Probing anxiety repeatedly during a wait changes the wait itself — design real-time and retrospective measures as separate studies.

Where it stops holding

• This claim is about the source of anxiety, not about all costs of waiting: a known but very long wait still produces irritation and abandonment — information converts anxiety into planning, and planning can conclude "not worth waiting." Progress indicators rescue emotion, not retention.
• Dishonest promises flip the result: a progress bar that fills without finishing, or an estimated time that passes without explanation, turns "known duration" back into "unknown" — worse than never having promised. After a misestimate, update explicitly and explain; do not go silent.
• Individual differences exist: the coping-style literature distinguishes information-seeking (monitors) from information-avoiding (blunters), and more information can make the latter more tense. Interfaces rarely adapt per person, but making details opt-in rather than full-screen mandatory leaves both groups a path.
• Waits under a second need no indicator at all; adding one is noise. The claim's territory begins where waits get long enough for users to start doubting the system.

Applying it

• Audit every wait point longer than a few seconds and supply both missing pieces: a progress indication (which step is done) and an expected duration (roughly how much longer); where neither can be computed, at least state what the system is doing right now ("compressing photos, 24 of 58").
• When remaining time is genuinely unknowable (uploads of unknown size, external dependencies), show what has been completed instead of faking a percentage — "3 of 7 files processed" never lies; a fake progress bar does.
• Say the state out loud for auto-retries and queues: "Retrying, attempt 2 of 3" beats a silent spinner.
• Give estimates as ranges or conservative values, and when a deadline is about to slip, update proactively with a reason.
• To validate: instrument where in the wait users abandon and look for cliffs; during usability tests of long waits, ask "do you believe it's still working, and how much longer?" — every wait the participant cannot answer for is unfinished.

Related

• Same group: P1.14.2 Failure messages must offer a next step, not just describe a state · P1.14.3 Recoverability beats wording in loss scenarios · P1.14.4 Attribution framing decides whether users blame themselves or the system
• Nearby: I2 Loading & waiting · P1.03.3 Negative peaks are amplified in memory too
• Search terms: uncertain wait · progress feedback · dread · state anxiety · stress and uncertainty