50 Weekly Standup Questions That Actually Get Good Answers

"What did you do yesterday? What are you doing today? Any blockers?" These three questions have been running standups since the mid-90s when Scrum formalized them from Jeff Sutherland's early XP experiments. They're not bad questions. But after a few weeks, most teams stop actually thinking about the answers and just fill in the template. The standup becomes a status read-out that nobody really listens to, and then it becomes a meeting everyone wishes they could skip.

The fix isn't to abandon standups — it's to rotate or sharpen the questions. Here are 50 that consistently generate more honest, useful, and engaged responses, organized by what you're trying to achieve.

Daily standup questions (work focus)

These replace or supplement the classic three. Use them in rotation to prevent the answers from becoming automatic.

1. What's the most important thing you'll ship today?
2. What's your confidence level (1–5) that you'll finish what you planned?
3. What would make today a win for you?
4. Is there a decision you need to make — or need someone else to make — before you can move forward?
5. What did you finish yesterday that you're proud of, even if it was small?
6. Is there anything you started yesterday that turned out to be more complex than expected?
7. Are you waiting on anything from another person or team today?
8. What's the one thing that, if it stayed blocked, would most hurt this week?
9. Is anything on your list today that shouldn't be — scope creep, tangents, someone else's work?
10. What's your energy level today, and does your plan match it?

Weekly sync questions (Monday)

Monday kickoff questions set the direction for the week. They should surface priorities, dependencies, and risks — not just restate what's on the sprint board.

1. What does a successful week look like for you?
2. What are you most looking forward to working on this week?
3. What are you most worried about or uncertain about this week?
4. Is there anything from last week that's carrying over and might affect this week's plan?
5. Is there a decision that needs to be made this week — and does it have an owner?
6. What do you need from someone else (on the team or outside) to hit your week's goal?
7. Is there anything that might pull you away from your priorities this week?
8. What's something you'd like to learn or try this week?
9. Is there a process or tool slowing you down that we should talk about?
10. Is your workload this week reasonable, too heavy, or light enough for stretch work?

Weekly reflection questions (Friday)

End-of-week questions should close loops: what got done, what didn't, what was learned, and what needs attention next week. Friday answers also become your Monday kickoff context.

1. What's your biggest win this week?
2. What didn't go as planned, and why?
3. What's one thing you learned this week?
4. What are you carrying over to next week — and is that carry-over expected or a problem?
5. Did you do the work that was actually most important, or did you get pulled off-track?
6. Who do you want to give a shoutout to this week?
7. What's one thing you'd do differently if you could redo this week?
8. Is there a process that's been frustrating you for a while that we should fix?
9. What are you most looking forward to next week?
10. On a scale of 1–5, how would you rate this week's team collaboration?

Sprint ceremony questions

These are specifically for engineering, product, and design teams running sprints. They go into sprint planning, mid-sprint check-ins, and retrospective prep messages.

Sprint kickoff

1. Is the sprint goal clear, and does your work connect to it?
2. Are there any tickets in the sprint that you don't have enough context on to start?
3. What's your biggest risk for this sprint, and what would need to happen to derail it?
4. Is there any external dependency (another team, a vendor, a decision) that could block sprint work?
5. Is the sprint scoped correctly — do you have enough work, or are you over- or under-committed?

Mid-sprint check-in (usually Wednesday or Thursday of the sprint)

1. Based on where you are right now, will everything in the sprint get done?
2. Is there anything in the sprint that's grown in scope since it was estimated?
3. Is there anything in the sprint that no longer needs to be done?
4. What's the most important thing to complete before the sprint ends?
5. What's at risk of not making it, and what would help?

Retrospective prep

1. What went well this sprint that we should keep doing?
2. What slowed us down that we should change?
3. What's one thing we should try differently next sprint?
4. Was there anything in this sprint that felt like wasted work?
5. How well did we collaborate as a team this sprint (1–5)?

Async check-in questions for remote teams

Remote and distributed teams need questions that work in writing — questions that don't require tone or real-time back-and-forth to land correctly.

1. What's the most important thing on your plate right now?
2. Is there anything you're waiting on from someone else? (If so: who, what, by when?)
3. What's your plan for the rest of the day / rest of the week?
4. Is there anything you wish the team knew about what you're working on?
5. On a scale of 1–5: how connected do you feel to the team's work right now?
6. What's one thing you're proud of that you don't think got enough visibility?
7. Is there anything that's been quietly draining you that we should talk about?
8. What would make the biggest difference to your productivity this week?
9. Is there someone on the team you've been meaning to connect with and haven't?
10. What's the hardest problem you're working on right now?

How to rotate questions without losing ritual

Rotating questions is good, but structure matters. If the questions change every day at random, people can't build a habit around answering them. A better approach:

• Keep 1–2 fixed questions that are always there (e.g., 'what are you working on today?' never changes). These are the bones of the ritual.
• Rotate 1 variable question weekly or bi-weekly. This provides variety without removing the structure.
• Use themed days — Monday is priorities, Wednesday is blockers, Friday is wins. People know what's coming without the exact wording being identical every time.

With Schedule Message, you can set up separate recurring messages for each day of the week — a Monday kickoff message, a different Wednesday blocker check, a different Friday reflection — each with different questions but all on the same automatic schedule. See how to run a daily standup in Slack without a meeting for the full setup.

The best standup question is the one your team actually answers thoughtfully, not the one that fills in the template automatically. Start with the classics, watch where answers go on autopilot, and replace those with something that makes people think for a moment before replying. That moment of thinking is where the value lives.