The short answer
Queues feel shorter when uncertainty is replaced by a controlled wait. Give a realistic, slightly conservative estimate; explain the reason for the delay; update progress as the position changes; and acknowledge the person as soon as they arrive. Research shows customers respond better to a known, explained wait than to an unknown one, even when actual minutes are unchanged.
Key takeaways
- Perceived time matters more than clock time: people overestimate waits when they do not understand what is happening.
- A known, finite wait feels shorter than an unknown wait, so an estimate beats silence or a vague 'just a moment'.
- A conservative estimate you beat improves satisfaction, but an implausibly large cushion drives customers away.
- Explaining the delay and sending frequent progress updates reduce anxiety even when the line has not moved faster.
- Highlighting that someone is last in line increases discomfort; it is better to state how many people are ahead.
Perceived time is not the same as clock time
People evaluate waiting through a sense of control and understanding, not by a stopwatch. David Maister's classic work on the psychology of waiting lines remains the foundation for much of queue communication: occupied time feels shorter than unoccupied time, and a known finite wait feels shorter than an unknown one.
Field observations and practitioner data point in the same direction. In queue management discussions, a commonly cited estimate from MIT professor Richard Larson is that people overestimate how long they have waited by roughly 36 percent. That means improving communication can often deliver more value than shaving a minute off the actual service time.
- The same two minutes can feel instant or endless depending on information and engagement.
- Anxiety and ignorance stretch subjective time more than the delay itself.
- A service-related distraction fills the wait and reduces irritation.
Underpromise and overdeliver, but watch the size of the cushion
Research on virtual queues and call centers, summarized in a Harvard Business Review column, found four practical effects: providing wait-time estimates lowers overall waits, pessimistic estimates are preferable to optimistic ones, frequent progress updates improve the experience, and customers who wait longer than promised take longer once they are served.
A separate field experiment in emergency departments found that announcing an overestimate of wait time improved patient satisfaction more than announcing the average. Patients appeared to treat the announced time as a reference point: beating it felt like a gain, while exceeding it felt like a loss.
The cushion must remain believable. An estimate that promises an hour when the real wait is ten minutes will make some people leave before service begins and make others suspicious of manipulation.
- State a range or an upper bound rather than one precise minute.
- Make the forecast moderately conservative so you can usually beat it.
- Keep the cushion plausible enough that people do not abandon the queue.
- A plausible upper bound is safer than an optimistic single number.
Explain the wait and keep the explanation honest
An unexplained delay reads as indifference, while a short explanation converts an anonymous wait into a process. Maister noted that unexplained waits feel longer than explained waits, and that customers repeatedly ask staff what is happening. The explanation does not have to excuse the organization; it has to be true and specific enough to remove the main uncertainty.
Operational transparency research adds another layer: when customers see that work is being done on their behalf, they can value the service more even if the wait is longer. The perceived effort and the explanation together create a sense that the delay is justified rather than arbitrary.
Honesty matters at the moment the plan changes. If the initial estimate can no longer hold, say so promptly and provide a revised one. Repeating 'just a few more minutes' while the wait grows is more damaging than one uncomfortable update.
- Give a short, truthful reason: a rush, a staffing gap, a safety check.
- Name the cause before the customer asks for one.
- Revise the forecast clearly when conditions change.
- Avoid repeated optimistic promises that are not confirmed by progress.
Progress updates and position: avoid the last-place effect
Telling people where they stand can reduce anxiety, but the frame changes the result. Research by Ryan Buell described a 'last place aversion' effect: someone who sees themselves at the back of a queue experiences markedly more discomfort and is more likely to switch lines or leave, often wasting more time than if they had stayed.
The practical rule is to state how many people are ahead rather than emphasizing that the customer is last. 'There are three people ahead of you' lands better than 'You are fourth of four.' The same applies in call centers and app-based virtual queues.
Frequent progress notifications also provide a feeling of motion. A brief update showing that the position has improved acts as proof that the process is working, even when the change is small.
- Describe people ahead, not the customer's position as the final one.
- Confirm early that the request has entered the system.
- Send short progress updates to show movement.
- Avoid framing the queue as a fixed, unchanging block.
Where communication fails: vague, static, or too-optimistic messages
The most damaging message is no message. Silence leaves customers unable to decide whether to stay or leave, and they keep re-estimating the wait. The second failure is an overly optimistic estimate: promising five minutes and delivering fifteen produces stronger dissatisfaction than honestly saying twenty.
Static signage is a related problem. A sign that says 'wait up to 15 minutes' all day loses credibility as soon as it fails to match reality. Effective displays show current queue length, recent average waits, and a live status that changes with conditions.
Finally, the message must be consistent across channels. If the screen, the app, and the staff member give different numbers, trust falls and perceived time grows. Synchronized estimates are just as important as the estimates themselves.
- Silence increases anxiety and the urge to abandon.
- A too-optimistic promise creates an expectation that is easy to break.
- An implausibly long estimate pushes customers away before service begins.
- Mismatched information across channels destroys trust.
Put it into practice
Wait-time communication checklist
Use this checklist before publishing an estimate on a screen, sending a queue notification, or briefing staff on what to tell waiting customers.
- State a range or upper bound instead of a single precise minute.
- Make the forecast moderately conservative so you can often beat it.
- Give a short, truthful reason for the delay in one sentence.
- Tell people how many are ahead rather than that they are last.
- Update the status whenever a position changes or at least every five to ten minutes.
- Offer a service-related activity: a form, a guide, or a short explainer.
- When a disruption occurs, revise the forecast honestly and explain the new timing.
- Train staff to acknowledge a customer's presence within the first moments of waiting.
Questions people ask
How is perceived waiting time different from actual waiting time?
Actual waiting time is measured in clock minutes, while perceived time is the subjective experience of duration. People often overestimate how long they have waited, especially when they do not know how much longer it will take or why the delay is happening. This is why clear communication can improve satisfaction without making service faster.
Should I overstate the wait time so customers are served sooner than promised?
A moderate overstatement usually helps. Customers compare the actual wait with the announced reference point, and finishing earlier than promised feels like a gain. But the cushion must be believable. An unrealistically long forecast can drive people away before they even start waiting and may look like manipulation.
How often should wait time information be updated?
Update it more often than feels necessary. Refreshing the estimate whenever a position changes, or at least every five to ten minutes, gives people visible proof of movement and preserves a sense of control. When the queue suddenly grows or a disruption occurs, send a proactive update instead of waiting for complaints.
Is it worse to say nothing about the wait or to give an inaccurate time?
Saying nothing is usually the worst option because uncertainty makes the wait feel longer and makes customers anxious about whether they have been forgotten. A highly optimistic estimate is also harmful because it creates an expectation that is easy to miss. A honest range with a small cushion, updated as conditions change, is the safer choice.
Why does telling someone they are last in line make the wait feel worse?
Being at the back of a queue triggers a strong sense of disadvantage, which researchers call last place aversion. People in that position are more likely to switch lines or leave, often wasting more time than if they had stayed. Communicating the number of people ahead is a more useful and less stressful frame.
Do I need to explain a delay if the reason seems obvious?
Yes. Even a brief explanation such as 'we are processing two urgent requests' transforms an anonymous delay into a comprehensible process and reduces the feeling of unfairness. The explanation does not have to fully excuse the organization; it simply needs to be truthful and specific enough to remove the main uncertainty.
Sources and further reading
Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.
- The Psychology of Waiting LinesDavid Maister
- The Labor Illusion: How Operational Transparency Increases Perceived ValueEconPapers / RePEc
- HBR: It pays to underpromise and overdeliver on wait timesUniversity of Cincinnati
- Under-Promising and Over-Delivering to Improve Patient Satisfaction at Emergency Departments: Evidence from a Field Experiment Providing Wait InformationKellogg School of Management
- Ожидание в «хвосте» очереди заставляет терять больше времени впустуюNaked Science
- How to Reduce Waiting Times with Queue ManagementJRNI