• Waits are treated as inevitable. Variability, schedules, and rework create long lines at ERs, call centers, and counters, while trust erodes when time feels idle, uncertain, or unexplained.
• Shape demand and schedule with care. Forecast by 15 to 30 minute intervals, separate short from long work, and staff to service goals so queues never form.
• Fix the factory behind the line. Find the bottleneck, standardize key steps, move prep forward, and parallelize setup so the constraint flows and system-wide delays fall.
• Design the wait experience to feel fair. Give precise ETAs, communicate progress in plain language, offer reliable callbacks, and train updates that prevent recontact and reduce abandonment.

Long waits do more than waste minutes. They trigger anxiety, increase walkouts, and strain trust, which can spill into complaints and staff burnout. Idle time without explanation feels longer and harsher than the clock would suggest, so people remember the wait rather than the service.¹ Psychologically, unfilled and unexplained waits magnify attention on the delay, lower perceived control, and raise anxiety, which stretches perceived time and suppresses satisfaction even when the actual duration is the same.

The math behind lines is straightforward. When arrivals outpace effective capacity, queues grow, and when work boomerangs for rework, the queue grows again.² Visible effort helps because people tolerate delay better when they see work moving in front of them and know what will happen next.⁴ Variability makes the problem bigger. Mixing long and short tasks in one lane creates a lurching flow that stretches tail waits even when averages look fine.⁶ The slowest step sets the overall pace, which is why minutes removed at the bottleneck shorten the entire line.⁷

Well-meaning fixes often disappoint when they ignore how time feels. A screen that says “five minutes” and delivers twenty erodes patience more than silence, which means the estimated time of arrival must be accurate, updated early, and believable. Progress boards and agent scripts help when they show real steps completed rather than vague reassurance, because specific cues restore a sense of control. Appointment templates can also backfire when they favor neat spacing over demand patterns, so schedules need to reflect no-show risk, service time spread, and local peaks.

The experience of waiting is shaped by consistent psychological levers. Unoccupied time drags, so give people something meaningful to do, see, or prepare. Uncertain time drags, so share a window and a reliable next update that teams can meet. Unexplained time drags, so name the step underway in plain language. These small choices make minutes feel fairer, which lowers abandonments, keeps tempers cool, and gives staff room to deliver the work well.

A hospital emergency room at 6 p.m., a utilities call center after a billing drop, and a licensing office on the first Monday of the month share a pattern that operators know well. Demand crests overwhelm staffed capacity, uncertainty rises, and patience falls. Forecasts built on daily averages hide the 9 to 10 a.m. swell at a counter and the 5 to 6 p.m. surge on the phones, which leaves teams scrambling to catch up. When the same lane absorbs quick and complex work without triage, one long case quietly blocks a dozen short ones, and average numbers disguise painful delays that people remember.

Variability multiplies the effect that arrivals create. A single complicated call in a general queue will lurch the line forward in bursts, then stall it again. Short transactions like payments and form updates do not belong behind rare cases of deep troubleshooting, and the reverse is also true. The fix starts with a fast lane and a scheduled lane that protect short work from long work, so each lane flows at the pace it can sustain. Staff feel the difference because their screens and scripts match the type of work in the line rather than starting every conversation from zero.

Waste creeps in when schedules and appointments ignore known patterns. Lunch windows overlap across teams, which creates a daily dip where queues form and linger. Evenly spaced appointment slots look neat but perform poorly when walk-ins crest at known times. Lean practice highlights waiting and over-processing as waste, and both show up when teams retype known information or chase missing documents while customers watch the clock.⁸

Promises often backfire when they lack credibility. A kiosk that says “average wait 5 minutes” while 20 minutes tick by erodes trust that lingers after service completes, because perceived unfairness overrides the number on the screen. Callers hear “two minutes” on a loop and open a second channel, which doubles arrivals without adding capacity. Websites that bury clear self-service for routine tasks push every question to the busiest lane, while urgent issues land in slow channels because callbacks feel uncertain.

The heart of this challenge is design. Coarse forecasts, one-size lanes, and shallow channel guidance create lengthy queues that apologies cannot fix. The antidote is upstream precision paired with clear paths that direct each request to the lane built for it. When demand shaping, triage, and schedules share one screen, queues shrink in both minutes and memory. A small, steady rhythm of weekly forecast review, schedule edits, and script updates will hold gains through seasonality and special events.

Build forecasts at the granularity of the problem and staff to service goals that people can feel. Use 15 to 30 minute blocks that reflect real arrival patterns for each channel, and include realistic allowances for breaks, coaching, and training when you convert targets into scheduled positions.⁵ Share one view across clinical leads, counter managers, and workforce planners so everyone works from the same picture. Publish the plan in a simple calendar that names who covers which crest and what to do if arrival rates deviate.

Separate dissimilar work to lower variability and protect speed. Create a fast lane for narrow-variance tasks and a scheduled lane for complex cases that need deep focus so short work is not trapped behind outliers. In emergency rooms, route simple rechecks and quick treatments to a results-waiting track while abdominal pain and chest pain follow a different route. In call centers, send known short calls to a rapid-response queue and place deep technical calls into scheduled callbacks that hold a steady window.

Reduce waste in schedules and appointments by matching slots to patterns that repeat each week. Move short visits toward peaks and longer visits into calmer periods, and protect a same-day buffer for late breakage so the afternoon does not hit the wall. Lean methods point to over-processing and motion as common sources of wasted time, which appear in service as retyping, searching, and backtracking that stretch slots beyond plan.⁸ Hold a short weekly clinic with planners to adjust templates before the next crest, and retire steps that do not change outcomes.

Adopt a test-and-learn cadence to keep drift from returning. Try a small change in one queue for one week, measure abandonments and tail waits, and decide fast whether to scale or stop. When teams see their changes reflected quickly in the plan, they bring better ideas to the table and protect the gains they helped create. Write down the rule that worked and keep it in a visible place so new staff can follow it from day one.

Even with better forecasts and routing, cycle time balloons when the work itself drags. The slowest step sets the pace for the whole system, which is why a single constraint like bed assignment in an emergency department or supervisor approval at a counter can make the entire line feel slow. Walkthroughs often reveal seconds that repeat at scale, like searching for supplies, retyping known data, and reprinting forms that did not scan cleanly. Those seconds look small in isolation, but add up over a day in ways the average hides.

Emergency departments offer a careful view into the effects and limits of process change. Reviews of triage-related interventions show that splitting flows, moving tasks earlier, and clarifying roles can shorten waits and reduce the number of patients who leave without being seen when executed with discipline.⁴ Critical reviews remind leaders to protect safety and to avoid superficial adoptions that create paperwork on good days and confusion on tough days.⁹ The lesson is to redesign where the time actually goes, measure carefully, and protect clinical judgment while you streamline.

Scheduling rules affect speed in service as much as staffing. Advanced access in primary care places more near-term slots into the schedule and reduces the time between intent and visit, which lowers no-shows and returns fewer people to the queue the following week.¹⁰ Scripts and job aids change rework because keeping methods consistent lowers variability in handling the top cases. Teams that write down the best-known method for handling the top twenty cases and keep it current see fewer errors and faster flow within a month.

Language and updates shape the memory of a wait as much as minutes do. People tolerate delays better when they know what is happening and how long it will take, which puts scripts and progress displays on the critical path for experience.¹¹ Vague updates invite escalation because silence feels like neglect under stress. Specific, believable progress cues calm people and reduce the urge to retry in another channel that would add arrivals.

Design attention belongs at the constraint first, then at the feeders to the constraint, and then at the first touch where work enters. That order keeps teams from spreading effort thin across many small wins that customers cannot feel. Leaders who protect buffer capacity around the constraint guard against the daily lurch that follows small disruptions like a printer jam or a room clean delayed by ten minutes. When the constraint holds, the whole line holds.

Map the current flow and time each step during a typical hour, then circle the slowest step because that is the best first investment. In an emergency department, this might be moving a patient from triage to a bed or waiting for a radiology room. In a call center, it might be identity verification or a specialist consult. In a government office, it might be supervisor approvals or document scanning. Post a one-page map and teach every supervisor how to read it so improvement becomes part of daily management.

Remove rework where it starts by standardizing questions and prefilling what systems already know. Rewrite screens in plain language and validate fields in real time so the most common errors do not make it to the next step. Provide side-by-side job aids for the top cases so new staff and veterans follow the same method under pressure. Hold five-minute huddles to update a single aid each week and retire steps that add clicks without improving outcomes.

Move prep forward and parallelize setup so the constraint sees clean, ready work. In clinics, that means vitals, medication lists, and consent before a clinician enters. In counters, that means document scans and account pulls before a specialist sits down. In contact centers, that means authenticating identity in the interactive voice response so the agent can start on the issue. Build small buffer stocks of supplies at the point of use so a missing label does not stall a busy hour.

Reserve near-term appointment slots for high-friction groups and align templates with known demand patterns so waits do not reappear next week.¹⁰ Keep a same-day buffer that opens at midday so late-breaking demand does not collapse the afternoon. Teach supervisors to watch the constraint first, not the average, and to add help at the feeder steps when minutes begin to climb.

Two families can wait the same twenty minutes and tell very different stories afterward. Psychology explains the gap—idle time, uncertain time, and unexplained time drag.¹ People tolerate delay better when they understand the cause, see progress, and know how long it will take, which shifts design attention to the information people receive while they wait. Explanations that feel fair raise patience because people see that the system is working on their behalf rather than ignoring them.

Operational transparency helps because showing the work makes progress real in the moment.³ A triage board that names steps like labs sent and imaging pending changes the story families tell about the same minutes. A progress bar in a call queue that shows authentication complete and account pulled reduces the urge to hang up and redial. A screen at a counter that displays place in line and the next step replaces a vague “please wait” message that invites frustration.

Announcements about anticipated delay shape behavior when they are believable.¹² Accurate ETAs reduce duplicate arrivals across channels because people do not feel the need to hedge by chatting and calling at the same time. Early updates soften the edge when estimates drift, which keeps patience from turning into aggravation. Believability matters more than optimism because a broken promise poisons the well for the next visit.

Appointment design changes the feel of a wait because a near-term slot beats a long countdown, especially for people with brittle transport or childcare.¹⁴ Templates that hold space within the week reduce missed visits and shrink tomorrow’s queue because today’s work finishes on time. People remember that the system respected their time, which grows trust over weeks rather than single encounters.

Give precise, honest ETAs and update them early.¹² Calibrate estimates with real flow data and display windows that match variability rather than a single optimistic number. Put update times on ER whiteboards and honor them. Tell callers how many people are ahead and offer a callback with a firm window that the system reliably meets. Tell counter visitors both their number and an expected range that narrows as the queue advances. When reality shifts, send an update before patience breaks.

Make progress visible in plain language so minutes feel like movement. Show a checklist of steps, such as triage complete, labs sent, clinician review pending, and discharge in preparation, then tick them off as they happen. Reveal authentication complete, account retrieved, and solution in testing, so callers know that effort is underway. Display documents scanned and approval under review at the counter rather than a static screen. Operational transparency raises perceived fairness and reduces the urge to retry in another lane.

Use contact center playbooks to support the promises you make.¹³ Offer callbacks as a standard choice in interactive voice response and meet the promised window. Right-channel routine work to clear, visible self-service so live help can focus on complex cases without drowning. Publish a simple dashboard that shows service levels by interval so teams can see whether promises match reality during the day. Design appointments that reduce both actual and perceived delay for high-friction groups. Reserve near-term slots, align hours with transit peaks, and send reminders that include travel tips and required documents.

Queueing principles travel well, yet every site runs on its own rhythms. Before changing staffing, hours, or promises, take a week to learn the pattern. Count arrivals in 15 to 30 minute blocks, time the common request types, and note which days swing widest. Turn that into a simple capacity view, try a small tweak on a low-risk shift, and compare before and after. Sharing those results helps teams see why a change sticks.

Operational transparency eases frustration when it shows motion without exposing private details. In health and finance, keep updates plain and scoped to the role. A waiting room board can say labs sent or imaging pending without naming conditions. A contact center can show place in line and expected window without revealing account data. Assign an owner to each display or message so updates land on schedule and trust holds.

Emergency department flow can improve with split streams and earlier tasks, yet safety remains the first check. When you adjust triage rules or create a fast track, watch time to clinician, return visits within 72 hours, and adverse events. Start on one unit or shift, review results with clinical leads, then expand only when time and safety trends move together. A faster door is a win when reliability follows.

Lean tools remove waste when the people who do the work help design the method. Problems surface when a new checklist adds clicks without removing any. Pick one bottleneck, co-create the standard steps, and test during a busy hour to see if the method holds. Remove steps that do not change outcomes. Revisit the process monthly so drift does not erase gains.

Near-term appointment models lower delay in primary care, yet templates need local tuning. Track no-show rates, average visit lengths by service, and seasonal effects like weather and school calendars. Adjust the mix of short and long slots, hold a same-day buffer that opens at midday, and line up late-day capacity with transit and childcare patterns. The goal is a schedule that matches real life and keeps tomorrow’s line from forming today.

Reducing waits is about dignity, safety, and trust. Minutes on hold or in a hallway shape whether people believe their hospital, utility, or agency will be there when it counts. Long queues drain confidence, fuel complaints, and wear down staff. Shorter, more predictable waits free up clinical hours, prevent repeat contacts, and lift satisfaction scores that determine funding and loyalty. The payoff shows up in steadier teams, fewer walkouts, and better outcomes.

Behavioral science turns that goal into practice by focusing on how people experience time. Clear expectations, credible updates, and visible progress ease uncertainty. Simple, timely choices keep the next step within reach. Warm handoffs replace cold referrals so effort does not evaporate between steps. Friction audits reveal where forms, scripts, and screens slow the line. When operations adopt these cues alongside good capacity planning, the clock moves faster and the wait feels fair.

The path forward is a system, not a slogan. Forecast demand at the cadence you serve, protect the few steps that set the pace, and make progress visible where people are waiting. Pair that with lightweight dashboards that report minutes and memory, then adjust weekly. Over a quarter, those habits create a culture where promises match reality and patience grows because people can see work moving in front of them.

The Decision Lab works with public-sector organizations to strengthen these habits across teams and service environments. We combine behavioral design, clear analytics, and practical workflow shifts to help leaders build a steady rhythm of improvement. If your goal is to deliver smoother experiences while protecting quality and staff capacity, we can help you turn pressure points—like long waits—into predictable, well-managed flow.

Wellness Together Canada: Building a 12-second path to care

Read this article for a concrete playbook for shrinking waits in high-stakes environments. The case study walks through demand shaping, triage, and staffing choices that cut access time to seconds, plus design patterns for credible ETAs, reliable callbacks, and multilingual support you can lift into clinics, counters, or contact centers.

Bridging the digital divide: How can we keep healthcare accessible in the digital age?

Here we discuss actionable tactics to make digital front doors reduce waiting instead of creating it. The piece outlines mobile-first flows, plain-language guidance, and in-the-moment help that raise completion rates, with clear steps to boost digital health literacy and bring more people into timely care.

1. Maister, D. (1985). The psychology of waiting lines. In J. A. Czepiel, M. R. Solomon, & C. F. Surprenant (Eds.), The service encounter: Managing employee/customer interaction in service businesses (pp. 113–123). Lexington Books. https://davidmaister.com/articles/the-psychology-of-waiting-lines/
2. Little, J. D. C. (1961). A proof for the queuing formula L = λW. Operations Research, 9(3), 383–387. https://doi.org/10.1287/opre.9.3.383
3. Buell, R. W., Kim, T., & Tsay, C. J. (2020). Creating operational transparency: How and when does showing work work? Management Science, 66(8), 3295–3317 .https://dx.doi.org/10.2139/ssrn.2449029
4. Oredsson, S., Jonsson, H., Rognes, J., Lind, L., Göransson, K. E., Ehrenberg, A., Asplund, K., Castrén, M., & Farrohknia, N. (2011). A systematic review of triage-related interventions to improve patient flow in emergency departments. Scandinavian Journal of Trauma, Resuscitation and Emergency Medicine, 19, 43. https://doi.org/10.1186/1757-7241-19-43
5. Gans, N., Koole, G., & Mandelbaum, A. (2003). Telephone call centers: Tutorial, review, and research prospects. Manufacturing & Service Operations Management, 5(2), 79–141. https://doi.org/10.1287/msom.5.2.79.16071
6. Kingman, J. F. C. (1961). The single server queue in heavy traffic. Mathematical Proceedings of the Cambridge Philosophical Society, 57(4), 902–904. https://doi.org/10.1017/S0305004100036094
7. Hopp, W. J., & Spearman, M. L. (2014). Factory physics (3rd ed.). Waveland Press. https://doi.org/10.1111/poms.12188
8. Womack, J. P., & Jones, D. T. (1996). Lean thinking: Banish waste and create wealth in your corporation. Simon & Schuster. https://www.simonandschuster.com/books/Lean-Thinking/James-P-Womack/9780743249270
9. Holden R. J. (2011). Lean Thinking in emergency departments: a critical review. Annals of emergency medicine, 57(3), 265–278. https://doi.org/10.1016/j.annemergmed.2010.08.001
10. Murray, M., & Berwick, D. M. (2003). Advanced access: Reducing waiting and delays in primary care. JAMA, 289(8), 1035–1040. https://doi.org/10.1001/jama.289.8.1035
11. Hui, M. K., & Tse, D. K. (1996). What to tell consumers in service encounters: The effects of verbal statements on perceived waiting time and satisfaction. Journal of Marketing, 60(2), 81–90. https://doi.org/10.1177/002224299606000206
12. Whitt, W. (1999). Improving service by informing customers about anticipated delays. Management Science, 45(2), 192–207. https://doi.org/10.1287/mnsc.45.2.192
13. Aksin, Z., Armony, M., & Mehrotra, V. (2007). The modern call center: A multi-disciplinary perspective on operations management research. Production and Operations Management, 16(6), 665–688. https://doi.org/10.1111/j.1937-5956.2007.tb00288.x
14. Gupta, D., & Denton, B. (2008). Appointment scheduling in health care: Challenges and opportunities. IIE Transactions, 40(9), 800–819.https://doi.org/10.1080/07408170802165880