A ten-person team ran a daily standup, a weekly ops review, a weekly leadership sync, a biweekly all-hands, and a monthly retro, and still felt like nobody knew what anyone else was working on. Adding meetings hadn't fixed the communication gap, it had buried it under thirty minutes of status updates a day that nobody had time to act on before the next one arrived.
More meetings isn't more communication
Meeting cadence gets added the same way tools do: a coordination gap appears, a recurring meeting gets scheduled to fix it, and it's never removed even after the gap closes or the team changes. Nobody schedules the meeting where an existing one gets cancelled, the same pattern covered in the ops stack audit for tools. A calendar with meetings from three different eras of the company's growth is exactly as common as a tool stack in the same condition, and just as rarely audited.
What a recurring meeting actually has to earn
A decision or a real update that can't wait
If a meeting's content could be a two-line async message read whenever convenient, it doesn't need a synchronous slot. Reserve live time for things that genuinely benefit from real-time back-and-forth: a decision needing input from several people, a nuanced update needing questions answered live.
Every attendee needed, not just invited out of habit
A meeting with eight people where four never speak isn't inclusive, it's expensive. Check attendance against actual participation every few months. Someone who hasn't spoken in the last five instances probably doesn't need the slot.
A cadence that matches how fast the underlying thing actually changes
A weekly review of a metric that moves meaningfully once a month produces four meetings of restating the same number. Match frequency to the real rate of change, not to a default weekly rhythm nobody questioned.
Running an actual audit
List every recurring meeting on the team's calendars with its attendees, cadence, and stated purpose, the same first step as process improvement: map what's actually happening before deciding what to change. For each one, ask who would notice if it stopped for a month. If the honest answer is "nobody," it's a strong candidate to cancel outright, not just shorten. If the answer is a specific decision-maker who genuinely needs it, keep it, but check whether the cadence and attendee list still match that need.
Where async replaces sync without losing anything
Status updates, FYI-style information, and anything that doesn't require live discussion move cleanly to an async written format read on each person's own schedule, freeing the live slot for what actually needs it. This connects directly to the cadence question in the weekly ops review: a written weekly review that people actually read is often more useful than a live meeting where half the room is only half paying attention.
FAQ
How many recurring meetings is too many?
There's no universal number. The real test is whether each meeting has a specific decision or update that genuinely needs synchronous time, with the right attendees, at a cadence matching how fast the underlying thing changes. Any meeting failing that test is a candidate to cut, regardless of total count.
How do you know if a meeting should be cancelled?
Ask who would notice if it stopped for a month. If nobody has a specific answer, it's a strong candidate to cancel outright rather than shorten or reschedule.
Should meeting cadence match the metric it reviews?
Yes. A weekly review of something that meaningfully changes once a month produces repeated meetings restating the same number. Cadence should match the real rate of change, not a default weekly rhythm.
Can status updates move to async communication?
Usually, yes. Anything that doesn't require live back-and-forth, straightforward status updates and FYI information, works fine as a written update read on each person's own schedule, freeing live time for decisions that actually need it.
Why do unnecessary meetings accumulate over time?
Because a meeting gets scheduled to fix a real coordination gap, then never gets cancelled once the gap closes or the team changes, the same pattern that causes unused tools to accumulate in a stack.
How often should meeting cadence be audited?
Every few months is enough for most teams. List every recurring meeting with its attendees, cadence and purpose, and check attendance against actual participation, not just who was originally invited.
Recurring meetings accumulate the same way unused tools do: added to fix a real gap, then never removed once the gap closes. A meeting earns its slot only with a genuine decision or update that needs live discussion, the right attendees, and a cadence matching how fast the underlying thing actually changes. Audit the calendar with the same rigor as a tool stack, and move anything that doesn't need real-time back-and-forth to async instead.
Read next
Calendar feels heavier than the team actually needs?
I help teams audit meeting cadence, ops processes and tool stacks so coordination doesn't cost more than the problem it's solving, see how I work.
Book a Call