Yes -- the same "currently preventing progress" idea that applies to a missing document or a broken environment applies just as naturally to a person, team, or decision-maker whose action or inaction is holding up work.
"I'm blocked on Legal" or "waiting on Priya" shows up constantly in standups and status updates. This isn't a rare edge case -- it's one of the word's most common everyday uses.
The risk is entirely in the phrasing
The underlying diagnosis can be completely accurate, and the phrasing can still land badly. Naming a person or team directly as "the blocker," especially in writing or across seniority lines, turns a status diagnosis into a label for them.
Blunt and risky: "You're the blocker on this."
Safer: "This is waiting on your review -- can we find ten minutes today?"
Both sentences convey the exact same underlying fact. The second one just doesn't put a name where a process step should go.
Reframe around the decision, not the person
The fix isn't to soften the observation into vagueness -- it's to move the grammatical subject off the individual and onto the pending decision or dependency they're carrying.
Instead of "Finance is the blocker," try: "This is waiting on Finance's budget approval -- can we get it on their radar today?"
Want to learn "Blocker" 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 →"The review is stuck because we're waiting on Priya's decision, not because anyone dropped the ball."
That last line does something worth noticing explicitly: it names the same true dependency while pre-empting the blame reading altogether, closing off the "anyone dropped the ball" implication before it can even form.
This applies to teams, not just individuals
The same reframe works at team scale. "Finance is the blocker" and "Legal is the blocker" carry the same risk as naming an individual -- they turn an entire department into a label rather than a step in a process. "Waiting on Finance's approval" says the identical thing about what's actually happening, without characterizing the team.
The mistake to avoid
Mistake: "Maria is the blocker" or "Finance is the blocker," which turns a status diagnosis into a label for a person or team. Reframe around the decision or dependency instead of the individual -- you lose no specificity by doing this, and you keep the working relationship intact.
A habit worth building before it's needed
The reframe is easiest to do well when it's already a habit, not something you're improvising under time pressure in the moment you're frustrated. Before a status update goes out, a quick check -- "does this sentence name a person, or does it name a decision?" -- catches most of the risky phrasing before it's sent. Over time, the decision-first framing becomes the default way you describe any stalled work, whether the underlying cause is a person, a team, or a system.
Practice scenarios
Practice using blocker in situations like:
- reporting that a person's pending decision is holding up your work, without naming them as "the blocker"
- reframing a blunt, name-first status update into a decision-first one
- flagging that an entire team's approval process has become the thing you're waiting on
Useful practice phrases:
- "This is waiting on [person/team]'s [approval/decision] -- can we get it prioritized today?"
- "The review is stuck because we're waiting on [person]'s decision, not because anyone dropped the ball."
- "Can we find ten minutes today to get [person]'s sign-off unstuck?"
The diagnosis can be exactly right and the phrasing can still cost you the relationship.
Keep the specificity, move the subject off the person.
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.