How Do You Answer "Any Blockers?" in a Standup?

"Any blockers?" is one of the most common status-check questions in modern project, product, and software-adjacent workplaces -- and answering it well is a small skill with an outsized payoff.

The answer is precise, not elaborate: either name the one specific thing currently stopping your work, or say "no blockers" when nothing actually is. Both are correct, complete answers to this fixed daily-standup question.

"No blockers" is not an evasive answer

A learner sometimes hesitates to say "no blockers," worried it sounds like they aren't being forthcoming enough, or that they should have something to report. That instinct is backwards. "No blockers" is itself a correct, complete answer whenever nothing is genuinely stopping the work.

"Any blockers? -- No blockers, the API integration is on track."

There's nothing more to add here. Padding a clean "no blockers" with unnecessary hedging or unrelated commentary doesn't make the answer more thorough -- it just makes the standup longer.

When a real blocker exists, name the specific condition

The other half of the skill is just as important: when something genuinely is stopping your work, name it specifically, and name the affected work too when it isn't obvious.

"One blocker: I'm waiting on legal's sign-off before I can send the contract."

"No blockers on my side, but I'm keeping an eye on how long the vendor takes to respond."

That second example shows a useful middle case -- not a current blocker, but a named risk worth flagging without inflating it into one.

The mistake to avoid: vague non-answers

The failure mode isn't usually saying the wrong word -- it's saying nothing specific at all.

Mistake: giving a vague non-answer like "things are a bit stuck" instead of naming the actual thing, or reflexively saying "no blockers" to avoid raising something that really is stopping the work. Both versions leave the team with nothing to act on -- the first because it's too vague to respond to, the second because it hides a real problem behind a clean-sounding answer.

The instinct to always have something to report

There's a common instinct, especially early in a career or on a new team, to feel like "no blockers" isn't a substantial enough answer -- like it doesn't show enough engagement with the work. Resist that instinct. A standup is a status check, not a performance, and a clean "no blockers" that's actually true is exactly what the question is asking for. Manufacturing a minor concern just to have something to say does the opposite of what a standup exists to do: it adds noise instead of signal, and it can even train the team to take your future blocker reports less seriously.

Why this exchange is worth mastering specifically

Because "any blockers?" repeats every single day in many teams, getting comfortable with a precise, low-effort answer pays off far more than most single vocabulary items do. It's not really a vocabulary question at all -- it's a fluency habit: naming the specific thing, or confidently saying there isn't one, without over-explaining either way.

Practice scenarios

Practice using blocker in situations like:

• answering "any blockers?" with a specific, complete answer
• saying "no blockers" confidently instead of padding it with unnecessary hedging
• naming a real blocker specifically instead of a vague "things are a bit stuck"

Useful practice phrases:

• "No blockers, [task] is on track."
• "One blocker: I'm waiting on [person/team]'s [specific thing] before I can [next step]."
• "No blockers on my side, but I'm keeping an eye on [specific risk]."

The standup question repeats every day, so the answer is worth making automatic.

Name the specific thing, or confidently say there isn't one -- nothing in between.

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.