Bottleneck, delay, blocker, backlog, constraint, and dependency all describe conditions that can limit work. Mixing them up can lead a team to the wrong fix.
Choose the label based on operational evidence. A capped rate points to a bottleneck, while longer elapsed time points to a delay. A full stop is a blocker, while work that piles up is a backlog. A broad limit is a constraint, while reliance on another item is a dependency.
Why the label matters
Each word names a different fact about the work, so the wrong label can lead to the wrong response. A team may clear a queue when it needs more capacity, or add a backup when a review step needs more staff.
Try it yourself
Diagnose the constraint at Oriole Games
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 80 waiting tickets are the backlog. The engineer's weekly capacity is a bottleneck only if it limits the flow. For example, that would be true if tickets keep arriving faster than the engineer can clear them.
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. The shipment cannot move until the license is approved. There is no partial flow to speed up. Calling it a "bottleneck" would not make the full stop clear.
Scenario 3: "One investor update waiting on a single teammate's data pull, nothing else affected."
What's the diagnosis? The evidence supports a dependency, not a system bottleneck. Only one item is waiting. The data pull does not cap the rest of the system. That is a fact about work order, not capacity.
Common mistakes
Mistake: picking the label based on how serious the situation feels, rather than what the evidence shows.
Urgency does not decide which word is correct, so use the facts. An urgent issue may still be a simple dependency, while a routine issue may be a structural bottleneck. Check the evidence before you choose the word.
Practice scenarios
Practice choosing the right label in cases like:
- separating a rate limit (bottleneck) from the work that piles up (backlog)
- seeing when a condition stops the affected work (blocker) versus caps its rate (bottleneck)
- checking whether reliance affects one task (dependency) or caps a wider flow (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."
Want to actually use "Bottleneck" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Bottleneck" learning path →Six words point to six types of facts.
Check what actually happened before you reach for any of them.