Bottleneck and backlog show up together constantly, because one usually causes the other — but they're not the same thing, and mixing them up points a team at the wrong fix.
A backlog is the pile-up of unfinished work; a bottleneck is the stage or capacity limit actually causing that pile-up.
A queue in front of a narrow gate
Picture a queue building up in front of a narrow gate: the queue is the backlog, and the narrow gate creating it is the bottleneck.
"150 pull requests waiting is the backlog. The single authorized reviewer is the bottleneck causing it."
The 150 requests are the visible symptom. The single reviewer's capacity is the cause. Fix the cause, and the symptom stops accumulating. Manage only the symptom, and it comes right back.
"Clearing the backlog with a one-time push doesn't fix anything if the same single-reviewer bottleneck is still there next week."
This is the trap teams fall into constantly: a heroic effort clears the queue, everyone feels relief, and then the pile-up starts rebuilding immediately — because the actual limiting stage never changed.
Want to learn "Bottleneck" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →"The bottleneck is the stage; the backlog is what accumulates in front of it."
Common mistakes
Mistake: treating the backlog itself as the root cause.
The pile-up is a symptom — the bottleneck is the capacity-limited stage generating it, and that's what actually needs redesigning or expanding. A plan that only talks about "clearing the backlog" hasn't yet answered the more important question: why does it keep forming in the first place?
Practice scenarios
Practice separating backlog from bottleneck in situations like:
- explaining why a one-time cleanup won't stop a queue from rebuilding
- reporting the pile-up (backlog) and its cause (bottleneck) as two separate facts
- proposing a fix aimed at the capacity limit, not just the visible queue
Useful practice phrases:
- "[Number] waiting is the backlog. [Stage/resource] is the bottleneck causing it."
- Clearing the backlog with a one-time push doesn't fix anything if the same bottleneck is still there next week.
- The bottleneck is the stage; the backlog is what accumulates in front of it.