Queue Management That Doesn't Rely on Heroes
Every volume-based team has one: the reliable person who quietly clears the backlog. It works — until they take leave. The difference between queues that flow and queues that accumulate is design, not heroics.
Every volume-based team has one. The reliable person who knows what is urgent, remembers what is stuck, and quietly clears the backlog before it becomes a problem. When work piles up, they absorb it. When something is about to slip, they catch it.
It works. Until they take leave.
Then the queue reveals what it really was: not a system, but a person. Work that used to flow starts to accumulate. Nobody knows what is urgent. Items that were "being handled" turn out to have been handled only in one person's head.
This is the difference between queues that flow and queues that accumulate. Flowing queues run on design — visibility, prioritisation, assignment, and escalation that anyone can operate. Accumulating queues run on heroes. And heroes go on holiday.
The test of a healthy queue
A queue is healthy when it keeps flowing regardless of who is present. If the backlog depends on one person's memory, diligence, or goodwill, you do not have a queue — you have a single point of failure with a to-do list.
Why queues accumulate
Work does not pile up at random. It piles up for identifiable, structural reasons — and naming them is the first step to fixing them.
Research from MIT Sloan Management Review on organisational bottlenecks makes a useful distinction: work stalls for one of two reasons. Either it depends on the output of other tasks that have not been completed — a task bottleneck — or the resources required to complete it are not available — a resource bottleneck. Task bottlenecks frequently occur as teams wait for approvals from other functions, such as legal or compliance .
The distinction matters because the fixes are different. Throwing more people at a task bottleneck does not help if the work is waiting on an approval that only one team can give. And the article's larger point applies directly to queues: bottlenecks are best managed by taking a holistic view of the work system, not by addressing them piecemeal . A hero clearing today's backlog is the definition of piecemeal — it moves the pile without changing the system that produced it.
Heroics hide the real problem
When a reliable individual absorbs the overflow, the queue looks healthy while the underlying design stays broken. The heroics mask the very signals that would tell you where the system needs fixing.
The four signals of queue health
A queue that flows without heroes has four things working together. Each can be observed, each can be measured, and each has a specific fix when it is missing.
Four Signals of Queue Health
Click each signal to explore what healthy looks like
A queue you cannot see is a queue you cannot manage. Visibility means every piece of work lives in one place, with a status anyone can read at a glance. When work hides in inboxes, chat threads, and side spreadsheets, it depends on the memory of whoever is holding it — the definition of a hero-dependent queue.
- •All incoming work lands in one intake, not scattered channels
- •Every item has a visible status anyone on the team can read
- •Nothing lives only in one person's inbox or head
- •Work arrives through DMs, emails, and hallway requests
- •Only the person handling an item knows where it stands
- •Status is reconstructed from memory in stand-ups
Create a single intake and one shared, visible queue. If it is not in the queue, it does not exist. Visibility is the precondition for every other signal.
Healthy queues track how long each item has been waiting and surface the oldest first. Without aging discipline, work quietly grows stale — the newest, loudest, or easiest items get picked while older ones sink to the bottom. Aging is where fairness and reliability quietly break down.
- •Age is tracked on every item and visible in the queue
- •The oldest work is surfaced, not buried
- •Clear time targets exist for how long work should wait
- •No one can name the oldest item in the queue
- •New or easy work gets picked ahead of aging work
- •Items age out silently until someone complains
Track age on every item, surface the oldest first, and set explicit time targets. Make aging work visible so it cannot be ignored in favour of fresher, easier items.
Balance is whether work is distributed according to capacity and skill — or whether one reliable person quietly absorbs whatever no one else picks up. Hero-dependent queues look fine until the hero takes leave. Balanced queues assign work by rule, so no single person is a single point of failure.
- •Work is assigned by capacity and skill, not by who volunteers
- •No single person carries a disproportionate share
- •The queue keeps flowing when any one person is away
- •One person consistently clears the hardest or oldest work
- •Pickup is voluntary, so load drifts to the conscientious
- •Coverage collapses when a key person is on leave
Replace voluntary pickup with assignment rules that route work by capacity and skill. Design the queue so it survives any one person being absent.
Escalation clarity means the triggers, the path, and the response are defined in advance — not improvised when something is already on fire. Without it, escalation depends on whoever happens to be paying attention. With it, the right item reaches the right person before it becomes a crisis.
- •Clear triggers define what gets escalated and when
- •A named path exists — people know exactly who to reach
- •Expected response times are agreed, not assumed
- •Escalation happens only when someone notices and shouts
- •People are unsure who owns a stuck or urgent item
- •The same emergencies recur because triggers are informal
Define escalation triggers, a named path, and expected response times up front. Make escalation a system, not an act of individual vigilance.
Tap the progress bar or cards above to navigate between the four signals
The four signals are not independent. Visibility comes first because you cannot manage what you cannot see. Once work is visible, aging tells you whether it is being handled fairly, balance tells you whether it is distributed safely, and escalation clarity tells you whether the exceptions are caught by design rather than by luck.
Visibility: the precondition for everything
You cannot manage a queue you cannot see. When work arrives through scattered channels — emails, chat messages, hallway requests, a form here and a spreadsheet there — no one holds the complete picture. The person who comes closest becomes the hero by default, because only they know what is actually outstanding.
Visibility means one intake and one shared queue where every item has a status anyone can read. It sounds basic. It is also the single most common thing missing in hero-dependent operations, because informal channels feel faster in the moment and only reveal their cost when the person holding the context is unavailable.
Aging: where fairness quietly breaks
Once work is visible, the next question is how long each item has been waiting — and whether the oldest work is being surfaced or buried.
Without aging discipline, queues drift toward the newest, loudest, or easiest items. Older work sinks to the bottom, not through any decision, but through the natural gravity of a busy team picking what is in front of them. The result is silent unfairness: some requests are handled in hours while others age for weeks, and no one chose that outcome.
How work waits is not a neutral detail. Decades of service research have examined the experience of waiting and the factors that affect people's tolerance for it, offering testable propositions and specific managerial guidance on managing queues . The operational lesson is direct: unexplained, invisible waiting erodes trust — both from the people waiting and from the team handling the work. Tracking age and surfacing the oldest items first turns waiting from an accident into a managed decision.
Make aging impossible to ignore
Track age on every item and surface the oldest first. When aging work is visible in the queue, it competes for attention on equal terms with the fresh, easy items that would otherwise jump ahead of it.
Balance: designing out the single point of failure
Balance is whether work is distributed by design or by accident. In hero-dependent queues, pickup is voluntary — so load drifts to the most conscientious person, who absorbs whatever no one else takes. It looks like dedication. It is actually concentrated risk.
The fix is to replace voluntary pickup with assignment rules that route work by capacity and skill. The goal is not to remove judgment but to remove dependence: the queue should keep flowing when any one person is away. If the honest answer to "what happens when our best person is on leave?" is "the backlog grows," balance is the signal to fix.
Escalation clarity: catching exceptions by design
Most queues have exceptions — items that are stuck, urgent, or outside the normal path. Escalation clarity is whether those exceptions are caught by a system or by a vigilant individual.
Without it, escalation happens only when someone notices and raises the alarm. That someone is usually the hero. With clear triggers, a named path, and agreed response times, the right item reaches the right person before it becomes a crisis — and it does so whether or not any particular person is watching.
A practical diagnostic
How much does your queue rely on heroes rather than design? The assessment below scores five dimensions and shows where your queue is most exposed when the right person is unavailable.
Queue Resilience Assessment
Question 1 of 5
If someone asked to see every open item your team is responsible for right now, how quickly could you show them?
Building a queue that runs itself
Moving from heroics to design is a sequence, not a single change. The order matters.
Start with visibility. Get all incoming work into one intake and one shared queue. Until work is visible, nothing else can be managed. This single step often reveals how much was previously carried in someone's head.
Add aging. Track how long each item has waited and surface the oldest first. Set explicit time targets so aging work cannot be quietly ignored.
Replace pickup with assignment. Route work by capacity and skill rather than relying on whoever volunteers. Design so the queue survives any one person's absence.
Define escalation up front. Agree the triggers, the path, and the response times before the next emergency — not during it.
The compounding benefit
A queue built on these four signals does not just survive when a key person is away — it frees that person from firefighting. The hero stops being a single point of failure and starts being someone who can improve the system instead of holding it together.
Final thoughts
The reliable person clearing the backlog is not the solution to a queue problem. They are what a queue problem looks like before it becomes visible.
Queues that flow without heroes share four traits:
- Work is visible in one place, not scattered across channels and memories
- Aging is tracked, so the oldest work is surfaced rather than buried
- Load is balanced by rule, so no single person is a single point of failure
- Escalation is defined in advance, so exceptions are caught by design
The heroics feel like strength. In a well-designed operation, they should rarely be necessary.
When your most reliable person takes a week off, does your queue keep flowing — or does it reveal how much depended on them?
Sources
- MIT Sloan Management Review. Improve Workflows by Managing Bottlenecks. December 10, 2024.Samina Karim, Chi-Hyon Lee, and Manuela N. Hoehn-Weiss. The article distinguishes task bottlenecks (work stalled because it depends on the output of other tasks that have not been completed) from resource bottlenecks (work stalled because the resources required are not available), and argues bottlenecks are best managed by taking a holistic view of work systems rather than addressing them piecemeal.View source
- Harvard Business School. The Psychology of Waiting Lines. 1984.David H. Maister, Harvard Business School Background Note 684-064. Discusses the experience of waiting and the factors that affect tolerance for waits, presenting eight testable propositions on the psychology of queues together with specific managerial advice.View source
Ready to improve your service operations?
We design and operate integrated operating models for organisations ready to compound efficiency. Let's discuss yours.