Stop running weekly standups as recap meetings

Look at your last weekly standup honestly. Of the forty-five minutes the team spent in that meeting, how many were spent on people re-stating things that are already known and recorded somewhere? Updating each other on tickets that anyone could see in Trello. Recapping conversations that happened in Slack. Re-summarizing the status of projects the rest of the team has been reading about all week.

If the answer is "most of it", you are not unusual. The weekly standup at most SMEs has quietly devolved into a synchronization meeting that exists because the team does not have a real synchronization layer underneath. The meeting is doing the job of a missing piece of infrastructure, badly, in expensive synchronous time.

This is fixable, and the fix is not "have shorter standups".

What standups were supposed to do

The original intent of a standup was tight. Each person says, briefly: what they did, what they're doing, what is blocking them. Fifteen minutes max for a team of seven. The point was not information transfer in any deep sense. It was a coordination beat. A blocker surfaces. Someone offers to help. The meeting ends.

What happened, over time and at scale, is that "what I did" expanded. Without a shared substrate where the team can already see what each person did, the standup became the substrate. People started preparing updates. Updates got longer. The fifteen-minute beat became a forty-five-minute recap. The blockers, which were the actual point, got buried in the middle.

Most companies have not noticed this drift because each individual meeting still feels productive. People are talking. Information is moving. The actual cost — that you are paying for the same information to be transferred orally that was already available in writing — does not show up anywhere.

The cost of synchronous recap

Take a team of eight. Forty-five minutes per person of pre-meeting prep (status doc, update notes, what to share) plus the meeting itself. That is roughly eight hours of senior-team time per week, ninety percent of which is recap of information that already exists.

Across a year, that is four hundred hours, which is two and a half months of one senior person's time, consumed by the act of orally re-stating things that were already written down. Per team. If you have three teams running variants of this ritual, you have committed seven and a half months of senior time per year to recap.

This is not a small operational tax. It is a significant chunk of payroll, and it is invisible because it is paid one meeting at a time.

Why "make it shorter" fails

The reflex response is to shorten the standup. Cap it at thirty minutes. Then twenty. Then enforce a strict round.

This works for about three weeks and then quietly stops working. The reason is that the standup is doing real work — orally synchronizing the team on what has been happening — and that work has to happen somewhere. If you cap the meeting at fifteen minutes, the synchronization that was happening in the missing thirty minutes either moves to side conversations (which are worse, because they are not visible to the whole team) or simply doesn't happen, and the team starts feeling out of sync.

The size of the meeting is a symptom. The disease is the absence of a substrate that lets the team be synchronized without speaking.

What a real synchronization layer looks like

Imagine that, at any time, anyone on your team could ask a question in plain language — "what changed on Project X this week", or "what is currently blocked across the team" — and get back a structured, current answer pulled from the actual conversations, tickets, and updates that have been happening.

In that world, the standup does not need to be a recap. Everyone walks in already knowing what has been happening, because they have either read or queried the substrate at their own pace. The meeting reduces to the original intent: blockers surface, coordination happens, the meeting ends.

The substrate is what most companies are missing. The standup has been doing the substrate's job, and doing it badly.

The shape of meetings that survives

At companies that have built this layer, three patterns emerge.

The weekly standup gets dramatically shorter — fifteen to twenty minutes — and is composed almost entirely of coordination items, not status updates. The status is read off the substrate by anyone who needs it, on their own time.

The post-meeting notes go away. The reason for post-meeting notes was that they were the only persistent record of what was discussed. With a substrate that captures conversations automatically and structures them queryably, the notes are redundant.

The one-on-ones get more substantive. The "let me update you on what's been happening" portion of every one-on-one collapses, because both parties already have the same view of the work. The conversation goes immediately to the things that actually require a human conversation: judgment calls, growth, hard problems.

These are not small changes. Across a quarter, they are the equivalent of one full-time hire's worth of senior time given back to actual work.

"But the team needs the face time"

A common objection is that standups serve a social purpose, not just an informational one. The team gets a regular moment to see each other, especially in distributed setups.

This is fair, and it is important. It is also not what an information-heavy standup is delivering. A meeting where most of the time is consumed by status updates is not actually face time; it is a transactional ritual where people perform updates at each other.

The fix is to be deliberate about what the meeting is for. If it is informational, make it short, sharp, and focused on what genuinely requires synchronous discussion. If it is social, make it social — without forcing it through a status-update format that satisfies neither purpose. Most companies that make the shift end up with two short rituals (a fifteen-minute coordination beat and a separate, shorter social moment) instead of one bloated standup, and the team prefers it.

A diagnostic

Ask one question at your next standup. "Of what I am about to say, how much was already visible to the team this week?"

If the honest answer is "almost all of it", the meeting is doing recap work, not coordination work. That recap work is happening because the team has no other way to be synchronized. The cost of continuing to pay this in synchronous time is significant, and growing as the team grows.

The standup, at its best, is a fifteen-minute coordination beat. At its worst, it is a forty-five-minute synchronous status report. The difference between them is whether the team has a substrate underneath that can carry the status burden without anyone having to speak it out loud.

Build the substrate. The standups will shrink. The team will thank you. The hours come back.