A recurring one-hour meeting with six people is not a one-hour meeting. It’s six hours of payroll, every week, forever. At a loaded cost of $75 an hour per person, that standing sync is a $23,400-a-year subscription — auto-renewing, rarely reviewed, and approved by nobody. Most calendars carry several of them. Nobody remembers signing up.
The fix is not “fewer meetings” as a vibe. It’s a system: audit what you have, kill or convert what doesn’t earn its cost, and run what survives so it produces the one thing only a live meeting can produce — a decision people actually commit to. Here’s the whole system, scripts included.
Step 1: Run the 20-minute audit
Open your calendar to a typical week. List every recurring meeting in a plain table with four columns:
- Type. Tag each one: Decision (we choose something), Status (we tell each other what happened), Creation (we build something together), or Connection (we stay human). Be honest — most “working sessions” are status meetings wearing a costume.
- Cost. Attendees × hours × a loaded rate (use $75/hour if you don’t know; it’s conservative once salary, benefits, and overhead stack up). Write the annual number. It will upset you. Good.
- Output. What did the last three sessions actually produce? Decisions, artifacts, or vapor.
- Vanish test. If this meeting disappeared for a month, what would break — specifically?
You now have something almost no one has: a P&L for your calendar. The rest of the playbook is just acting on it.
Step 2: Apply the kill test
For each recurring meeting, three questions:
- Did the last three sessions produce a decision, an artifact, or a genuinely stronger relationship?
- If this meeting didn’t exist, would anyone rebuild it from scratch this week?
- Could the same output happen async — in writing — without losing anything that matters?
Two no’s and a yes: kill it or convert it. The conversion rule of thumb: status is written, decisions are live, creation is scheduled deep work, connection is deliberately social. A status meeting converted to a written update isn’t a downgrade — it’s usually an upgrade, because writing forces the vague to become specific, and nobody has to perform busyness out loud at 9 a.m. Protecting the freed-up hours is its own discipline — that’s attention architecture, and the hours will be reclaimed by someone else’s calendar if you don’t claim them first.
Step 3: Shrink what survives
Two dials: duration and headcount. Default every surviving meeting to 25 or 50 minutes — the shaved five minutes is your buffer against back-to-back decay. Then run the attendee test: every person in the room should be deciding, essential to informing the decision, or executing the outcome. Everyone else is an audience, and audiences get notes. If someone can be replaced by the notes, replace them with the notes — they’ll thank you.
Step 4: The agenda spine
An agenda that lists topics (“Q3 planning,” “website update”) is theater. Topics generate talk. Decisions generate outcomes. The spine of a real agenda:
- The decision, in one sentence, in the invite. “Decide: do we raise prices in September or January?” If you can’t write this sentence, you don’t need a meeting yet.
- A one-page pre-read, sent 24 hours ahead. Context, options, the owner’s recommendation. One page, hard limit.
- A named decider. In the invite, by name. A decision meeting without a decider is a debate club.
- Timeboxed discussion. Most single decisions fit in 15 minutes of structured argument.
- The two-minute close. Decisions made, owners named, dates attached — read aloud before anyone leaves.
How hard calls get made inside that timebox — options, criteria, and no relitigating — is its own system; we wrote the Decision Playbook for exactly that.
Step 5: Run the room
Three roles, which can be three people or two: the driver runs the agenda and the clock, the decider makes the call, the scribe captures decisions and owners in real time. Start on the decision, not a recap — if half the room skipped the pre-read, take five minutes of silent reading at the top; it’s faster than a twenty-minute retelling. Tangents go to a visible parking lot with a name attached. The driver’s job is one sentence, used without apology: “We have twelve minutes and one decision left — can we park the rest?”
Step 6: Close the loop
Notes ship within 24 hours, three sections, nothing else: Decided (what we chose), Owned (who does what, by when), Parked (what we deliberately didn’t decide). If your notes have no owners and no dates, the meeting was theater and the notes are the program. Feed the Owned list straight into your weekly review so commitments made in rooms survive contact with the week.
The scripts
- Declining without burning anything: “I don’t think I add value to this decision — send me the notes and I’ll flag anything within a day. Ping me if something needs my call live.”
- Converting a recurring meeting: “Proposal: we swap Monday’s sync for a written update by 10 a.m., and keep a 25-minute Thursday slot only if something needs a live call. Two-week trial, then we decide?” The trial framing matters — nobody has to defend the old meeting to accept an experiment.
- Shrinking the list: “Trimming this invite to the people making or executing the decision. You’ll get notes same day — grab 10 minutes with me if anything looks off.”
- Adding an expiry date: “Setting this series to end October 1 — if it’s still earning its slot, renewing takes ten seconds.”
A worked example
A team lead runs the audit and finds 11 recurring hours: two team syncs, a cross-functional status call, four project check-ins, a metrics review, a 1:1 block, a planning meeting, and a “quick” Friday wrap. The verdicts: the Friday wrap and one project check-in fail the vanish test outright — killed. The cross-functional call, the metrics review, and two project check-ins become written updates with a comment window — converted. The team syncs merge into one 25-minute session with a decision-first agenda. The 1:1s and planning survive untouched — they were the two that were working. Result: 11 hours becomes about 5, decisions now close in the room instead of drifting, and the written updates turn out to be more legible than the meetings they replaced. The freed hours went to actual work — which was the point all along.
Our take: Meetings aren’t the enemy; unpriced meetings are. The moment you attach a dollar figure and an output requirement to every recurring slot, the calendar starts making its own case — most of it for deletion. Run the audit once a quarter, give every recurring series an expiry date, and guard the one thing a room full of humans still does better than any document: commit to a hard call, together, out loud.
Failure modes
- The zombie recurring. The project ended; the meeting didn’t. Expiry dates on every series — renewal should be the active choice, not cancellation.
- The eight-person decision meeting where nobody decides. No named decider means no decision — just consensus cosplay. Name the decider in the invite or don’t send it.
- The meeting after the meeting. If the real conversation happens in DMs afterward, disagreement wasn’t safe in the room. That’s a candor problem; no format fixes it.
- Agenda theater. Topic lists that generate an hour of informed talking and zero owners. If the invite can’t state the decision, it’s a memo that hasn’t been written yet.
- Async fundamentalism. Some things need a room: real conflict, genuine ambiguity, kickoffs, bad news. Convert those to writing and you’ll pay for the “saved” hour many times over. If your calendar is overrun because you can’t decline anything, that’s a boundary problem — the Say-No Playbook handles that half.
