The meeting audit: how we helped teams cut sync time in half

Every recurring meeting was created by a reasonable person solving a real problem. That's what makes them so hard to kill. The weekly status call exists because in March someone shipped the wrong thing. The Monday all-hands exists because two teams duplicated work once. Nobody remembers the incidents — but the calendar does, forever.

Over the past year we've run a structured meeting audit with dozens of teams moving onto Relay, and internally every quarter. The teams that follow it through cut recurring sync time roughly in half — not by “banning meetings,” but by making each one prove it still earns its slot. Here's the whole exercise. It takes about 45 minutes and a spreadsheet — you don't need our product to run it.

Step 1: Inventory the true cost (15 minutes)

List every recurring meeting your team holds. For each one, multiply duration × attendees × occurrences per month. Don't estimate prep time or context-switch cost yet — the raw number is startling enough. An 8-person, 30-minute weekly standup is 16 person-hours a month. Two working days, every month, for one ritual.

Now add one column: “What would break if this vanished for a month?” Write the honest answer, not the official one. “We'd miss each other” is an honest answer — and it points to a social ritual worth keeping, just not disguised as a status meeting.

Step 2: Classify — decision, creation, or broadcast (10 minutes)

Every recurring meeting is mostly one of three species:

• Decision meetings — options are debated, a call gets made. These are usually worth their slot, if the options were written down beforehand.
• Creation meetings — critique, pairing, workshopping, planning poker. The work happens in the room. Almost always keep these.
• Broadcast meetings — one person talks, everyone else listens (or pretends to while answering messages). Status updates, readouts, “alignment.” This is the species async replaces outright.

Be ruthless about hybrid meetings. The classic weekly team meeting is 20 minutes of broadcast wrapped around 10 minutes of decision. Split it on paper: the broadcast part becomes a written digest, and the decision part becomes a shorter meeting with a written agenda — or a comment thread with a deadline.

Step 3: Replace broadcast with writing (the actual work)

The failure mode here is treating “async” as “type your standup into a channel where it scrolls away.” Broadcast content needs a home with a routine: a daily or weekly digest that compiles everyone's update into one document, delivered at a predictable time, with blockers pinned at the top. (This is the thing Relay automates, but a disciplined team can run it in any docs tool — we did, for a year, before building it.)

Three rules make written status survive contact with reality:

1. Prompts, not blank pages. “Yesterday / today / blocked” beats “post your update” every time.
2. One compiled artifact. Eight separate messages are a chore to read; one digest is a 90-second scan. Compilation is what makes async cheaper for the reader, and the reader is who meetings were protecting.
3. Blockers get an escalation path. The deepest fear about killing the standup is “what if someone's stuck and nobody notices?” Answer it structurally: a blocker unacknowledged for 24 hours pings the lead automatically. Fear resolved, meeting unnecessary.

Step 4: Cancel with a review date (5 minutes)

Don't delete meetings — suspend them for six weeks with a named review date. Two reasons. Psychologically, people release the safety blanket far more easily when reinstating it is explicitly allowed. And practically, the review forces a real comparison: did the digest surface fewer problems than the meeting did? In our experience, at review time teams reinstate roughly one meeting in five — usually as the decision-only version, in half its old slot.

What the numbers looked like for one real team

Fathom & Frame, a 14-person studio, ran exactly this audit (their full story is here). Inventory: nine recurring meetings, 41 person-hours a month. Classification: two creation (critique, retro), one decision (resourcing), six broadcast. The six broadcast meetings became a daily digest; the resourcing decision moved into the digest's Friday edition with a comment deadline. Six weeks later they reinstated nothing. Their calendar now holds two recurring meetings — and the critique got longer, because status stopped eating its slot.

The honest caveats

• New teams need more sync, not less. Run the audit after the team has worked together for a quarter, not during forming.
• Writing is a skill with a ramp. The first two weeks of written updates will be worse than the meeting was. Budget for that dip instead of declaring failure on day four.
• Some managers hear “fewer meetings” as “less visibility.” The digest is the answer — it's more visibility, written down, searchable — but bring them into the audit rather than presenting its conclusion.

The audit's real product isn't a cleaner calendar. It's the habit of asking every ritual, twice a year, what it's for. Calendars, like codebases, grow until something makes them justify themselves.