Bottleneck usually points to a process. At times, one person's capacity may limit that process. In that case, careless use of the word can sound like blame.
A person's available time may set the pace for a whole system. Their workload, queue, approval authority, or current skill coverage may be the limit.
But calling them "the bottleneck" can hide the cause and sound like personal blame.
Quick check: blame Priya or name the review design?
Choose the sentence that reports the measured dependency while separating it from personal performance.
Ready to go beyond the quiz on "Bottleneck"?
Take the full learning path: hear it in real workplace contexts, watch short explanations, learn its nuances and when to use it, then practice using it yourself.
Start learning for free →Now see if you can use it naturally yourself.
Try it yourself
You know how to use "Bottleneck," too.
Keep going with the full learning path — more workplace contexts, related expressions, and continued practice.
Continue with "Bottleneck" →There's more to "Bottleneck" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Bottleneck" in depth →The diagnosis can be right and the phrasing can still land badly
A resource is a bottleneck when its capacity limits the flow of work. A reviewer's time can be such a resource. So can the time of a designer or sole approver. The basic finding may be sound, but it still needs evidence and context.
"Priya is the bottleneck on every design request."
The sentence may describe the flow of work. Yet it can sound like blame because it names Priya, not the process. It also leaves key causes out. Priya may lack backup, clear authority, or enough review time.
Reframe around the process, not the person
"The review step depends heavily on Priya, and that's capping how many requests move forward."
This keeps the same finding and level of detail. But it points to the review step and its reliance on Priya. It does not treat Priya as the cause.
"One designer's queue is the limiting capacity for every asset request right now."
This version still says that one person's available time limits the flow. Yet the subject is the queue, not the person. The team can then discuss backup review, fewer requests, or broader approval authority. The person or group with authority over the workflow should decide any change.
Want to actually use "Bottleneck" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Bottleneck" learning path →Common mistakes
Mistake: naming the person instead of the process.
The finding about capacity may be correct. Do not make it vague. State the facts about the step, queue, or reliance on one person. Also name who can approve a change and what outcome the team expects. This keeps the issue clear without making one person at fault.
Practice scenarios
Practice reframing a person-capacity bottleneck in situations like:
- flagging that one reviewer's availability is capping a whole workflow
- rewriting a risky, name-first sentence into a process-first one
- explaining a capacity limit to leadership without singling anyone out
Useful practice phrases:
- "The review step depends heavily on [name], and that's capping how many requests move forward."
- "[Name]'s queue is the limiting capacity for every request right now."
- Keep the specificity of the diagnosis; move the subject of the sentence off the individual.
Reframe Omar’s release role
A capacity limit still matters, whoever carries it.
Say where it sits in the process, then agree on the next step.
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.