Bottleneck gets reached for sometimes when the real situation is much smaller: one task waiting on another. That's a dependency, and calling it a bottleneck overstates what's actually happening.
A dependency is one task simply relying on another; a bottleneck is a stage that limits overall downstream flow, not just one waiting task.
Reliance alone isn't a bottleneck
"One landing page waiting on a design asset, with no other work affected, is a dependency — not a bottleneck."
Only one thing is stalled. Nothing else in the system is capped by it. That's a sequencing fact, not a capacity diagnosis.
"If every landing page in the launch is waiting on the same single designer, that designer's queue is now a bottleneck."
Same underlying relationship — work waiting on a designer — but now scaled up to affect the whole launch. The designer's capacity, not any one task, is what's capping the system.
"Sequencing (this must happen before that) is a dependency question; throughput (how much can move per week) is a bottleneck question."
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 →That's the cleanest way to hold the distinction: dependency is about order, bottleneck is about volume.
Common mistakes
Mistake: escalating a single waiting task as a bottleneck.
Unless the dependency is capping wider flow, it's a sequencing issue, not a capacity diagnosis. Calling one waiting task a "bottleneck" makes a small, normal scheduling fact sound like a systemic capacity crisis — and dilutes the word for the moments when you actually need it.
Practice scenarios
Practice separating dependency from bottleneck in situations like:
- deciding whether one waiting task is a sequencing issue or a capacity issue
- recognizing when a single dependency has scaled into a system-wide bottleneck
- avoiding overstating a normal sequencing fact as a capacity crisis
Useful practice phrases:
- "[Task] waiting on [thing], with no other work affected, is a dependency — not a bottleneck."
- "If every [task] is waiting on the same [resource], that [resource]'s queue is now a bottleneck."
- Sequencing is a dependency question; throughput is a bottleneck question.