Bottleneck, delay, blocker, backlog, constraint, and dependency all describe something limiting work — and mixing them up sends a team toward the wrong fix.
The right label follows the operational evidence: a capped rate points to bottleneck, elapsed time points to delay, a full stop points to blocker, accumulated work points to backlog, a broad limit points to constraint, and simple reliance points to dependency.
Why the label matters
Each of these near-words describes a genuinely different piece of operational evidence. Mixing them up sends a team toward the wrong fix — clearing a queue when they should be adding capacity, or building redundancy when they should be resourcing a review step.
Test yourself: three scenarios
Scenario 1: "80 support tickets waiting for triage, one on-call engineer clearing 60 a week."
What's the diagnosis? The engineer's triage capacity is the bottleneck; the 80 waiting tickets are the backlog. Two labels, two different facts about the same situation — the cause and the pile-up it's creating.
Scenario 2: "An unapproved export license, with the shipment unable to leave the warehouse until it's granted."
What's the diagnosis? Blocker, not bottleneck. Nothing moves at all until the license clears — there's no partial flow to speed up, so "bottleneck" would understate what's actually happening.
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 →Scenario 3: "One investor update waiting on a single teammate's data pull, nothing else affected."
What's the diagnosis? Dependency, not bottleneck. Only one thing is waiting, and nothing else in the system is capped by it — that's a sequencing fact, not a capacity diagnosis.
Common mistakes
Mistake: picking the label based on how serious the situation feels rather than what the evidence actually shows.
Perceived severity and the correct diagnostic label aren't the same thing — the evidence decides. A situation can feel urgent and still be a simple dependency, or feel routine and actually be a structural bottleneck. Check the evidence, not the emotional temperature, before you choose the word.
Practice scenarios
Practice diagnosing the right label in situations like:
- separating a capacity cause (bottleneck) from the pile-up it creates (backlog)
- recognizing when nothing is moving at all (blocker) versus just moving slowly (bottleneck)
- checking whether only one task is affected (dependency) before calling something a bottleneck
Useful practice phrases:
- "[Resource]'s capacity is the bottleneck; the [number] waiting is the backlog."
- "[X] is a blocker, not a bottleneck — nothing can move until it clears."
- "[Task] waiting on [thing], with nothing else affected, is a dependency, not a bottleneck."