A stand-up update can be grammatically correct and still leave the team unable to act.
"Yesterday I worked on checkout. There is a problem with testing, and I need help."
The listener still does not know whether work has stopped, whether one stage is merely slow, what new evidence appeared, or who can help. A precise update follows four moves:
Progress → condition → consequence → next action or ask
Quick check
Classify the condition precisely
You know "Blocker" well.
Keep going with the full learning path — more workplace contexts, related expressions, and practice using it yourself with feedback.
Continue with "Blocker" →There's more to "Blocker" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Blocker" in depth →1. State the progress, not just the activity
"I worked on" says where you spent time. It does not say what changed.
Compare:
"Yesterday I worked on the checkout tests."
"Yesterday I completed the checkout load test and added connection-pool metrics."
The second sentence gives the team a new state. Use verbs such as completed, validated, deployed, or ruled out when the evidence supports them.
Try it yourself
Give an actionable stand-up update
2. Name the condition precisely
Use surface when work or evidence brings a previously hidden issue into view.
"The load test surfaced a connection leak."
Surfacing is not fixing. The issue may be newly visible and still unresolved.
Use blocker when a specific obstacle prevents relevant work from continuing.
"The blocker is the missing security approval."
"Security approval is blocking deployment."
Do not call every inconvenience a blocker. If you can continue the relevant task, describe the actual limitation.
Use bottleneck when work still moves but one stage limits the overall rate.
"Code review is the release bottleneck."
A blocker stops progress on relevant work. A bottleneck constrains flow across a process. One team can sometimes be both, but the sentences make different claims.
3. Explain the consequence
After naming the condition, state what it affects.
"The certificate approval is blocking production deployment, but it is not blocking the remaining documentation work."
"Database review is the bottleneck for release testing, so the queue is growing even though individual changes are still moving."
This prevents a local problem from sounding like a complete project stop.
4. Name the action that would unblock progress
To unblock work means to remove the specific obstacle preventing it. General help is not automatically an unblock.
Vague:
"I need help from Priya."
Actionable:
"Priya can unblock testing by confirming the new pool limits."
The useful pattern is:
[Person or team] can unblock [work] by [specific action].
If you do not know the correct owner, make that uncertainty explicit:
"I need help identifying who owns the certificate policy. Once we have that owner, we can ask for approval to unblock deployment."
A complete stand-up update
"Yesterday, the load test surfaced a connection-pool issue. It is not blocking development, but database review is now the bottleneck for release testing. Priya can unblock the test by confirming the new pool limits. Until then, I'll finish the monitoring changes."
This update is concise because every sentence performs a different job. It reports progress, classifies the condition, limits the consequence, and names the next action.
Before your next stand-up, check whether your update answers four questions:
- What changed?
- What exact condition exists?
- What work does it affect?
- What action or decision is needed next?
Precise vocabulary does not make an update longer. It removes the follow-up questions caused by the word problem.
Return to English for Software Engineers for more language for planning, incidents, and technical meetings.
Related guides
Want to actually use "Blocker" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Blocker" learning path →