Bottleneck is only half as useful as it could be if you stop at naming it. The real skill is describing one clearly enough that whoever reads the update knows what to decide.
The structure that works: combine three things in one line — the specific constraint, its business impact, and a next action.
"Bottleneck: [constraint] is causing [impact]; next action: [step]."
Why this structure works
This lets leadership evaluate the cost of the constraint and the proposed response without reading a long process narrative.
"Bottleneck: legal review is causing a 2-week delay on every enterprise deal; next action: requesting a dedicated reviewer for Q3 deals."
"Bottleneck: onboarding capacity is causing 30% of new signups to churn before activation; next action: hiring two onboarding specialists."
Notice what's missing from both: a story. No account of every meeting, every handoff, every reason things got here. Just the constraint, what it's costing, and what you're proposing.
A companion pattern is useful when a bottleneck has newly emerged, rather than being a known ongoing issue:
"The single-reviewer approval step has become the bottleneck because pull requests are now waiting 4 days on average, up from same-day."
This version leads with evidence — the shift from same-day to four days — rather than just asserting that something has become inconvenient.
Common mistakes
Mistake: reporting only that something is slow.
Without the impact and the next action, the update describes a problem without giving leadership anything to decide. "Legal review is slow" is a complaint. "Legal review is causing a 2-week delay; here's what I'm proposing" is a decision leadership can actually make.
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 →Escalating a stalled approval without blaming the approver
The same structure gets harder to apply cleanly when the message is going directly to the person who owns the limiting step. Escalating a decision bottleneck is especially sensitive for exactly that reason.
"Risky: 'Procurement is holding everything up again.'"
That's an accusation, and it tends to make the decision-owner defensive — which slows things down further, not faster.
"Safer: 'Procurement approval is the bottleneck on three deals this week — is there anything I can do to help move it, or should we flag it to your lead?'"
"Also safer: 'I know contracts review is buried right now — is there anything I can do to help move the Meridian deal, or should I flag it to your director?'"
Both safer versions still get the priority handled. They just keep the subject on the step's capacity, not the person's slowness — the same reframe that matters when a person is the resource behind a bottleneck.
Explaining a bottleneck to a client without sounding like an excuse
External updates raise a different problem: the same honesty can read as blaming the client, a vendor, or your own team if you're not careful. The structure that works here is cause, impact, and mitigation.
"'Customs clearance is currently the bottleneck for your shipment — it's adding roughly 5 business days, and we've requested expedited processing to reduce that.'"
"'The delay is coming from a single compliance review step — it's adding about 3 business days, and we've assigned a second reviewer to clear it faster.'"
Sometimes a softer register serves the same purpose better than the word "bottleneck" itself:
"Client-safe: 'a supply constraint is affecting delivery timing' can preserve the same logic as 'bottleneck' with a softer register when that reads better for the audience."
Mistake: hiding behind a vague excuse, or quietly blaming the client's own team. Stage plus impact plus mitigation does neither — it just tells the client what's happening and what you're doing about it.
Practice scenarios
Practice describing a bottleneck clearly in situations like:
- writing a one-line constraint-impact-action update for leadership
- escalating a stalled approval to its owner without sounding accusatory
- explaining a client-facing delay with cause, impact, and mitigation
Useful practice phrases:
- "Bottleneck: [constraint] is causing [impact]; next action: [step]."
- "[Step] has become the bottleneck because [evidence]."
- "[Stage] is currently the bottleneck for [outcome] — it's adding [impact], and we've [mitigation]."