Why Meeting Load Creeps Back Up After Every Cleanup

A one-time cleanup removes existing meetings but does nothing about how new meetings get created going forward. Without a standing rule governing when a new recurring meeting is allowed to start, the same default habits that created the original clutter, scheduling a meeting because it's easier than deciding whether one is actually needed, regenerate it within a couple of quarters.

Think of the purge as treating the symptom, like draining a bathtub without turning off the tap. The relief is real and immediate, but it's temporary by design unless something also addresses the ongoing inflow of new meetings that never stops on its own.

Most new recurring meetings get added by managers who are new to a role and default to weekly syncs as a way to feel in control of their team's work. This is an understandable instinct, but it's rarely questioned, and each new manager who joins adds their own new standing meeting on top of whatever already exists, without removing anything in exchange.

This pattern compounds specifically as a company grows, because growth means more new managers being promoted or hired in a given year, each independently reaching for the same default. A flat headcount company doesn't see this effect nearly as strongly, which is part of why meeting creep tracks so closely with growth stage.

Require that any new recurring meeting request come with a stated purpose and a review date, thirty or sixty days out, where the meeting's continued existence gets actively reconfirmed rather than defaulting to continue. Pair this with a norm that a new standing meeting means an existing one on the same calendar gets reviewed for whether it's still earning its slot. This keeps total meeting load roughly flat as the org grows, instead of purely additive.

The reconfirmation step matters more than it sounds like it should. A meeting that simply continues by default survives indefinitely because canceling it takes an active decision nobody wants to be the one to make; a meeting that expires by default unless someone actively renews it flips that inertia in the other direction.

Set these conditions for every new recurring meeting:

• A stated purpose written into the invitation, so the meeting has a reason beyond being the default way to stay informed.
• A review date thirty or sixty days out, where the meeting must be actively renewed or it expires.
• A check of one existing meeting on the same calendar, to see whether it still earns its slot.
• A written async update template offered as a real alternative, so the underlying need for visibility is actually met.

Banning weekly syncs without giving new managers another way to stay informed just creates anxiety that resurfaces as an even less efficient meeting later. Pair any reduction effort with a genuine async alternative, a written weekly update template, so the underlying need for visibility is actually met rather than just suppressed.

Managers who trust the async update tend to stop scheduling redundant live syncs on their own, without needing to be told to. Managers who don't trust it will find a reason to add a meeting back regardless of what the policy says, so building that trust is worth more effort than writing the rule itself.

Rather than a one-time audit, track total scheduled meeting hours per person as a standing number leadership reviews quarterly, the same way you'd watch any other operational metric that tends to creep. A gradual increase over two consecutive quarters is worth a real look before it becomes the kind of overload that needs another disruptive purge to fix.

This single number, tracked consistently, is a far better early warning than waiting for people to start complaining about their calendars, since complaints tend to surface only once the load has already become genuinely painful rather than merely trending in the wrong direction.

For example, a leadership team can add total scheduled meeting hours per person to the same quarterly review as its other operating numbers. When the figure rises for two consecutive quarters, the next step is to look at which new recurring meetings were added and whether their review dates were honored, rather than launching another purge. A common mistake is reviewing only the company-wide total. Break it down by team as well, since one department adding standing syncs can hide inside a flat overall number. Share the trend with managers so they see the effect of their own calendars, and ask each to retire one meeting when their team's figure climbs.