The Meeting Culture Audit: A Quarterly Review That Frees Up Hours

Recurring meetings are subject to a ratchet: they get created easily, attended by default, and cancelled almost never — because cancellation requires someone to actively decide the meeting has stopped earning its cost. The meeting audit is the mechanism that forces the decision. Run quarterly, it reliably recovers hours per person per week.

The audit, step by step

• Step 1 — Inventory: list every recurring meeting the team owns, with attendee count, frequency, and duration. Compute annual cost (attendees × hours × loaded rate × occurrences). Sorting by cost is usually the first surprise.
• Step 2 — Evidence: for each meeting, pull the last month of recaps and ask: what decisions did this meeting actually produce? Meetings with automatic recaps make this step trivial — an empty decisions section four weeks running is a verdict. Meetings with no record at all answer the question differently.
• Step 3 — Sentence each meeting: keep as-is; shrink (fewer people, shorter, less often); transform (convert status meetings to async updates); or kill. The default for meetings that failed step 2 is kill, with a two-week trial to see who notices.
• Step 4 — Re-justify the survivors: each kept meeting gets a one-line objective rewritten in the calendar invite. If the owner cannot write the line, the meeting returns to step 3.

The rules that make it stick

• Someone owns the audit: unowned processes decay. The team lead or ops owner runs it the same week each quarter.
• Killing is reversible — say so: 'we can always bring it back' lowers the bar to cancellation. In practice, almost nothing comes back.
• Watch the reflux: cancelled meetings reincarnate under new names within a quarter or two. The recurring audit is what catches them.
• Measure the reclaim: report the recovered hours after each audit. Visible wins fund the next round's political will.

Why recaps make audits honest

The audit's hardest step is evidence, and evidence is what automatic meeting records provide. When every meeting emits an Oya recap, the question 'what has this meeting produced?' has a documentary answer — decisions and completed action items, or their absence. Teams auditing against records cancel more confidently than teams auditing against feelings, which is exactly why the meetings least worth keeping prefer not to be recorded.