Library/T-05
Meeting Keep, Kill or Redesign
Put every recurring meeting through one of three verdicts.
Subtract · Exit (close)T-05
The pattern it solves
Standing meetings accumulate and nobody is allowed to end one.
Signals you need it
Meetings without agendas. The owner attends out of habit. Updates that could be written.
Use it when
The Calendar Audit shows high meeting load or fragmentation.
What it takes in
The recurring meetings on the calendar (the Calendar Audit's meeting list works).
What you end up with
A verdict per meeting: keep, kill, or redesign (shorter, fewer people, async, less often).
The steps
- 1.For each meeting write its purpose in one sentence. If you cannot, kill it.
- 2.Ask: is a decision made here that cannot be made in writing? If no, go async.
- 3.Ask: does the owner's presence change the outcome? If no, remove the owner.
- 4.Cut length and frequency to the minimum that still serves the purpose.
- 5.Review in 30 days.
How it returns time
`length × attendees × frequency × 52` returned for every meeting killed or reduced.
What to measure
Recurring meeting hours per week, owner and team, before and after.
What to measure, before and after. Not what anyone achieved — there are no client results to report.
Where it comes from
Time Operators.
What it fixes
The leaks this addresses
Next