Replace status-update meetings with async written updates — synchronous time is for coordination and decisions, not information transfer

Why This Is a Rule

Status update meetings are the most common form of meeting waste. The format is typically: each person speaks for 2-5 minutes about what they did last week and what they're doing next week while everyone else listens (or doesn't). A 30-minute meeting with 6 people transfers 6 status updates at the cost of 3 person-hours of synchronous time. The same 6 updates written as 2-paragraph Slack messages transfer the same information at the cost of maybe 30 person-minutes of asynchronous writing and reading — a 6x efficiency improvement.

The key distinction is between information transfer (one-directional: "here's what I'm doing") and coordination (multi-directional: "we need to align on X, resolve conflict Y, make decision Z"). Synchronous meetings are expensive but necessary for coordination — real-time dialogue, negotiation, and decision-making benefit from the bandwidth of face-to-face interaction. Information transfer, by contrast, is inherently one-directional and doesn't benefit from synchronous co-presence. Reading is 2-3x faster than listening, and written updates can be consumed at each person's convenience rather than requiring simultaneous availability.

The exception clause is important: some "status update" meetings have evolved to include genuine coordination functions — "I'm blocked on X, can you help?" "Your timeline conflicts with mine, let's resolve it." If the meeting serves this coordination function beyond pure status transfer, it may warrant synchronous time — but the status-transfer portion should still be written, with the meeting time reserved for the coordination discussion.

When This Fires

• When evaluating recurring meetings for potential elimination or conversion
• When status meetings consistently feel like they could have been an email
• When implementing Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration (meeting consolidation) and looking for meetings to eliminate entirely
• When team members are spending 5+ hours per week in update-only meetings

Common Failure Mode

Keeping status meetings for "team bonding" or "visibility" when those purposes could be served more efficiently by other means. The meeting exists, people show up, so it must be valuable — but the actual value (information transfer) doesn't require the meeting format. Team bonding happens more naturally in working sessions; visibility is better served by written updates that create a searchable record.

The Protocol

(1) For each recurring meeting, apply the information-or-coordination test: "Does this meeting primarily transfer information (status updates) or coordinate action (decisions, conflict resolution, alignment)?" (2) If primarily information transfer → replace with asynchronous written updates. Define the format, cadence, and channel (weekly email, Slack thread, shared doc). (3) If primarily coordination but starts with a status round → split: status updates go async, coordination discussion stays synchronous with a shorter meeting duration. (4) Trial for 2 weeks: replace the meeting with async updates. If no one requests the meeting back, the async format is sufficient. If coordination issues arise, add back a shorter, coordination-focused meeting. (5) Calculate the time saved: (meeting duration × number of attendees) minus (writing time + reading time). This is the capacity recovered for all participants.