The Best Standup Questions for Engineering Teams (Hint: Not Those Three)
The classic standup questions for engineering teams produce status theatre, not signal. Here are better ones that surface what actually matters.
By Ellis Keane · 2026-03-26
In 1790, the Royal Navy formalised its watch report protocol. Every four hours, the officer of the watch would relay a brief to his relief: sea state, wind changes, any vessels sighted, and anything requiring the incoming officer's immediate attention. The format was ruthlessly efficient – not because sailors had short attention spans, but because a frigate in contested waters couldn't afford ceremonial waffle. You reported what had changed, what was risky, and what needed the next person's judgment. Everything else was noise.
Two hundred and thirty-odd years later, the standup questions for engineering teams have managed to invert this entirely. We've kept the ritual (same time, same people, same room or Zoom call) while gutting the signal. "What did you do yesterday?" is not a watch report. It's a performance review administered daily, in public, to people who'd rather be writing code.
(And yes, I've stood in plenty of standups where I rehearsed my update in my head while someone else was talking. You have too. Let's not pretend otherwise!)
I ran standups badly for years, by the way. Full confession. I'd dutifully go round the circle, collect updates I'd forget within the hour, and then wonder why our retros kept surfacing the same problems. It took an embarrassingly long time to realise the questions themselves were the bottleneck – not the people answering them.
The Three Default Questions and Their Problems
You know the ones. "What did you do yesterday? What are you doing today? Any blockers?"
These standup questions for engineering teams aren't terrible in principle, but in practice they produce a very specific kind of dysfunction. "What did you do yesterday" optimises for memory, not relevance – so you get a chronological narration of someone's Tuesday rather than the two things that actually matter. "What are you doing today" produces a miniature project plan that nobody will remember by lunch. And "any blockers" gets answered with "no" by default – I once watched a junior engineer say "no blockers" for six straight days while quietly stuck on an auth issue they didn't want to raise in front of the whole team. Publicly admitting you're stuck requires psychological safety that most teams haven't earned yet.
The result is what I'd call status theatre – fifteen minutes of people reciting work summaries at each other, after which everyone disperses with exactly the same information they had before the meeting started. It feels productive. It is not productive.
The traditional three standup questions optimise for accountability, not information flow. They tell you that work happened, but not what needs your attention right now.
Better Standup Questions for Engineering Teams (by What They Reveal)
The following questions aren't a universal template – pick 2 or 3 that match your team's current pain, rotate them monthly, and retire any question that starts producing rehearsed answers.
Questions That Surface Risk
- "What's the riskiest thing on your plate right now?" – My favourite standup question, full stop! It skips past yesterday's accomplishments and lands squarely on what might go wrong today. People know what's risky, but they won't volunteer it unless you ask directly.
- "Is anything taking longer than you expected?" – Quieter than "any blockers" but far more revealing. A task taking longer than expected is often the first symptom of a problem that hasn't been named yet.
- "What are you least confident about this week?" – Better suited to weekly syncs than daily standups, but it gives you an early warning list instead of a backward-looking activity log.
Questions That Surface Dependencies
- "Where are you waiting on someone else?" – This is your dependency detector. In most teams I've worked on, more engineering work stalls on unacknowledged dependencies than on technical complexity. The PR that's been open for three days, the design review that hasn't happened, the decision that's quietly been deferred – these are the actual blockers, even when nobody calls them that.
- "Who do you need to talk to today?" – Shorter, more actionable. If two people both answer "each other," you've just saved them a day of async back-and-forth by putting them in a room. (This one has genuinely rescued entire sprints for me – turns out people will sit in parallel confusion for days rather than walk five metres to talk.)
Questions That Surface Learning
- "What surprised you since the last standup?" – Brilliant for catching architectural misunderstandings early. (And, trust me, there are always architectural misunderstandings.) If an engineer discovers that an API behaves differently than the docs suggested, or that a migration touches more tables than the ticket implied, that surprise is worth more to the team than any status update.
- "What do you know now that you wish you'd known on Monday?" – Again, more useful for weeklies. But it captures institutional knowledge that would otherwise get forgotten by next sprint.
Questions That Surface Morale (Use Sparingly)
- "On a scale of 1 to 5, how's your energy today?" – I've seen this work well exactly once, on a team where the lead had genuinely built trust over years. In most contexts it feels invasive. Know your team before deploying this one.
- "Is this work interesting?" – Sounds casual, but consistently boring work is a retention signal. If someone's been grinding through migration tasks for three sprints running, this question gives them permission to say so.
Group Standups vs 1:1s: Different Formats Need Different Questions
Not all of these standup questions for engineering teams belong in the same meeting. In a group setting, you want questions that are fast to answer and produce information useful to everyone present. In a 1:1, you have room for longer, more reflective questions.
Group standup (pick 2, rotate weekly):
| Question | What it reveals | Time per person | |----------|----------------|-----------------| | What's the riskiest thing on your plate? | Forward-looking risk | ~30 seconds | | Where are you waiting on someone? | Dependencies | ~20 seconds | | What surprised you? | Hidden complexity | ~30 seconds |
1:1 check-in (pick 2 or 3):
| Question | What it reveals | Time | |----------|----------------|------| | What do you know now that you wish you'd known Monday? | Learning gaps | 2–3 minutes | | Is anything taking longer than expected? | Emerging risk | 1–2 minutes | | Is this work interesting? | Engagement and morale | 1–2 minutes | | What's the one thing I could unblock for you? | Manager action items | 1 minute |
Group standups need to be short and useful. 1:1s can afford exploration, because the audience is one person who actually has the context to act on what they hear.
The Anti-Pattern: Questions That Create More Work
Some popular standup "improvements" actually make things worse. If your format requires engineers to prepare a written update before the meeting, you've created a pre-standup standup – a ceremony to prepare for a ceremony. If it demands numeric estimates of task completion ("what percentage done is the API migration?"), you've built a micro-tracking exercise that incentivises optimistic rounding. And if it requires people to update a Linear board during the call, you've turned a synchronous conversation into fifteen minutes of watching people type.
(The irony, of course, is that every one of these was introduced to "make standups more efficient." The ceremony grows to fill the time available, and then politely requests more.)
If your standup improvement requires preparation time, you've added overhead, not removed it. The best standup question is one that produces a useful answer in under thirty seconds and doesn't require anyone to do homework before the meeting.
A Practical Set You Can Start With Tomorrow
If you want something concrete to try for two weeks, here's what I'd recommend:
Daily standup (3 questions, strict 15-minute timebox):
- "What's the riskiest thing on your plate?" – Catches problems before they turn into blockers.
- "Where are you waiting on someone?" – Makes invisible dependencies visible.
- "Anything the team should know?" – Open-ended catch-all, but framed as "important things only."
That's it. No "what did you do yesterday" – your tools already have that information sitting in your Linear board, your GitHub activity feed, and your Slack threads. No "what will you do today" – if your sprint plan is current, this question adds nothing. Just: what's risky, what's stuck, and what's surprising.
If after two weeks the standups still feel like ceremony, the problem probably isn't the questions at all. It might be that daily synchronous check-ins aren't the right format for your team, and that's a perfectly reasonable conclusion to reach. The Royal Navy figured out their watch report format in the 18th century and then, crucially, stopped redesigning it every quarter. Sometimes the best process improvement is admitting the process isn't needed.
"The Royal Navy figured out their watch report format in the 18th century and then, crucially, stopped redesigning it every quarter. Sometimes the best process improvement is admitting the process isn't needed." – Chris Calo
Let Sugarbug surface your team's activity automatically – so your standup can skip the status report and focus on what matters.
Q: What are the best standup questions for engineering teams? A: Honestly, "What's the riskiest thing on your plate?" and "Where are you waiting on someone?" will get you further than the traditional three ever did. The classic standup questions for engineering teams optimise for status recitation – who did what yesterday – rather than surfacing the risks and dependencies that actually change how your day goes.
Q: Does Sugarbug help automate engineering standups? A: Sugarbug connects your engineering tools – Linear, GitHub, Slack, Figma – into a knowledge graph that surfaces what changed since the last standup automatically. Instead of asking people to recite what they did yesterday, Sugarbug shows you, so the standup can focus on the conversations that need human judgment rather than status reporting.
Q: How long should an engineering standup take? A: Fifteen minutes, hard ceiling, for a team of 5 to 8. If yours runs longer, you're either asking questions that produce too much low-value output (hello, "what did you do yesterday?") or the team is solving problems that deserve their own meeting. Two minutes per person is a reasonable benchmark to aim for.
Q: Can Sugarbug replace daily standup meetings? A: Sugarbug doesn't replace standups – it replaces the status-reporting portion of them. By pulling recent activity from GitHub, Linear, and Slack into a single view, the "what did you do yesterday" question answers itself. What remains is the part of the standup that actually benefits from being synchronous: risks, dependencies, and decisions that need the room's attention.
Q: What makes a standup question effective? A: It produces new information in under thirty seconds, requires zero preparation, and surfaces things the team didn't already know. If people start giving the same rehearsed answer every day (you'll know – you'll hear it), retire the question and try a different one. The best standup questions have a shelf life, and that's fine.
If your standups spend more time on status recitation than actual decisions, Sugarbug can handle the reporting portion automatically – so your fifteen minutes go to the things that actually need a human in the room.