Draft pattern
The Queue Collapses Slowly, Then Suddenly
Backlogs look manageable until a small delay turns into a system-wide stall.
How it starts
A queue absorbs variation. It lets people prioritise, batch work and keep the front door open even when demand is uneven.
How it drifts
The queue becomes the place where unresolved trade-offs are hidden. Every delay is treated as local until the backlog starts changing the behaviour of the whole system.
Why it survives
Queues are politically convenient because they make pressure look orderly. A long list feels more controlled than an open admission that capacity, demand and promises no longer match.
What to watch
Look for queues where triage work grows faster than delivery work. The queue is no longer a buffer; it is consuming the attention needed to clear it.
Questions worth asking
- What work is being created by the queue itself?
- Which promises assume the queue will recover by itself?
- What is the oldest item telling us?
- Who is allowed to reduce demand rather than merely sort it?
Comment carefully
Send examples or corrections by email. Responses are private by default and manually reviewed before anything is quoted. Respond to this draft.