- The true, compounding cost of meetings — beyond the hour on the calendar
- A one-question "real-time test" for whether a meeting deserves to exist
- How to audit your recurring meetings and convert the weak ones
- Async replacements that preserve alignment, plus how to improve the meetings you keep
In an office, a meeting cost a walk to a room. Remotely, it costs a click — so meetings multiplied, because scheduling one became the frictionless default response to any uncertainty. The predictable result is calendars so dense that the actual work has to happen early, late, or in the cracks. Meeting reduction is about restoring the balance: keeping the meetings that genuinely need to be live and moving the rest to channels that serve them better.
The real cost of meetings
A one-hour meeting with eight people isn't one hour — it's eight, plus the hidden costs that rarely get counted:
- The fragmentation tax. A meeting at 11 a.m. doesn't just take an hour; it ruins the two focus blocks on either side, because you can't start deep work knowing an interruption is coming.
- The context-switch cost. Every attendee pays to unload their current task and reload it afterward.
- The default-yes ratchet. Recurring meetings are created easily and cancelled almost never, so they accumulate indefinitely.
The most expensive meetings aren't the long ones — they're the recurring ones no one questions. A weekly hour-long sync with eight people costs over 400 person-hours a year. Almost nothing on your calendar would survive being priced that honestly.
The real-time test
Before any meeting exists or continues, ask one question: does this genuinely require everyone present at the same moment? Real time adds value in specific situations and adds only cost in others.
Auditing your meetings
Run a simple audit on every recurring meeting on the calendar:
- List each recurring meeting, its attendees, and its weekly person-hours.
- Apply the real-time test to each: keep, shrink, or convert.
- For "keep," confirm it has a clear purpose and the right (usually smaller) invite list.
- For "convert," design the async replacement before cancelling, so nothing falls through.
Async replacements that preserve alignment
| Meeting | Async replacement |
|---|---|
| Weekly status sync | Written update posted by a set time; comments for questions |
| Daily standup | Async check-in thread: done / doing / blocked |
| Project kickoff read-out | A brief doc plus a short optional Q&A |
| "Quick sync to align" | A decision doc with the options and a comment deadline |
These lean on the habits in the Async Communication Guide and the documentation-first culture. The written artifact often keeps people better aligned than the meeting did, because it's durable and searchable.
Making the survivors better
Meetings that pass the test still deserve discipline:
- An agenda, or it doesn't happen. No agenda means no clear purpose.
- The smallest necessary invite list. Optional attendees should be genuinely optional.
- Written notes and decisions. Capture outcomes so absent people stay aligned and nothing gets re-decided.
- Cluster them. Group meetings into a window so the rest of the day keeps unbroken focus time.
A worked example
A remote engineering team of twelve had four recurring weekly meetings totaling six hours — 72 person-hours a week. The audit converted the status sync and the standup to async, shrank the planning meeting to the six people who actually needed it, and kept the retro live because it was genuinely interactive.
Weekly meeting load dropped from 72 person-hours to about 20. Alignment didn't fall — the async updates were more thorough than the meetings had been, and searchable later. Most importantly, engineers got back the long focus blocks the fragmented calendar had been destroying.
Common mistakes to avoid
- Cutting without replacing. Delete a meeting and put nothing in its place, and coordination really does suffer. Design the replacement first.
- Keeping meetings out of habit. "We've always had this sync" is not a purpose.
- Oversized invite lists. Ten attendees for a three-person decision wastes seven people's time.
- No written record. Even good meetings leak value if their decisions aren't captured.
- Meetings cost far more than the hour shown — count the fragmentation and person-hours.
- Apply the real-time test: keep live only what genuinely needs everyone present at once.
- Convert status and one-way meetings to async updates, but design the replacement before cancelling.
- Give surviving meetings agendas, small invite lists, written notes, and clustered timing.
Frequently asked questions
How do I know which meetings to cut?
Apply a real-time test to each meeting: does it genuinely need everyone present at the same moment, or is it transmitting information that a document or async update could carry better? Status meetings, one-way updates, and anything where most attendees just listen are the strongest candidates to cut or convert. Meetings for decisions, ambiguity, or relationship-building are more likely to earn their slot.
Won't cutting meetings hurt team alignment?
Only if you cut without replacing. Alignment comes from shared, current information, and a well-run async update often keeps people better aligned than a meeting, because it's written, searchable, and readable on each person's schedule. The failure mode is deleting a meeting and putting nothing in its place; the goal is to move the coordination to a better channel, not remove it.
What should replace a recurring status meeting?
A written async update on a fixed cadence: each person or team posts progress, blockers, and next steps in a shared place by a set time. People read and respond on their own schedule, and the update becomes a searchable record. This preserves the coordination the meeting provided while returning the live hour to focused work.
How many meetings is too many?
There's no universal number, but a useful signal is whether people have enough unbroken time for deep work. If the calendar is so fragmented that focused blocks are impossible, meetings have crossed the line regardless of the count. Protecting at least a couple of uninterrupted hours a day is a more meaningful target than any specific meeting quota.