Nobody designed your calendar. It accumulated. Each recurring meeting was a reasonable answer to a real problem on the day it was created, each standing report was requested by someone who genuinely needed it, and almost none of them have been looked at since. Adding a weekly meeting takes thirty seconds; removing one apparently requires an act of leadership.
The takeaway up front: every recurring routine exists to answer a question, and routines outlive their questions. The problem gets solved, the person who needed the report leaves, the system now shows the same data live — but the meeting survives, because no one owns the job of stopping things. Maintaining an operating cadence is not about running meetings well. It is about periodically checking which ones are still answering a live question, and retiring the rest without losing the information they carried.
What actually degrades
Operating routines do not fail loudly. They decay in three predictable ways, and each looks different from the inside.
The question dies but the routine continues. A weekly production call was created during a crisis about missed deliveries. Deliveries were fixed eighteen months ago. The call still happens, now filled with updates in search of a purpose.
The routine gets absorbed by a system. Someone built a report by hand because there was no other way to see the numbers. There is now a dashboard. The report continues, and is reconciled against the dashboard, which is worse than either.
The audience changes and nobody re-scopes. A meeting designed for four people who all made decisions now has eleven attendees, most of whom are there to be informed. It has silently converted from a decision forum to a broadcast, and a meeting is an expensive way to broadcast.
The common thread is that none of these are anyone's fault, and none of them will correct themselves. Accumulation is the default state; removal has to be deliberate.
The three tests
For each recurring meeting or report, answer three questions honestly. The wording matters, because vaguer versions let everything pass.
1. What decision does this produce? Not what it covers — what it decides. A routine that produces no decisions is a status broadcast, and status is better distributed in writing that people read at their own speed. If the answer is "it keeps everyone aligned", press harder: aligned on what, and what would go wrong if they weren't?
2. Who acts on the output, and what do they do differently? Name the person and the action. A report that goes to six people, none of whom can point to a decision they made because of it, is being produced for the archive. This is the test standing reports fail most often.
3. Would anyone notice if it stopped for a month? The most useful of the three, because it is testable rather than theoretical. And you should actually test it — see below.
A routine that passes all three is load-bearing. One that fails all three is theatre. Most of what you find sits in between, and the fix is usually to change its shape rather than to kill it: less often, fewer people, shorter, or converted to a written update.
What is usually theatre
Named plainly, because these are the patterns that survive audits by sounding responsible:
- The round-the-table status meeting where each person reports what is already visible in the system everyone can see.
- The report built for someone who has left, still produced monthly by a person who assumes somebody must want it.
- The meeting held to make one senior person feel informed, which taxes eight calendars to serve one.
- The dashboard nobody opens, built with real effort during a push for visibility, now a monument to it.
- The recurring one-to-one that has become a task list read aloud. The slot is valuable; the use of it has drifted.
- The pre-meeting for the meeting, which is a sign the real meeting has the wrong people or no agenda.
What routine genuinely helps
Maintenance is not the same as elimination. A small number of routines earn their recurrence, and they share a property: something changes between occurrences that requires a human judgement.
- A decision forum — a regular slot where things that need deciding get decided, with the people who can decide them in the room. This is usually the one meeting worth defending.
- An exception review — looking at what went wrong, not at what went normally. Normal work does not need a meeting; deviations do.
- A forward-looking commitment check — what is promised in the next period and what could stop it. Different from a status update, because it is about risk, not history.
- Genuine one-to-ones — the routine where the topic is the person, their obstacles, and their development, not their task list.
- A periodic look at the numbers that would change your plan — a small set, reviewed slowly, rather than a large set reviewed fast.
If you are unsure whether a routine belongs here, our operations and process guide covers how these connect to the work they are supposed to be managing.
Running the audit
A half-day exercise you should repeat perhaps twice a year.
- List everything recurring — meetings, standing reports, dashboards, standing agenda items. Pull it from calendars rather than memory; the list is always longer than anyone expects.
- For each, write the question it exists to answer, in one sentence, and name the person who needs that answer. Anything you cannot write a sentence for is your first candidate.
- Apply the three tests and sort into keep, reshape, and stop.
- Pause rather than cancel. Suspend the "stop" pile for thirty days and see what actually breaks. A pause is politically much easier than a cancellation, and the evidence it produces ends the argument.
- Reinstate what genuinely broke, in a smaller form. Something that only needed to be monthly comes back monthly.
The trade-off nobody mentions: cancelling a meeting does not remove the need for the information it carried. It relocates it — usually into ad-hoc messages and interruptions, which are less efficient than the meeting was, and harder to see. So for every routine you stop, name where that information now lives: a written update, a dashboard, a shared document, an escalation path. Delete the container, keep the contents. Where the answer is "somebody just needs to own this call," that is a delegation question rather than a calendar one, and our guide to delegating without losing control of quality covers making that handover properly.
Keeping it from growing back
The audit is worthless if the calendar refills, and it will unless you change how things get added.
- Put a sunset date on every new recurring item. Ninety days, then it must be renewed by name. Defaults should expire; anything genuinely valuable will survive a renewal conversation.
- Require a stated question and an owner before anything recurring is created. Two sentences, not a proposal.
- Make the default shorter and smaller. Half the length and half the attendees is the right starting point, and both can be increased on evidence.
- Give someone the job of removal. Nobody is currently accountable for what should stop, which is the whole reason accumulation wins. When routines are the way work gets done rather than reported, write them down properly instead — our guide to writing SOPs people actually follow is the better home for that.
This is the same discipline as choosing what not to do at a strategic level, applied to the operating layer — covered in our guide to deciding what not to do.
FAQ
How many recurring meetings should a small company have? There is no correct number, because it depends on how much genuinely changes between occurrences and how many decisions your work requires. The better test is proportional: if managing the work consumes more attention than doing it, the cadence is too heavy regardless of the count.
What if people say they like the meeting? Liking it is real information — it often means the meeting is serving a social or reassurance function the rest of the week does not provide. Take that seriously, then meet the need directly rather than through a weekly hour that also has to pretend to be about work.
Isn't cancelling meetings just a way to avoid communication? It is if you only delete. That is why every stopped routine needs a named replacement home for its information. The goal is not less communication; it is communication that does not require eight people to be in the same place at the same time to happen.
Who should run the audit? Whoever owns operations, with the owner or general manager visibly backing it — the sponsorship matters more than the analysis, because most of the resistance is political rather than practical. In a very small company, do it together in one sitting.
How do I handle a routine a client or investor requires? Keep it, and stop applying the tests to it. Some reporting exists to satisfy an external obligation rather than an internal decision, which is a legitimate reason on its own. Just be honest about which category it is in, so it is not defended internally as something it is not.
Where to start
Open your calendar, list every recurring commitment, and write the question each one exists to answer. The ones where nobody can name a live question are your answer, and a thirty-day pause will prove it without a confrontation. Then name where the information goes before you switch anything off. For more practical operations and management guidance, visit Consulting Firm USA.
