Bottleneck sometimes gets used for anything that eats time and feels annoying — but time-consuming isn't the same as flow-capping, and the word for the first one is overhead, not bottleneck.
Overhead is indirect cost or administrative burden; a bottleneck is a point that actually caps delivery flow.
The test: would removing it speed anything up?
Something can eat time and effort without being the thing capping how fast work actually ships. The test is whether removing it would speed up delivery — if not, it's overhead, not a bottleneck.
"A daily status form takes 10 minutes but doesn't affect shipping speed — that's overhead, not a bottleneck."
Ten minutes a day is real time. It's also not what's capping how fast anything ships — cut the form entirely and the shipping timeline doesn't change.
"The single-reviewer approval step that everything waits on is the bottleneck; the extra Slack updates around it are overhead."
Both cost time. Only one of them, removed, would actually change how fast work moves.
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 →"Cutting overhead is about efficiency; removing a bottleneck is about throughput."
That's the useful reframe: overhead work is worth trimming because it's wasteful, not because it's slowing anything down structurally. A bottleneck is worth fixing because fixing it directly increases how much gets through.
Common mistakes
Mistake: calling every extra administrative task a bottleneck because it's annoying.
Unless it's capping actual delivery speed, it's overhead. Annoying and flow-capping aren't the same axis — plenty of tedious tasks have zero effect on how fast the real work ships.
Practice scenarios
Practice separating overhead from bottleneck in situations like:
- deciding whether a tedious admin task actually affects shipping speed
- distinguishing a genuine capacity limit from something that's merely annoying
- proposing to cut overhead versus proposing to fix a bottleneck
Useful practice phrases:
- "[Task] takes [time] but doesn't affect shipping speed — that's overhead, not a bottleneck."
- "[Step] is the bottleneck; [related admin task] around it is overhead."
- Cutting overhead is about efficiency; removing a bottleneck is about throughput.