Calling every delivery problem a "blocker" makes a status update sound urgent but less informative.
Some work is stopped. Some work still moves, but too slowly because many items pass through one constrained point. A precise dependency update distinguishes the two:
"The missing data agreement is blocking the pilot. Legal review is also the broader bottleneck because every vendor request waits there. Procurement can unblock the pilot by confirming the approved terms today. Review throughput has fallen from twelve requests a week to seven."
That update names the stopped work, the system constraint, the requested action, and the effect on completed flow.
Quick check
Blocker or bottleneck?
You know "Blocker" well.
Keep going with the full learning path — more workplace contexts, related expressions, and practice using it yourself with feedback.
Continue with "Blocker" →There's more to "Blocker" 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 "Blocker" in depth →Call it a blocker only when required progress stops
A blocker is a specific issue that stops required progress on a task or outcome.
"The missing security approval is blocking the production launch."
A hard task is not automatically a blocker. If the team can still make the needed progress, describe the difficulty rather than overstating it.
Useful pattern:
"[Issue] is blocking [specific work] because [dependency]."
Try it yourself
Make a dependency update actionable
Use bottleneck for the point that limits flow
A bottleneck is the step that limits how quickly the larger flow can move.
"Legal review is the bottleneck; all vendor changes queue there."
Work may still complete through a bottleneck. The problem is the rate. A blocker can affect one critical item, while a bottleneck can constrain many items at once.
Useful pattern:
"[Step] is the bottleneck because [items] wait there before [next stage]."
Ask who can unblock the work
To unblock work is to remove the obstacle so progress can continue.
"Procurement can unblock the pilot by confirming the approved terms."
"Can you help?" asks for support. "Can you unblock this by approving the exception?" names the obstacle and action. Use the stronger verb only when the requested action actually removes the stop.
Use throughput for completed work over time
Throughput is the amount of work a process completes during a period.
"Review throughput fell from twelve requests per week to seven."
It is not a measure of how busy people are. A team can be extremely busy and still have low throughput if work waits, loops, or remains unfinished.
Useful pattern:
"Throughput changed from [amount] to [amount] per [period] after [condition]."
A reusable dependency update
"[Issue] is blocking [work]. The broader bottleneck is [step], where [items] wait. [Owner] can unblock [work] by [action]. As a result, throughput is [measure or direction]."
Example:
"The unsigned data agreement is blocking the pilot. The broader bottleneck is legal review, where all vendor requests wait. Procurement can unblock this pilot by confirming the standard terms today. Until review capacity changes, weekly throughput will remain below target."
The structure helps the listener decide whether to solve one stop, improve one constrained stage, or both.
Practice aloud
- "___ is blocking ___ because ___."
- "The bottleneck is ___, where ___."
- "___ can unblock the work by ___."
- "Throughput has changed from ___ to ___."
Return to English for Project Managers for more language on delivery, risk, and stakeholder decisions.
Want to actually use "Blocker" 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 "Blocker" learning path →