The Psychology of Waiting: It Was Never Really About Those 5 Seconds
Three laws of waiting with Disney and Houston airport cases; drag the duration slider across three presentation tiers: under 1s show it raw, under 10s must stream, over 10s go async
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat is the key idea behind “The Psychology of Waiting: It Was Never Really About Those 5 Seconds”?
Three laws of waiting with Disney and Houston airport cases; drag the duration slider across three presentation tiers: under 1s show it raw, under 10s must stream, over 10s go async
Turn taste into a behavior the product can repeat. The useful outcome is not a nice opinion. It is a visible rule, a small example, and a way to tell when the experience falls below the bar.
Capture one before-and-after example that shows the quality bar without extra explanation.
Polish that improves the surface while leaving the user's uncertainty untouched.
HCI research has a set of classic thresholds used for decades, from Jakob Nielsen's Usability Engineering (1993, tracing back to Miller 1968): under 0.1s feels instantaneous, under 1s keeps the train of thought, 10s is the limit of focused waiting. Those three lines cut three presentation strategies. Drag the slider, enter your feature's real duration, and see which tier it lands in—and how to present it.
Management scholar David Maister laid down a set of waiting-line laws in his 1985 paper The Psychology of Waiting Lines. Theme parks, banks, and airports have used them for forty years. Two textbook cases—worth reading number by number.
Price the wait in the open—and deliberately overstate it
The board at the queue entrance says “40 minutes from here”, while most of the time you're through in 30. Guests aren't annoyed—they feel they gained 10 minutes. Knowing how long you'll wait lets the brain plan; without a scale, it defaults to worst-case anxiety.
The line itself is designed too: the switchback makes you shuffle forward every few dozen seconds, and scenery plus preview clips give your hands something to do. The same physical duration becomes an experience of “always advancing, always occupied.”
Complaints hit zero—by making passengers walk more
Passengers complained about waiting for bags. The airport added staff and cut average wait to 8 minutes—complaints stayed. Digging into the data revealed the real issue: walking from gate to carousel took 1 minute; the remaining 7 minutes were pure standing around.
The later fix didn't shave a second: they moved the arrival gate farther out and routed bags to the farthest carousel, so passengers walked 6× farther and arrived just as bags came out. Total time unchanged; complaints nearly vanished. People who are walking feel progress; people who are standing feel waiting.
From Maister's set, three laws hit AI products hardest. Each gives you a pair of UIs—toggle the bad pattern and the good one yourself, and watch the anxiety score move. The spinners and progress bars in all three panels are live; watch a few seconds and the feel gets real.
Law ① · Uncertain waits feel longerDid you say how long?
No scale, the brain anxietizes for the worst case—around second 10 it starts suspecting a hang.
Law ② · Unexplained waits feel longerDid you say what's happening?
A bare spinner only answers “alive or dead,” not “what is it doing”—the brain fills in the worst script.
Law ③ · Empty-handed waits feel longerIs there something in hand?
Three blank seconds can feel like someone else's ten. Eyes with nowhere to land make the stopwatch crawl.
Scene: the user asks an Agent to review a 50-page procurement contract—about 25 seconds total. Left is the chat UI, currently stuck on a bare “Analyzing…”. Right, four design moves map to the laws you just learned—check them one by one, watch the UI grow, and see how far anxiety drops.
① Payment terms: 90-day cycle is long
② Missing cap on liquidated damages
③ IP ownership is fuzzy…
Law ①Give an estimate—and pad it high
Quote a high historical percentile as “30 seconds”; finishing in 25 is a free surprise. The wait goes from a bottomless pit to a countdown.
Law ②Report progress by stage
Say what you're doing each time the stage changes—silence becomes a live feed. Lesson 3 will reuse these intermediate states: they also vouch for capability.
Law ③Stream the outline first
Give the analysis frame in 5 seconds; the user reads and confirms priorities—hands aren't empty, so the stopwatch stops.
Change formOffer background + done notification
Give an exit they can take anytime. Most won't click—but knowing they can leave turns waiting into something with an escape hatch.
Nielsen's 10-second line is a product-form boundary. Past it, keeping the user in a synchronous stare guarantees attention loss—that's not a UX flaw, it's a design accident. The right move: turn sync waiting into a background task. Hit the button below and watch the whole pattern run.
Let's tally the bill. The LLM fundamentals part covered streaming from chat/completions; the hands-on build part covered Agents' visible progress. In this lesson they show up as psychology tools. So here's the question—answer first, then look at the invoice.
Turn the feeling in “Hands-on · First, dial in your task duration” into a judgment
“HCI research has a set of classic thresholds used for decades, from Jakob Nielsen's Usability Engineering (1993, tracing back to Miller 1968): under 0.1s feels instantaneous, under…” points out that AI has lowered the bar for making something usable. The skill readers need is noticing what is wrong and turning that feeling into an actionable requirement.
Watch the user's next action, not just the surface
Turn “Management scholar David Maister laid down a set of waiting-line laws in his 1985 paper The Psychology of Waiting Lines .” into observable questions: does the user know what happened, what to do next, and how to recover from an empty or failed state? Does the hierarchy make the important information visible first?
- Tier the task first : under 1s show it raw; 1–10s must stream with progress; past 10s go background with notification
- Fix presentation against the three laws : give an estimate, give an explanation, put something in hand—anxiety drops one by one
- Pad estimates high, never low : quote 40 minutes and finish in 30 and it's a surprise; the reverse is betrayal
Pretty is not the same as usable
Apply “Let's tally the bill.” to a second screen or flow. Record one moment of hesitation and the user action after the change; observable behavior is stronger evidence than polish alone.
From “Hands-on · First, dial in your task duration” to “Thesis first · Disney and airports already ran the answer”
“Hands-on · First, dial in your task duration” grounds the problem in “HCI research has a set of classic thresholds used for decades, from Jakob Nielsen's Usability Engineering (1993, tracing back to Miller 1968): under 0.1s feels instantaneous, under 1s keeps the train of thought…”. “Thesis first · Disney and airports already ran the answer” then moves it toward “Management scholar David Maister laid down a set of waiting-line laws in his 1985 paper The Psychology of Waiting Lines . Theme parks, banks, and airports have used them for forty years. Two textbook cases—wort…”. Together, they show that the lesson is not just a conclusion to remember, but a claim with conditions.
Carry the judgment into the next situation
For experience work, turn abstract impressions into user actions: did the person understand the state, find the next step, recover from an error, and want to continue?
- “Hands-on · First, dial in your task duration”: HCI research has a set of classic thresholds used for decades, from Jakob Nielsen's Usability Engineering (1993, tracing back to Miller 1968): under 0.1s feels instantaneous, under 1s keeps the train of thought…
- “Thesis first · Disney and airports already ran the answer”: Management scholar David Maister laid down a set of waiting-line laws in his 1985 paper The Psychology of Waiting Lines . Theme parks, banks, and airports have used them for forty years. Two textbook cases—wort…
- “The closing point”: Fix presentation before latency : most “too slow” complaints need zero model changes—and the bill is an order of magnitude cheaper
The final “The closing point” brings the discussion to “Fix presentation before latency : most “too slow” complaints need zero model changes—and the bill is an order of magnitude cheaper”. The useful thing to carry forward is knowing which judgments must be revisited when input, scale, or risk changes.
✅ What this lesson wants to share
- Tier the task first: under 1s show it raw; 1–10s must stream with progress; past 10s go background with notification
- Fix presentation against the three laws: give an estimate, give an explanation, put something in hand—anxiety drops one by one
- Pad estimates high, never low: quote 40 minutes and finish in 30 and it's a surprise; the reverse is betrayal
- Fix presentation before latency: most “too slow” complaints need zero model changes—and the bill is an order of magnitude cheaper
I turned one judgment from this article into a small experiment I could run today. Knowing what to observe next is more useful than simply remembering the conclusion.
After reading this, I first looked for the conditions behind the idea instead of copying the method into a project. That order made the later trade-offs much clearer.
When this judgment reaches real work, which constraint should be added first? I am curious which step matters most between reading and the first practical attempt.
No discussion on this article yet.