Skip to content
All articles

What to say at standup when you were blocked

· 6 min read

There's a particular feeling when it's your turn at standup and the honest answer is that nothing moved. Knowing what to say when you were blocked for a morning is easy. Saying it on the third day, with the same ticket still in the same column, is where most people start to mumble, pad the update or bury the blocker under detail.

Being blocked is normal, and standup is the meeting built for it. The trouble is usually not the blocker itself but how it's said. This guide gives you a shape for the update, examples for the common kinds of blocker, and what to do so that tomorrow's update is easier than today's.

Why it feels hard to say

Most of the discomfort comes from one worry: that being blocked sounds like an excuse. It feels as if you're admitting you couldn't do the work, especially if you've been stuck for a while or the blocker turned out to be something you could have spotted sooner.

Your team sees it differently. A blocker raised early is information they can act on: someone can chase the other team, pair with you, or move the work around. A blocker raised late, or hidden inside a vague update, is a surprise at the end of the sprint. The update that feels most exposing is often the most useful thing you'll say all week.

The shape of a blocked update

A good blocked update has four parts, in this order. Each one is a sentence, sometimes less.

  1. What's blocked. The ticket or piece of work, by the name the team uses.
  2. What it's waiting on. A person, a team, a decision, access, or an answer you don't have yet.
  3. What you need, and from whom. One specific ask, with a name and ideally a time.
  4. What you're doing meanwhile. So the team knows your time isn't lost.
Four parts, about fifteen seconds

"The export ticket is blocked. I need read access to the reporting database, and the request has been with the platform team since Tuesday. Maya, could you help me find the right person after this? Meanwhile I'm writing the tests against a local copy."

Notice what's missing: the history of every message you sent, how frustrating it was, and an apology. All of that can go in the ticket. In standup, the team needs the state and the ask.

What to say when you were blocked for days

A long blocker needs one extra thing: a short account of what you've already tried. Without it, the team's first instinct will be to suggest the things you did on day one, and you'll spend the meeting saying "yes, I tried that".

Defensive and vague

"Still on the flaky test thing, sorry. It's been, um, really hard to pin down, I've been trying a lot of stuff, I think I'm getting closer, so hopefully today. No blockers really, I just need to keep going."

Honest and specific

"I'm three days into the flaky checkout test and I'm stuck. I've ruled out test order and the clock mock. It only fails on CI, so I think it's the shared database. I'd like an hour pairing with someone who knows the CI set-up. Arun, are you free after lunch? If we can't find it today, I'd suggest we quarantine the test and I move on to the payment bug."

The second version admits the delay without apologising for it, shows the work that has been done, asks for something specific, and offers a way forward if the ask doesn't work. That last part is what turns a blocked update into a decision the team can make.

Different kinds of blocked

Waiting on another team

Name the team, say when you asked and through which channel, and ask whether anyone has a better contact. "I asked the identity team in their channel on Monday and haven't heard back. Does anyone know who's on call for them this week?"

Waiting on a review

This one feels awkward because the person who can unblock you is probably in the call. Say it anyway, kindly and directly. "My pull request for the rate limiter has been open since yesterday. Could someone take it today? It's about two hundred lines, mostly tests." Saying the size helps someone decide to pick it up.

Unclear requirements

Turn the uncertainty into a question with options. "I'm not sure whether cancelled orders should appear in the export. I can do either. Priya, can you decide by tomorrow? Until then I'll leave them out." A question with a default is far easier to answer than an open one.

Stuck on your own understanding

Sometimes the blocker is that you don't understand a piece of the system yet. That's a real blocker and worth saying. "I don't understand how the sync job decides what's changed, and I've spent most of yesterday reading it. Is there someone who's worked on it who could give me twenty minutes?"

Ask for one thing, then take it offline

Standup is the place to raise a blocker, not to solve it. If the conversation starts turning into debugging, stop it yourself: "Let's pick this up straight after. Arun, Maya, can you stay on for five minutes?" People appreciate the person who protects everyone else's time.

Keep the ask to one thing. If you need access, a review and a decision, say the most urgent one in standup and put the others in writing. Three asks in one update tend to blur into none.

Make tomorrow's update easier

  • Write the blocker in the ticket. What you're waiting on, since when, and what you've tried. Then standup can be one sentence and a link.
  • Note what changed. Tomorrow, lead with the difference: "Access came through yesterday afternoon, so the export is moving again."
  • Report back on the ask. If someone agreed to help, say what came of it. It closes the loop and makes the next ask easier.
  • Say when you'll escalate. "If I haven't heard by Thursday, I'll raise it with the platform lead." A date takes the drama out of chasing.

The hardest sentence is usually the first one, "I'm stuck", so it's worth saying it out loud once before the meeting. Hearing yourself say it plainly in private makes it much easier to say plainly in public.

That's part of what Staging Mind is for. Before standup it lists the work since your last meeting, straight from git, and lets you practise the update out loud, including the question nobody wants: "What got in the way?"

Frequently asked questions

Should I say I'm blocked if I think I can sort it out myself today?
Mention it briefly. "Slightly blocked on access, I expect to have it by lunch" costs five seconds, and if it doesn't sort itself out, nobody is surprised tomorrow.
How do I raise a blocker caused by a teammate who's in the standup?
Describe the work, not the person, and ask for help with timing. "The review on the rate limiter is still open, could we find time for it today?" is direct without putting anyone on the spot.
What if I've been blocked so long it looks bad?
Say it now. Own the delay in one sentence, show what you tried, ask for one specific thing and offer a way forward. The longer it stays unsaid, the harder it gets.

// Staging Mind

If the blocked update is the one you dread, Staging Mind lets you practise it with the work since your last meeting in front of you, and keeps a short note of the actions so tomorrow starts from them.

Start free: one session on us

More from the blog