A blocker is something that prevents relevant work from moving now, not a stronger-sounding name for every issue, delay, or concern.
Most mistakes come from losing that narrow meaning, while others involve grammar or tone. Here are the main problems and their fixes.
Ready to go beyond the quiz on "Blocker"?
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 "Blocker," too.
Keep going with the full learning path — more workplace contexts, related expressions, and continued practice.
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 →Mistake 1: Calling every issue a blocker
An issue may need attention without stopping progress, but a blocker stops the affected work.
Issue: "The error message is unclear, but users can still finish checkout."
Blocker: "Checkout is down, so users cannot place orders."
Ask one question: What cannot continue because of this? If there is no clear answer, issue may be the better word.
Avoid calling a preference a blocker too. A minor design choice can remain open while other work continues.
Mistake 2: Using the wrong preposition
Three noun patterns are natural, but they emphasize different things.
- a blocker for the affected person, team, or project
- a blocker on the work item
- a blocker to the outcome being prevented
"The expired test certificate is a blocker for the QA team."
"There is a blocker on this task."
"The locked test environment is a blocker to release validation."
Avoid the blocker of the project. That pattern sounds unnatural. You can often make the sentence clearer by naming the cause directly: "The missing credentials are blocking testing."
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 →Mistake 3: Turning a person into the blocker
The facts may involve another person or team. Still, a direct label can sound like blame.
Blunt:
"Procurement is the blocker."
More useful:
"This is waiting on Procurement to finish the vendor setup. Can we raise it today?"
The rewrite keeps the same status information. It focuses on the pending decision and the next action.
Mistake 4: Using severity labels too freely
Terms like hard blocker, release blocker, and P0 blocker signal a serious stoppage. Reserve them for work that truly cannot continue.
"Payroll cannot run without the bank file. This is a hard blocker."
A normal dependency or open question does not automatically deserve that label.
The reverse mistake also matters. Do not describe a release-threatening stop as a small concern. Match the label to the actual impact.
Mistake 5: Reporting a blocker without a path forward
"We have a blocker" is rarely enough. Name the affected work, the cause, the owner, and the next action when you know them.
"Testing is blocked by missing credentials. Omar requested access this morning, and we will escalate at 3 p.m. if it is still pending."
That statement names the stopped work, cause, owner, and next action. A vague label does not.
Mistake 6: Mixing up blocked on and blocked by
Both patterns are natural, but they place attention differently. Blocked on often names the pending item or party: "We are blocked on legal approval." Blocked by points more directly to the cause: "We are blocked by missing credentials." Neither pattern is always better. Choose the one that makes the current dependency easiest to understand. Do not treat them as interchangeable pieces in a memorized phrase. In a useful update, either pattern should still make the stopped work clear. Add the next action when the audience needs it.
Practice scenarios
Try correcting these situations:
- A teammate calls a minor question a hard blocker.
- A status update says, "Legal is the blocker."
- Someone writes, "the blocker of testing."
Practice phrases:
- "This is a blocker for ___ because ___."
- "The work is blocked by ___."
- "This is an issue, but it is not stopping ___."
Use blocker when progress truly stops. Then explain the stop clearly enough for someone to act.
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.