Bottleneck has a specific, extremely common workplace use around approvals — and it's worth knowing exactly what it's pointing at.
An approval bottleneck is the sign-off, legal review, procurement step, or centralized decision point that caps how quickly all the work waiting behind it can move forward.
The process can be fine and still be capped
This is one of the most common workplace uses of the word, because the underlying process itself is often perfectly reasonable — the cap is just how fast one review or decision point clears.
"Legal review is the bottleneck in our contract approval process — everything else moves faster than that step."
"Procurement sign-off is bottlenecking every vendor onboarding this quarter."
"Customer sign-off is the bottleneck before implementation can start."
In each case, nothing else in the process is necessarily broken. Sales might be fast. Drafting might be fast. Implementation readiness might be fine. The whole thing is still capped by the one gate everyone has to pass through.
Name the step, not the people running it
The instinct when an approval bottleneck is costing time is to point at the team sitting behind it. That's usually the wrong target.
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 →Common mistakes
Mistake: blaming the approver's team when the real issue is volume.
If too many requests are routed through one review point, that's a routing and capacity problem — not evidence that the reviewers are slow or careless. "Legal review is the bottleneck" describes the structure. "Legal is dropping the ball" describes a person, and it's usually not what's actually happening.
Naming the step precisely — which stage, what it's capping, and roughly by how much — gives leadership something to act on: add a reviewer, parallelize the step, or raise its priority. Naming a team as the problem gives them nothing but a reason to get defensive.
Practice scenarios
Practice naming an approval bottleneck in situations like:
- reporting that one review step, not the whole approval process, is what's capping speed
- distinguishing a routing/volume problem from a team performance problem
- describing a sign-off gate precisely enough that leadership knows what to fix
Useful practice phrases:
- "[Review step] is the bottleneck in our approval process — everything else moves faster than that step."
- "[Sign-off] is bottlenecking every [thing] this quarter."
- "[Step] is the bottleneck before [next stage] can start."