How to Report a Blocker in a Standup in English

Reporting a blocker well in a standup is a small but high-frequency skill — you do it often, in front of the whole team, usually with thirty seconds to make yourself clear. Vague blockers (“I’m kind of stuck on something”) waste everyone’s time; specific ones get you help fast and make you look competent, not behind.

Key Vocabulary

Naming the blocker specifically — stating exactly what is stopping your progress, rather than a general statement that something isn’t working, so listeners can immediately tell if they can help. “I named the blocker specifically: the staging database is returning a permissions error when I try to run migrations, and I don’t have access to fix the IAM policy myself.”

Stating what you’ve already tried — briefly mentioning the steps you’ve taken to solve it yourself, so the team knows you’re not asking them to do your first-pass debugging for you. “I stated what I’d already tried: I checked the IAM console myself and confirmed my role doesn’t have the migrate permission, so I don’t think this is something I can self-serve.”

Naming who or what you need — being explicit about who can unblock you, or what decision needs to be made, rather than leaving it to the team to figure out. “I named exactly who I needed: I asked if anyone on the platform team could grant temporary migrate access, or point me to who can.”

Estimating the impact — briefly noting what the blocker affects, such as a deadline or dependent task, so the team can judge urgency. “I estimated the impact: if this isn’t resolved by tomorrow, the API work that depends on it will also slip.”

Common Phrases

• “I’m blocked on [specific thing] — I need [specific person/access/decision] to move forward.”
• “I’ve already tried [X] and [Y], but I still can’t get past this.”
• “This is blocking [related task], so I’d like to resolve it today if possible.”
• “Could someone from [team] help me with this after standup?”
• “I’ll follow up with [name] directly after this — just flagging it here in case anyone has context.”

Example Sentences

A clear, specific blocker report: “I’m blocked on the payments integration — the sandbox API key we were given returns a 401 on every request. I’ve double-checked the key and confirmed it matches what’s in the docs, so I think it’s an account-side issue. Can someone connect me with our contact at the payment provider?”

A blocker with impact stated: “Quick blocker: the design specs for the settings page haven’t been finalized yet, which is holding up the frontend work. Not urgent today, but if it’s not resolved by Thursday, it’ll push the sprint deadline.”

Following up on a blocker from the previous day: “Following up on yesterday’s blocker — it’s resolved now, thanks to [name] for the quick help. I’m unblocked and back on track.”

Asking for a decision rather than a technical fix: “I’m blocked, but not technically — I need someone to decide whether we support the old API version or not, because the implementation is different depending on the answer.”

Professional Tips

• Name the blocker specifically — “I’m stuck” tells the team nothing; “the staging DB rejects my migration with a permissions error” tells them everything.
• Briefly state what you’ve already tried, so the team knows you’re asking for help, not for someone to redo your first debugging pass.
• Always name who or what you need, even if it’s just “anyone with context” — a blocker with no clear next step often stays unresolved for days.
• If the blocker has a deadline impact, say so — it helps the team prioritize whether to jump in immediately or after standup.
• Follow up publicly once a blocker is resolved — it closes the loop and credits whoever helped.

Practice Exercise

1. Write a 20-second blocker report for a hypothetical failing test you can’t diagnose, including what you’ve already tried.
2. Draft a sentence stating the impact of a blocker on a deadline.
3. Write a one-sentence follow-up thanking a colleague after a blocker is resolved.