A 20-Minute Wait Can Feel Better Than Ten Minutes of Uncertainty
- 1 day ago
- 4 min read
A customer who is told there will be a 20-minute wait can make a decision. They can order a drink, browse nearby, answer an email, settle the children or simply decide the experience is worth it. A customer who is told, ‘It won’t be long’, then hears nothing for ten minutes has a different problem. They are no longer waiting for the product or service. They are waiting for certainty.
Experience-led businesses often treat waiting as a capacity problem: add staff, speed up service, shorten the queue, turn the table faster. Sometimes that is exactly the right answer. But many of the most damaging waits are not long enough to justify major operational change. They become expensive because nobody designed what the customer should know while the delay is happening.
Customers judge the uncertainty before they judge the clock
Waiting becomes stressful when the customer cannot predict what happens next. A hotel guest standing at reception does not know whether the room will be ready in five minutes or fifty. A restaurant guest whose table is delayed cannot tell whether ordering another drink is sensible. A spa customer sitting alone after a treatment may wonder whether someone has forgotten them. The practical inconvenience might be modest, but the information gap forces the customer to keep reassessing the situation.
This is why an honest estimate often creates a better experience than an optimistic one. If you say ten minutes because it sounds reassuring and it becomes twenty-five, you have converted a delay into a broken promise. If you say twenty minutes, explain what is happening and update the customer when reality changes, you preserve trust even when the operational outcome is identical.
Research into restaurant waiting behaviour has also examined how the way wait-time information is communicated affects customer decisions. The practical lesson is useful: information about the wait is part of the experience, not an administrative detail. See the research here.
The operating problem starts before the queue forms
Frontline teams are often blamed for vague answers when the real problem sits further back in the system. They cannot give a useful estimate if nobody has defined the capacity limit, if the reservation system does not show the right information, if housekeeping cannot update room status reliably, if the kitchen has no visible measure of ticket pressure, or if security and admissions teams are working from different assumptions.
In those businesses, ‘won’t be long’ becomes a survival phrase. Staff use it because the operating model has given them responsibility for reassurance without giving them the information needed to be accurate. Training people to sound more confident will not fix that. The information, ownership and escalation rules have to exist first.
We explored the same principle in Your Event Starts Before the Doors Open. Arrival pressure is rarely one department’s problem. Parking, scanning, security, wayfinding, staffing and exception handling combine into one customer judgement: is this place under control?
Good waiting has four ingredients
A well-designed wait gives the customer four things. First, a believable expectation: what is likely to happen and roughly when. Second, visible progress: some evidence that the system is moving rather than stalled. Third, an update rhythm: the customer should not have to chase to discover whether the estimate has changed. Fourth, a recovery trigger: there needs to be a defined point at which the wait stops being normal and somebody takes ownership of fixing the experience.
None of this requires turning hospitality into a script. In fact, rigid scripts often make waiting worse because they force staff to repeat phrases that have stopped being true. A standard is more useful: tell the truth, give the best available estimate, update before the customer has to ask, and escalate when the agreed threshold is breached. The human delivery can still sound human.
This is also why speed is not the same thing as service. A premium business does not need to eliminate every pause. It needs to make the right pauses feel intentional, understood and worth the customer’s time.
Design the information system, not just the queue
The useful leadership question is not simply, ‘How do we reduce waiting time?’ It is, ‘At every point where a customer might wait, what do we know internally, what does the customer know, and who is responsible for closing the gap?’ That changes the work. You start looking at status visibility, handovers, ownership, thresholds, update prompts and the quality of the estimate itself.
Take a restaurant with a delayed table. The host needs more than a polished apology. They need a realistic view of table status, the authority to offer an appropriate alternative, a clear point at which the manager becomes involved and a way to update the guest without being reminded. If any one of those pieces is missing, the customer becomes the project manager of their own experience.
The same logic applies to hotel check-in, spa transitions, click-and-collect, premium retail consultations, event entry and customer support. The clock matters, but the design of uncertainty often matters first.
The leadership test
Walk the customer journey and mark every point where someone can be left waiting. Do not only time the delay. Record what the customer is told at the start, what changes during the wait, how they know progress is being made, who owns the update and what happens when the normal threshold is exceeded. Then compare that with what the team actually knows internally. The gaps between those two views are where frustration grows.
If leadership discovers that staff are routinely guessing, apologising without information or waiting for customers to chase, the issue is bigger than service language. It is a Customer Experience and Operational Excellence problem sitting in the same place.
Audit the wait as part of the whole experience
A Q Branch Customer Experience Audit looks at the real journey rather than the journey written in a process document. That includes the promises made before arrival, the moments where customers wait, the information teams have, the standards they work to, the handoffs that create uncertainty and the operating conditions that make good service easier or harder to repeat.
Reducing a 20-minute wait to fifteen can be useful. Turning ten minutes of unexplained uncertainty into ten minutes the customer understands can sometimes be more valuable. The customer does not need perfection. They need enough confidence to believe somebody knows what is happening and is still in control of the experience.
Comments