Queues Reveal Capacity

What is a growing backlog actually telling you?

The idea

A growing queue means arrivals exceed the rate of service, and no amount of urgency changes the arithmetic.

In the real world

A support backlog grows every week while the team works longer hours.

Going deeper

A growing queue is arithmetic, not motivation: arrivals exceed service rate, and the gap is accumulating. Effort has a ceiling well below what closing a persistent gap requires.

Only three things change it — fewer arrivals, faster service per item, or more capacity — and exhortation addresses none of them while reducing the third through burnout. The useful measurement is arrivals per week against completions per week, which turns an argument about how hard people are working into a number that points at one of the three levers.

Where it stops applying

Short-term surges genuinely can be absorbed by extra effort, and treating every backlog as structural misses the ones that are temporary. The distinction is whether the gap persists across several periods.

Why it matters

It tells you that a backlog is a measurement, not a motivation problem.

Try this today

Compare arrivals per week against completions per week for one queue you own.

Test yourself

A support queue grows by 30 tickets a week. The team is told to work harder and the queue keeps growing. Why?

Show the answer

Arrivals exceed service rate, and effort has a ceiling well below the gap. Only three things change it: fewer arrivals, faster service per item, or more capacity. Exhortation addresses none of them, and burnout reduces the third.

Learn this in the feed Answering from memory, then again days later, is what makes it stick.

More in Product & Systems Thinking

Small Experiments Constraints Shape Design Scope Grows Unless Bounded Observability Enables Learning Solve a Real Job Feedback Loops

All Product & Systems Thinking lessons