Dev Tool · No signup

Stand-up Question Generator

120+ curated questions for engineering standups, retrospectives, team culture check-ins, and async warm-ups. Pick a category, roll, and copy.

Pick a category and hit Generate to see questions.

How to Use This Generator

The stand-up question generator is designed to keep your team's rituals fresh without becoming a productivity tax. Pick the category that matches the meeting, generate 1–5 questions, and copy them straight into Slack, Notion, or your video call chat.

Why Rotating Questions Matters

Any standup format runs its useful life in about six weeks. After that, the answers start to become templated ("worked on the ticket, will keep working on the ticket, no blockers") and the meeting stops surfacing what it's supposed to surface. The fix is not to abandon the standup — it's to rotate the prompt every few weeks so the team's attention gets pulled to a different part of the work.

The best engineering managers we've worked with keep a small set of standard prompts and rotate in one variant per week. That's what this tool is for: a curated bank so you never have to invent one on the spot.

When to Skip the Standup Entirely

Some teams don't need a daily live standup. Distributed teams across many time zones are almost always better off async. Teams shipping deep technical work often prefer a twice-weekly review to a daily one. If the standup is a habit rather than a source of information, it's fine to change the cadence — or replace it with a written channel. The point is the coordination, not the meeting.

FAQ

What makes a good standup question?+
A good standup question surfaces information the team actually needs — usually about blockers, progress, and priorities — without turning into a performance report. The classic three ("what did you do, what will you do, any blockers") work but get stale. Rotating in one culture or async warm-up question every few days keeps engagement up without derailing the 15-minute time box.
How long should a daily standup be?+
15 minutes for a team of 6–10. If it runs longer, the questions are too open-ended, the team is too big, or people are debugging live in the meeting instead of taking it offline. Time box it strictly, use written async updates for details, and reserve the live time for coordination and blocker resolution.
Are async standups better?+
For distributed teams across many time zones, yes. Async standups (written in Slack or a tool like Geekbot) preserve status information without forcing overlap. For co-located or lightly-distributed teams, live standups still win because the human connection and quick clarifications matter more than the calendar cost.
Should the standup include manager questions?+
The manager's presence changes the vibe of a standup. If they're there to help remove blockers, great. If they're there to check progress, engineers will subtly perform for them and the standup loses honesty. Best pattern: manager attends but says almost nothing, only speaks up when someone flags a blocker they can help with.
How do you keep standups from going stale?+
Rotate the question set every 4–6 weeks. Add one culture or warm-up question at the start once or twice a week. Change the meeting format monthly — sometimes go around the circle, sometimes do a written pre-read, sometimes skip the standup entirely and just check the async board. Predictability breeds disengagement.

Find teams with cultures worth joining

Browse thousands of engineering roles at companies with strong rituals, healthy standups, and cultures that respect your focus time.

Browse Engineering Jobs → More Dev Tools →