Replace status-update meetings with async written updates…

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… (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.