The Queue Nobody Admits To
Where deferred work actually goes, why an invisible backlog behaves worse than a visible one, and the three numbers that make a queue manageable.
Work that cannot be done now does not disappear. It goes into a queue, and in most organisations that queue is invisible: it lives in people's inboxes, in half-remembered promises, and in a list the planner keeps privately because publishing it would look like a complaint.
The allocation decision in “The Queue Nobody Admits To” should be made from visible constraints rather than an assumed headcount. Used carefully for tips to increase productivity, a practical approach to tips to increase productivity can contribute recent workload context without replacing the documented priority rule or the manager accountable for the trade-off.
An invisible queue behaves worse than a visible one in every respect that matters, and making it visible costs nothing.
Additional context for “The Queue Nobody Admits To” is available from Gartner HR research. Use external material to prompt a specific validation check rather than replace local judgement.
Where deferred work goes
Back to the claimant, who re-asks later. Into a backlog list nobody grooms. Into the planner's memory. Or quietly into the team, who do it anyway because saying no twice is harder than doing it once.
The fourth is the most common and the most damaging, because it consumes capacity that the account believes is available.
Why invisibility makes it worse
Because nobody can see the total. Twelve deferred claims look like twelve individual disappointments; the same twelve as a list with hours against them look like a structural shortfall, which is what they are.
The total is also the only credible input into a conversation about establishment, and it is the number nobody has.
The three numbers
How many claims are waiting. How many hours they represent. And how long the oldest has been waiting.
Three figures, published with the account. They turn a queue from a source of individual resentment into a managed object.
The age figure, which does the work
A claim waiting four quarters is either not needed or badly failed. Both are findings and both require a decision.
Sorting the queue by age once a quarter and asking about anything over two periods old resolves most of it: a third are no longer wanted, a third are small enough to do, and a third turn out to be genuinely important and misfiled.
Queue discipline
A queue needs entry and exit rules. Entry: a claim that is declined or deferred goes in, with its figure and date. Exit: it is done, it is withdrawn, or it ages out after a stated period with a conversation.
Without exit rules the queue grows forever and becomes the thing nobody looks at, which returns the organisation to invisibility by another route.
Publishing the queue
With the account, as three lines rather than a list. The list belongs in the working document; the summary belongs where the capacity figures are.
Publishing it also protects the planner: a queue that everybody can see is the organisation's problem rather than a reflection on the person maintaining it.
What the queue tells you about the establishment
A queue that is stable in size means capacity and demand are roughly in balance and the shortfall is about sequencing. A queue growing steadily quarter on quarter means they are not, and no amount of prioritisation will fix it.
That distinction is the single most useful thing a capacity account produces for anybody deciding headcount, and it takes four quarters of data to show.
The queue that is really a product decision
Sometimes a growing queue means the organisation is trying to do more kinds of thing than it has the capacity to be good at.
That is a strategy conversation rather than a resourcing one, and the queue is the evidence that starts it. Framed as a resourcing problem it will be answered with headcount; framed as a scope problem it may be answered better.
Telling claimants where they are
Position, expected period, and the fact that it will be reviewed. Not a promise, and not silence.
Silence is what causes claimants to re-ask through other channels, which is how work ends up being done outside the account entirely.
The entry and exit rules, written out
- Entry: anything declined or deferred, with its hours and date.
- Exit: delivered, withdrawn by the claimant, or aged out after two periods with a conversation.
- Review: sorted by age, once a quarter, nothing older than two periods left unexamined.
Three rules. Without the third the queue becomes an archive, and an archive is indistinguishable from the invisible queue it was supposed to replace.
The queue as an argument for headcount
Four quarters of queue figures — count, hours and oldest — make a case that no single quarter can: that the organisation is consistently asking for more than it can do, by a measurable amount.
That is a different argument from "we are busy", and it is the only version that survives contact with a budget process, because it has a denominator and a trend.
The honest summary line
"Queue: 14 claims, 1,180 hours, oldest waiting since March."
One line beneath the difference. It completes the account: what exists, what is promised, what the difference is, and what is waiting because of it.