The three stand-up questions (and smarter alternatives)

The three daily stand-up questions are: what did I do yesterday, what will I do today, and is anything blocking me. Almost every team starts here, and for a new team it’s a reasonable floor — a shared structure so nobody freezes when it’s their turn.

But the three questions have a well-known failure mode, and it’s worth understanding before you adopt them uncritically. Answered literally, they turn the meeting into a status report: each person recites a task diary to the room, nobody responds, and the meeting produces coordination in name only. Teams feel this as the stand-up that’s “just list out all your accomplishments of yesterday.” That’s not a facilitation slip. It’s what the three questions do by default.

What each question is really asking

The questions are fine. The trick is answering the intent behind them, not the literal words.

“What did I do yesterday?” is not “prove you were busy.” It’s “did anything I finish change what someone else should pick up today.” If your progress unblocks a teammate or completes a hand-off, say it. If it’s just tasks you closed that touch nobody else, it belongs in the ticket, not the meeting.

“What will I do today?” is not “read your to-do list.” It’s “where are you heading, so the team can spot a collision or a dependency before it happens.” Two people about to touch the same module should discover that here, not in a merge conflict this afternoon.

“Is anything blocking me?” is the whole reason the meeting exists, and it’s the one people skip. Blockers get under-reported because naming one can feel like admitting you’re stuck. Lead with it anyway, and be specific: not “I’m a bit blocked on the API,” but “I need the staging credentials from Priya before I can test — can we sort that straight after this.”

Why “blockers first” beats “yesterday first”

The conventional order — yesterday, today, blockers — buries the most useful item last, by which point attention has drained. Flip it. Ask for blockers first, while the room is fresh, and the meeting immediately earns its place: the first thing said is something the team can act on.

The stronger alternative: walk the board

Once a team has the habit, the sharpest upgrade is to stop asking the three questions person by person and instead walk the board.

Rather than going around the room, the facilitator moves across the work in progress — typically right to left, from nearly-done back toward just-started — and the conversation is about items, not people. Who’s on this? What’s it waiting on? What’s stalled? Anyone able to help push it over the line?

The shift is subtle and it changes everything. Person-by-person invites everyone to justify their day. Walking the board invites the team to get items to done. It naturally spotlights the work that’s stuck — the card that’s been in review for three days is impossible to hide when you’re staring at the column — and it stops the meeting rewarding the person with the longest task list. For the mechanics of running it, see the daily stand-up agenda; for more ways to vary the format, see stand-up formats to keep it fresh.

When to keep the three questions

Don’t throw them out reflexively. The three questions are the right tool for a young team, a newly-formed team, or one that’s genuinely low on the habit of talking to each other — they give structure where there’s none yet. The LinkedIn field wisdom here is real: a stand-up is partly a workaround for a team that can’t yet see itself clearly. Use the scaffolding while you need it, and let the team walk the board when it’s ready to talk about work instead of about itself.

Whatever structure you use, the questions only work inside a meeting that’s actually facilitated — the subject of much of the daily stand-up guide. See how to run an effective stand-up for the moves that keep it fifteen minutes, and copy-paste stand-up templates for prompts you can drop into Slack or Teams.

Frequently asked questions

What are the three daily stand-up questions?

What did I do yesterday, what will I do today, and is anything blocking me. The three questions come from early agile practice and give a team a shared structure for the daily sync. They work as a floor for a new team, but experienced teams often outgrow them — because answered literally, they produce a status report rather than a coordination conversation.

What should you say in a daily stand-up?

Say the things that change what a teammate does today. Name any blocker first and be specific about what you need and from whom. Share progress in terms of the goal — “checkout is code-complete, starting on the error states” — not a task diary. Skip anything that doesn’t affect the team’s plan for the day; that belongs in the tool, not the meeting.

What makes a good stand-up update?

It’s short, it’s aimed at the team rather than a manager, and it leads with what’s stuck. A good update tells the room something they can act on — a blocker to clear, a dependency to plan around, a hand-off to arrange. A weak update recites completed tasks that nobody needs to respond to. If your update wouldn’t change anyone else’s day, most of it belongs in the ticket.

What is a better alternative to the three questions?

Walk the board instead of the people. Rather than going person by person, move right to left across the items in progress and talk about the work — what’s blocked, what’s close, what’s stalled. It keeps the focus on getting items to done rather than on justifying individual effort, and it naturally surfaces the items that are stuck, which is what the meeting is for.