How to Run a Remote Standup Meeting That Doesn't Waste Time
The daily standup is the most common meeting format in knowledge-work organizations and the one most likely to waste time. When it works, it surfaces blockers and creates alignment in 15 minutes. When it doesn't, it becomes a status report roundtable that nobody needs and everyone could have sent in a Slack message.
What is a standup meeting?
A standup is a short daily or regular team sync, originally borrowed from agile software development. The name comes from the practice of having participants stand — a physical cue to keep the meeting short. In remote work, 'standing' is metaphorical, but the time constraint is still the point: typically 15 minutes, rarely more than 30.
What should every standup cover?
- What did you complete since the last standup? (Yesterday/since last time)
- What are you working on until the next standup? (Today)
- What is blocking you? (Blockers)
- Optionally: any upcoming dependencies or handoffs the team needs to know about.
What makes standups run long and how do you fix it?
- Problem-solving during the standup: blockers should be named, not resolved in the meeting. 'That's a blocker — let's solve it after standup with the people who need to be involved.'
- Status theater: long explanations of work that only one person needs to hear. Keep it to what the team needs to know to coordinate.
- Absent participants causing wait: start on time, every time. The meeting waits for nobody.
- No time limits per person: give each participant 2 minutes max. Most blockers can be named in 30 seconds.
How do AI meeting notes help standup meetings?
Standup AI recaps are useful primarily for team members who missed the meeting and for tracking blockers over time. When every standup produces a brief written record, patterns become visible — blockers that appear multiple days in a row, teams that frequently have the same dependency issue. MeetOye's Oya generates the record automatically for every standup, including the written output that the team can reference async.