Every team says it has too many meetings, and every team keeps having them, because each individual meeting feels justified in the moment. The overload isn't caused by any single bad meeting — it's caused by the absence of a default that says this doesn't need to be one. Fix the default and the calendar clears itself.
Meetings are for the things text can't do
There's a clean line. Meetings are worth their enormous cost — everyone's time, synchronized, at once — only for genuinely interactive work: hashing out a decision with real disagreement, building shared understanding of something ambiguous, the human stuff that needs faces. Everything that's one-directional — status, FYIs, "here's what happened" — is information transfer, and information transfer is what writing is for. A status meeting is a document read aloud slowly to people who could read it faster themselves.
Do the arithmetic once
The reason meetings proliferate is that their cost is invisible to the person scheduling them. A one-hour meeting with eight people is a working day. A weekly one is roughly six working weeks a year. Nobody would approve a six-week project with no defined output, but that is precisely what a standing meeting with no agenda is.
You don't need a formal cost-tracking tool. You need the number said out loud once, in the room, about a specific recurring meeting. It changes the conversation permanently, because after that everyone can see the thing that was previously free.
Convert status meetings to written updates
The single highest-leverage cut is killing the recurring status meeting. Replace it with async written updates where each person posts what moved, what's blocked, and what's next — and where the work already lives. When status is visible on a shared board, half the "update" is just looking at the board, and the meeting was mostly narrating cards out loud. Keep a short weekly sync for the genuinely interactive part, and give everyone back the four other slots.
The transition fails in a predictable way, so plan for it: written updates only work if someone actually reads them and responds. If people post into silence for two weeks, the format dies and the meeting returns with the added conviction that "we tried async and it didn't work." Someone senior has to visibly read and reply for the first month, until the habit is load-bearing.
Make every meeting justify its existence
Institute a small tax: no agenda, no meeting. An agenda isn't bureaucracy — it's the meeting proving it has a job that requires everyone present. Writing "1. Decide X. 2. Resolve disagreement on Y." often reveals that item 1 could've been a message and item 2 is the only reason to gather. Half the meetings die at the agenda-writing step, which is exactly the point.
The stronger version of this is to write the agenda as questions to be answered rather than topics to be discussed. "Pricing" is a topic and will consume whatever time you give it. "Do we launch at £29 or £39?" is a question, and a meeting that answers it can end.
Cut the invite list, not just the meeting
A meeting that genuinely needs to happen usually needs to happen with fewer people. Most invite lists are padded by a reflex to avoid excluding anyone, which is a political instinct rather than a practical one — and its cost is that the meeting gets slower, more performative, and less decisive as it grows.
Two habits help. Mark attendance as optional by default for anyone who is not a decision-maker or a direct contributor to the agenda's questions. And make declining socially safe: if people cannot decline without appearing disengaged, "optional" means nothing. That norm has to be set by whoever is most senior, by visibly declining things.
Guard the maker's calendar shape
Ten meetings scattered one-per-hour destroy a day more thoroughly than ten meetings stacked back-to-back, because the gaps between them are too small to do real work in. When you must meet, cluster them and defend large contiguous blocks of unscheduled time. A meeting-free morning is worth more than the sum of its minutes, because focus has a warm-up cost that fragmentation never lets you pay off.
For teams, the version of this that actually holds is a shared no-meeting block — one morning or one full day a week where nothing may be scheduled. Individual calendar blocking gets overridden; a team-level agreement does not.
Audit the recurring ones quarterly
Recurring meetings are the calendar's plaque — they accrete, outlive their reason, and never get removed because removing them requires someone to actively decide. So decide, on a schedule: once a quarter, cancel every recurring meeting and re-add only the ones someone will fight for. The ones nobody defends were being attended out of habit, and their quiet death is the cheapest productivity win your team will get all year.
Set an end date on new recurring meetings when you create them — six or twelve weeks. Renewal then requires a decision, which is the opposite of the default that created the problem. Most meetings that outlive their purpose do so because nobody ever had to choose to keep them.
What to keep
Cutting too far has its own failure mode, and it is quieter: decisions stop getting made, disagreement goes unresolved rather than being aired, and new team members never develop the informal context that makes written communication legible. The goal is not a zero-meeting team.
Keep the ones where people genuinely talk to each other: the decision meeting with real disagreement in the room, the one-to-one, the retrospective, the session where something ambiguous gets worked out. Those are the meetings that justify the calendar. Everything else is a document waiting to be written.
