Bottleneck usually points at a process. Sometimes, though, the thing actually capping the process is a person's capacity — and that's where the word gets dangerous to use carelessly.
Yes, a person can be the resource whose limited capacity sets the rate for the whole system. Their workload, their queue, their skill level can absolutely be that constraint.
But naming them directly as "the bottleneck" is one of the riskiest ways to say it.
The diagnosis can be right and the phrasing can still land badly
A resource is a bottleneck when its capacity caps how much moves forward. A person's time or throughput is a resource like any other — a reviewer, a designer, a single approver. So the underlying observation isn't wrong.
"Priya is the bottleneck on every design request."
That sentence might be factually accurate. It's also almost guaranteed to read as blame, because it puts a name where a process should be.
Reframe around the process, not the person
"The review step depends heavily on Priya, and that's capping how many requests move forward."
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 →Same diagnosis. Same specificity. The difference is where the sentence points: at the review step and the dependency, not at Priya.
"One designer's queue is the limiting capacity for every asset request right now."
This version doesn't hide the fact that a single person's bandwidth is the constraint — it just keeps the subject of the sentence on the workload, not the individual.
Common mistakes
Mistake: naming the person instead of the process.
The capacity observation may be completely correct. The fix isn't to soften the diagnosis into vagueness — it's to keep all the specificity while moving the grammatical subject off the individual and onto the step, the queue, or the dependency they're carrying. You lose nothing useful by doing this, and you keep the working relationship intact.
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.