How Do You Talk About Being "Unblocked" Without Sounding Accusatory?

"Unblock" language can cut both ways in tone, depending on who's asking and why.

Ask "What's blocking you?" or "How can I unblock you?" as a supportive, blame-free way to surface obstacles -- and if you need to ask why something still isn't unblocked, name the dependency and request the needed action directly rather than asking "why haven't you unblocked us?"

The supportive direction

Used by a manager or teammate to ask what's stopping someone, "unblock" vocabulary is a genuinely useful, blame-free coaching move. It asks about the obstacle, not the person's performance -- the question is aimed at the thing in the way, not at the person supposedly failing to move fast enough.

Supportive: "What's blocking you on the migration this week? How can I help unblock it?"

In a 1:1: "Is anything getting in your way right now that I could help clear?" opens the door without implying the person is behind.

Both of these invite someone to name a problem without putting them on the defensive.

The direction that can turn accusatory

The same vocabulary, aimed the other way -- as a complaint about someone else's inaction -- can sound accusatory even when the underlying request is entirely reasonable. "Why haven't you unblocked us yet?" puts the listener in a defensive position immediately, regardless of how legitimate the wait actually is.

Accusatory: "Why haven't you unblocked us yet?" -- Direct, blame-free alternative: "We're still waiting on the schema sign-off from your team -- could you confirm a date this week?"

The fix isn't avoiding the topic or softening it into vagueness. It's phrasing the ask around the dependency and the action needed, not the other person's failure to act.

Why the same word carries such different tone

It's worth understanding why the exact same vocabulary can land so differently depending on direction. "Unblock" always implies that someone or something is responsible for the current stoppage. Asked about your own situation ("what's blocking me"), that implication is neutral -- you're simply naming a fact about your own work. Asked about someone else's inaction ("why haven't you unblocked us"), that same implication lands on a person, and people are more sensitive to being implicitly blamed than to a neutral fact being stated. Recognizing that shift is most of what it takes to catch the accusatory phrasing before it goes out.

Naming the dependency instead of the delay

The pattern that works in both directions is the same: name the specific thing you need, and ask for it directly. That keeps the same directness the original message wanted, without any implication that someone is at fault.

"We're still waiting on the schema sign-off from your team -- could you confirm a date this week?"

This says exactly what the accusatory version was trying to say -- we need this, and we need it soon -- without turning it into a complaint about the other person.

Practice scenarios

Practice using unblock in situations like:

• opening a 1:1 by asking what's blocking a teammate, blame-free
• rewriting an accusatory "why haven't you unblocked us" message into a direct request
• naming a specific dependency instead of implying someone else is behind

Useful practice phrases:

• "What's blocking you on this? How can I help unblock it?"
• "We're still waiting on the schema sign-off -- could you confirm a date this week?"
• "Is anything getting in your way right now that I could help clear?"

"What's blocking you?" is a gift. "Why haven't you unblocked us?" is a complaint wearing the same vocabulary.

Aim the question at the obstacle, not the person, and the directness stays intact without the blame.

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.