Too many meetings: the math nobody runs in the room

The invoice nobody signs

Every other spend in your company has an approval chain. A $4,000 software subscription gets reviewed. A $25,000 vendor gets three quotes and a contract. But a recurring Tuesday meeting — eight people, sixty minutes, fifty-two weeks — gets created by anyone with calendar access, in eleven seconds, and runs forever. Do the arithmetic those eleven seconds skipped: 8 × 1 × 52 = 416 hours a year. At a modest $60 loaded hourly cost, that's ~$25,000 — for one standing meeting. A company running ten of them is spending a salary on synchronized sitting, with no owner, no output definition, and no renewal review.

And the visible cost is the smaller half. The 10:30 meeting doesn't take an hour — it takes the morning: the hour before is too short to start anything deep, and the hour after is recovery and residue. Meeting load and deep-work capacity aren't two budgets. They're one budget, and the meetings spend it first.

Why meetings multiply (the real functions)

Meetings persist because they quietly serve functions nobody will say out loud. The honest taxonomy:

• Status theater. Eight people take turns narrating what a dashboard already knows, while seven of them rehearse their own turn. This is a reporting system wearing a meeting costume — and reporting systems don't need chairs.
• Responsibility diffusion. A decision someone is afraid to own gets converted into a meeting, so the outcome has twelve fingerprints and no author. The meeting isn't producing the decision; it's laundering it.
• Visibility performance. In cultures where presence signals contribution, meetings are where ambition goes to be seen. Attendance becomes a career strategy, which is why the invite list only ever grows.
• Loneliness management. The most human one: for many managers, meetings are the social texture of the job. Real need — wrong instrument, and an expensive one to bill eight salaries for.

Most meetings aren't communication. They're status systems, decision laundering, and company wearing the costume of work — billed by the hour, times everyone.

The four meetings that deserve to live

1. The decision meeting. A real choice with stakes, multiple necessary inputs, a named owner, and the decision made in the room. Test: if it ends with "let's think about it," it wasn't a decision meeting — it was a preview.
2. The working session. People building an artifact together — the plan, the design, the draft — where the bandwidth of live collaboration genuinely beats the round-trip of async. Ends with the artifact, not with notes about a future artifact.
3. The human meeting. One-on-ones, hard conversations, trust repair. The relationship layer is real work, async genuinely can't carry it, and cutting these to save hours is how teams get efficient and brittle simultaneously. Protect them.
4. The inflection alignment. Kickoffs, post-mortems, strategy turns — the rare moments when everyone's mental model needs rebuilding at once. High cost, justified by frequency: these should be occasional by definition. A weekly "alignment" meeting is a contradiction in terms; nothing inflects weekly.

Everything else on the calendar should have to argue for its life — which brings us to the protocol.

The kill protocol

1. Inventory and price. List every recurring meeting; run the formula next to each (people × duration × frequency × rate). Just seeing "$23,400/yr" beside "Monday Sync" changes the meeting's negotiating position permanently.
2. Ask the three questions of each: What decision or output does this produce? What would actually break after two weeks without it? Could a dashboard, memo, or two-line async update do this job? Write the answers down — vague answers are answers.
3. Suspend, don't debate. The genius of the purge approach (Shopify's calendar reset — deleting recurring meetings of 3+ people — reportedly cleared over 300,000 hours) is inverting the burden of proof: instead of justifying deletion, meetings must justify re-creation. The lighter version: every meeting that failed the three questions gets a two-week suspension trial. Track what's genuinely missed. Most suspended meetings are never mentioned again — and that silence is the audit.
4. Replace the function before the gap is felt. Status → shared dashboard or async update with a deadline. Broadcast → memo with "objections by Thursday noon; silence is consent." Decision-laundering → a named owner and a deadline (this one replaces a meeting with courage, which is why it's the hardest swap on the list).
5. Re-audit quarterly. Meetings regrow — every new project, hire, and anxiety plants one. A 30-minute quarterly pruning keeps the calendar honest forever.

Rules for the survivors

• Default to 25/50 minutes. Meetings expand to their container (Parkinson's law has never once been refuted by a calendar); shrink the container and the content survives, minus the throat-clearing.
• No owner + output in the invite, no meeting. "To discuss X" is not an output. "Decide between A and B; owner: Deniz" is.
• Prune the list to speakers. Anyone who'd attend in listen-only mode gets the notes instead — their morning is worth more than their visible attendance. (If people need to be seen to be valued, that's a culture bug; fix it directly, not with chairs.)
• Cluster into bands. Meetings live back-to-back in defined windows — early afternoon protects the morning peak (match the calendar to the energy curve) — leaving contiguous deep-work plains untouched.
• Let the machine take the minutes. Recording, transcription, action-item extraction, and the follow-up chasing are exactly the rule-based work agents absorb — which also kills the "we need a meeting to follow up on the meeting" lifecycle at the root.

Frequently asked questions

How much do meetings actually cost a company?

People × duration × frequency × loaded rate: one weekly 8-person hour ≈ $25K/year, before the context-switching tax on either side. Most companies run ten or more, approved by no one.

Which meetings are actually worth having?

Decisions made in the room, working sessions that produce artifacts, one-on-ones and the human layer, and alignment at genuine inflection points. Status and broadcast belong to dashboards and memos.

How do I reduce meetings without losing alignment?

Replace the function first: dashboards for status, memos with comment deadlines for broadcast, named owners for laundered decisions. Then 25/50 defaults, speaker-only invites, and clustered meeting bands.

Should we do a meeting reset like Shopify did?

A suspension trial works at any size: every recurring meeting that can't name its output gets two weeks off; re-create only what's missed. Most never are — that silence is the audit.