Bottleneck and blocker both describe something limiting work, which is exactly why they get used interchangeably. The question that actually separates them is degree: does the work still move, just slower or capped, or has it stopped completely?
A bottleneck restricts speed or capacity without a total stop. A blocker means work cannot proceed at all until it's resolved.
The test is whether anything is still moving
"A missing signed contract is a blocker — nothing can proceed until it exists."
Nothing moves. Not slower, not partially — not at all. That's a blocker.
"Legal review that still moves deals, just more slowly, is a bottleneck — not a blocker."
Deals are still closing. They're just closing more slowly than they would without that review step. That's a bottleneck.
"Once the contract is signed, the blocker is gone; if legal review is still slow after that, that's the bottleneck to address next."
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 →This last example is worth sitting with, because it shows the two aren't rival labels for the same situation — they can show up back to back in the same process. First there's a hard stop (no contract, nothing moves). Once that clears, there can still be a thinner, ongoing limit (a slow review step) that never fully halts things but keeps capping throughput. Calling that second stage a "blocker" would overstate it; calling the first stage a "bottleneck" would understate it.
Common mistakes
Mistake: calling a full stop a bottleneck.
Using "bottleneck" for something that has actually halted progress understates the severity and points people toward the wrong fix. If a team hears "bottleneck," they'll reach for more resources, a faster process, or an extra reviewer. If the real problem is a blocker, none of that helps — nothing will move until the blocker itself is cleared, regardless of how much capacity gets added around it.
Getting this right isn't pedantry. A bottleneck calls for increasing throughput or capacity at the limiting point. A blocker calls for removing whatever's preventing any progress at all. Naming the wrong one sends a team optimizing a step that was never the actual problem.
Practice scenarios
Practice choosing between bottleneck and blocker in situations like:
- reporting that work has completely stopped versus just slowed down
- explaining why adding capacity won't fix a missing precondition
- describing a review step that's still moving work, just more slowly
Useful practice phrases:
- "[X] is a blocker — nothing can proceed until it exists."
- "[Step] that still moves [work], just more slowly, is a bottleneck — not a blocker."
- "Once [the blocker] is cleared, if [step] is still slow, that's the bottleneck to address next."