Bottleneck and delay get used interchangeably by a lot of non-native speakers, and the mix-up costs you precision in exactly the moments where precision matters most.
A delay describes lost time — the result. A bottleneck identifies the point causing reduced flow — the cause.
Two ends of the same problem
"'The launch was delayed a week' reports what happened. 'Legal review is the bottleneck' explains why, and where to fix it."
Reporting a delay tells people something is late. Naming the bottleneck tells them where to intervene so it doesn't keep happening.
"A one-time flight delay isn't a bottleneck. A review step that's late every single week is."
That's the test worth holding onto: is this recurring and structural, or is it a single event? A delay can happen once and never happen again. A bottleneck, by definition, describes a stable limiting point — it'll keep producing the same effect until something about the process actually changes.
"Fixing the bottleneck reduces future delays; simply reporting the delay does not."
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 is really the practical payoff of the distinction. You can report every delay for a year and nothing will improve, because reporting isn't diagnosis. Naming the bottleneck is what gives someone something to actually fix.
Common mistakes
Mistake: using "bottleneck" when you only mean "we were late."
If you can't point to a recurring limiting point — a step, a resource, a review — you're describing a delay, not diagnosing a bottleneck. Reach for "bottleneck" only when you're making a claim about structure, not just about a missed date.
Practice scenarios
Practice choosing between delay and bottleneck in situations like:
- reporting a one-off missed deadline versus a recurring slow step
- explaining why a launch slipped and what's causing it to keep slipping
- deciding whether an update needs a cause (bottleneck) or just a result (delay)
Useful practice phrases:
- "[Event] was delayed [time period]" reports what happened. "[Step] is the bottleneck" explains why, and where to fix it.
- A one-time [event] isn't a bottleneck. A step that's late every single week is.
- Fixing the bottleneck reduces future delays; simply reporting the delay does not.