How to Run a Weekly Standup That Doesn't Waste Time

Status updates that should be async

Everyone reads from their task list while others zone out — 30 minutes × 6 people = 3 hours of collective time burned. At $200/hr average, that's $600/meeting. — Move status updates to written form. Use the meeting for decisions and blockers only.

No agenda or structure

Conversations spiral into tangents. Someone brings up a strategic question. Now it's a 90-minute meeting. — Meetings without agendas run 30-40% longer than meetings with them. That's an extra hour per week, minimum. — Share a 3-item agenda 24 hours before. If there's no agenda, cancel the meeting.

Too many people in the room

Half the room hasn't spoken in 3 weeks. They attend because they were invited, not because they need to be there. — Every unnecessary attendee adds cost without value. A 6-person meeting that should be 3 people costs double. — Apply the "two-pizza rule": if you can't feed the group with two pizzas, it's too many people.

No decisions made

Good discussion. Lots of input. No conclusions. Same topics come up next week. — The meeting was a ritual, not a tool. Your team leaves unclear and reverts to doing what they were already doing. — End every meeting with: "Here's what we decided. Here's who's doing what. Here's the deadline."

Wrong frequency or duration

Daily standups for a team that doesn't need daily check-ins. Weekly meetings that should be biweekly. — Meeting cadence should match work cadence. If nothing changes day-to-day, daily meetings are waste. — Match frequency to velocity. Fast-moving sprints → daily. Steady-state projects → weekly. Strategic work → biweekly.

The 15-Minute Weekly

Small teams (2-5 people), steady-state projects — [object Object],[object Object],[object Object],[object Object] — No laptops open (unless taking notes),If it takes more than 2 minutes to explain, it's a separate meeting,Standing optional, but keep the energy

The Async-First Standup

Remote teams, cross-timezone, teams that hate meetings — [object Object],[object Object],[object Object],[object Object] — Written updates are mandatory: no update means you're unblocked,Meeting only happens if there are blockers,If no blockers, the meeting is 0 minutes. Everyone gets time back.

The Client Team Sync

Consultants managing client projects with internal teams — [object Object],[object Object],[object Object],[object Object] — Everything is through the lens of client delivery,Internal process issues get their own time, not this meeting,If a client is at risk, that's the entire meeting

Letting one person dominate

Use a timer. Everyone gets 90 seconds. If someone goes over, politely cut them off: "Let's take that offline." This isn't rude. It respects everyone else's time.

Turning updates into problem-solving

Surface the problem in standup. Solve it after standup with only the relevant people. "Good catch, Derek and I will sort this out after the call."

Skipping when the lead is out

Rotate the facilitator role. If the standup can't happen without one person, it's too dependent on that person. Any team member should be able to run it.

No written record

Someone captures 3 things: decisions made, action items with owners, deadlines. Post it where everyone can see it. This takes 2 minutes and saves hours of "wait, what did we decide?"

Not canceling when unnecessary

If there are no blockers and no decisions needed, cancel the meeting. Send a message: "No blockers this week, meeting canceled, everyone gets 15 minutes back." Your team will love you for it.

Using the meeting for announcements

Announcements are one-way information. Send them in writing. Meetings are for two-way interaction: discussion, decisions, problem-solving.

Does every attendee need to be there?

Remove anyone who's been silent for 2+ meetings. Send them the notes instead.

Could this be async?

If you're just collecting status updates, switch to written updates and cancel the meeting.

Is 15 minutes enough?

If your "standup" regularly runs 30+ minutes, the format is wrong. Fix the structure, not the timebox.

Are decisions actually being made?

If topics recur week after week, the meeting isn't working. Add a "decisions" section and force conclusions.

Is the frequency right?

Try reducing frequency for 2 weeks. If nothing breaks, keep the new cadence.