The Standup Question That Surfaces Blockers People Hide

The standup question that surfaces blockers people hide is "what are you waiting on". It replaces "any blockers", which everybody answers with a no, and it works because waiting is not an admission of anything. Being blocked sounds like being stuck. Waiting sounds like a fact about someone else's inbox. People will say the second one on day two, and they will only say the first one on day nine, when it has become too big to hide.

That gap, day two versus day nine, is the whole value of the change.

Why "any blockers" gets a no

Three things happen when you ask a room whether anyone is blocked.

The word implies the person cannot proceed, and most people can proceed with something, so they honestly answer no while a real problem sits untouched.

It sounds like a request for help, and plenty of people would rather try one more thing than ask in front of the team. That instinct is not weakness. It is how most of us were taught to work.

And it is a yes or no question at the end of a meeting that is already running long. The path of least effort is no.

Why "what are you waiting on" gets an answer

Waiting is about someone else. Saying "I am waiting on the access from the platform team" reports a fact rather than confessing a difficulty. There is no judgement in it, so there is no reason to hold it back.

It is also an open question. A yes or no question can be closed in one syllable. An open one requires the person to actually look at their work and check.

And the answers are immediately useful, because a waiting item names a person or a team. That means the standup can act on it in the room: somebody says they know who to ask, or the person running the meeting takes it away to chase.

What you will hear in the first week

Expect the volume to jump. Teams that ran silent standups for months suddenly produce four or five items a day. That is not a new problem. It is the existing one becoming visible.

Common answers:

• Waiting on access, credentials or a licence
• Waiting on a review that was sent days ago
• Waiting on a decision nobody realised was theirs to make
• Waiting on a file, a data extract or a spec
• Waiting on another team's release
• Waiting on a client to answer a question

Most of these take minutes to resolve once named. They sit for a week because nobody outside the person's own head knew they existed.

Ask each person, by name

Do not ask the room. Asking the room means the confident people answer and the quiet ones do not, and the quiet ones are usually the ones sitting on something.

Go round in a fixed order, name by name, and ask each person the same question. It takes seconds per person and it removes the choice of staying silent without it feeling like pressure. It is also cheap, which matters when a small team only has so many meetings a week to spend.

What to do with the answers

The person running the standup needs a rule for what happens next, or the question becomes theatre.

• If someone in the room can clear it, they say so and it happens after the meeting
• If it needs a chase, one named person owns the chase, not the whole team
• If it has been said twice on separate days, it stops being a chase and becomes an escalation to whoever can actually move it

That last rule matters. An item that appears three mornings running is not a blocker any more, it is a decision nobody is making.

Write them down

Keep a short visible list of open waiting items with a name and a date next to each. This costs a minute a day and changes the meeting, because people can see how long things have been sitting, and it is the only record the standup needs, much like the five line version of meeting notes.

It also gives you something worth carrying into the weekly review, and something worth reading properly at the end of a month. If most of your waiting items point at the same team or the same approval, you have found a process problem rather than a series of unlucky weeks.

Do not turn it into a report

The question works because it is safe. It stops working the moment the answers get used against people, or the moment someone starts counting how many times each person was waiting.

Keep the focus on the item and off the person. The standup is asking what is stuck, not who is slow. Get that wrong for a fortnight and the answers go back to no.