5 exercises on flagging blockers in standup — being blocked, waiting on others, asking for help and escalating risk.
Key patterns
I’m blocked on… — the work is stuck (not I’m blocking).
I’m waiting on… — name the dependency or person.
could someone grab a review… — polite, impact-based ask.
on the critical path / at risk — escalation language.
0 / 5 completed
1 / 5
You cannot continue the feature until the design team delivers the final mockups. Which is the MOST natural way to flag this in standup?
“I’m blocked on X” + “I’m waiting on Y” is the standard blocker frame.
I’m blocked on the checkout feature — you (the work) are stuck.
I’m waiting on the final mockups from design — wait on (or wait for) names the dependency.
Why the others fail: option B blames design (“not mine”) — unprofessional; option C (“blocked since design”) is vague and grammatically off; option D reverses the meaning — “I’m blocking” means you are the obstacle. Note the key contrast: blocked on = stuck by something; blocking = causing the obstruction.
2 / 5
You need a code review before you can merge and move on. Which phrasing asks for help MOST naturally?
Ask for help politely but clearly. A good request names the item, the action needed, and a soft timeframe:
could someone grab a review — grab a review / take a look are friendly idioms.
when they have a moment — polite without removing urgency.
so I can merge and move on — explains the impact.
Why the others fail: “must review now” and “immediately” sound demanding; “Why no review?” sounds passive-aggressive. In standups, framing requests around impact (so I can…) gets faster help than commands.
3 / 5
A blocker is on the critical path and will slip the release if not resolved today. Which standup line communicates this BEST?
Escalate by naming impact precisely. Decision-makers act on clear stakes:
Heads-up — signals something important is coming.
it’s on the critical path — this work gates the timeline.
our Friday release is at risk — concrete, dated consequence.
Why the others fail: “kind of urgent maybe” and “probably fine” bury the risk; “ruining everything” is emotional and vague. The phrases at risk, critical path, and a specific date are what trigger management attention.
4 / 5
You depend on the platform team finishing a migration first. Which is the MOST natural way to flag a cross-team dependency?
Flag dependencies factually and own the follow-up.
There’s a dependency — labels it clearly.
I’m waiting on the platform team to finish… — names the team and the item.
I’ll ping them after standup — you take the next action (ping = send a quick message).
Why the others fail: “slow again” and “should hurry up” are blame; option B has a preposition error — it’s depend on, never depend of. Good blocker etiquette pairs the flag with an action you’ll take yourself.
5 / 5
You were blocked yesterday but it’s now resolved. Which is the MOST natural standup update?
Close the loop on resolved blockers. Teammates who heard the blocker need to know it’s cleared:
is sorted / is resolved / I’m unblocked — idiomatic ways to say it’s fixed.
ops bumped the rate limit — briefly says how (bumped = increased).
back on the integration — you’ve resumed the real work.
Why the others fail: “is no more” is unnatural here; “I was blocking but now not” misuses blocking (you were blocked) and is clipped; the last option adds a needlessly final tone. Always say what you’re moving on to next.