Why nobody cancels meetings
Creating a recurring meeting takes one person and thirty seconds. Removing one feels like it needs consensus, and consensus is never available, so calendars only ever grow.
Underneath that asymmetry sit three specific fears, all social rather than practical.
It implies a judgement about whoever set it up. Cancelling their meeting reads as saying their idea was bad, even when it was good and is simply no longer needed.
Someone might miss the one useful thing it did. Usually true. Most pointless meetings carry one genuinely useful function buried in forty minutes of updates.
Nobody wants to be the person who cut a meeting that turns out to matter. The downside is personal and visible; the upside is diffuse and shared.
The reframe that removes all three
Do not cancel it. Pause it for a month. A pause requires no judgement about anyone, it is trivially reversible, and it answers the question empirically instead of by argument.
Working out which to cut
Twice a year, take every recurring meeting and ask three questions.
| Question | If the answer is bad |
|---|---|
| Has it produced a decision in the last month? | It is a broadcast. Write it instead |
| Would anyone notice if it stopped? | Pause it and find out |
| Could it be half as long, or half as frequent? | Do that before considering cancelling |
Then apply the reductions in order, because each is less disruptive than the next.
Cut the invite list first. This is the highest-value move and the least resisted. Most bad meetings are reasonable meetings with four people who do not need to be there. Telling six people the meeting is now optional for them recovers most of the time at almost no social cost.
Then the length. A sixty-minute slot fills sixty minutes. Thirty produces a tighter meeting with the same output more often than people expect.
Then the frequency. Weekly to fortnightly is usually painless for anything that is not coordinating live work.
Then the meeting. By this point you often find you no longer want to, because the version that remains is fine.
The pause that beats a cancellation
Say it plainly and put a date on it:
"Let's pause this for four weeks and see what we miss. I'll put a reminder in for the 24th to decide whether to bring it back."
Three things make this work. Nobody has to argue the meeting was bad. Anyone who feels strongly knows there is a specific date to raise it. And you get evidence rather than opinions.
Then actually hold the review. A pause that quietly becomes permanent without anyone acknowledging it teaches people that your commitments have soft edges, which costs you the next time you propose something similar.
In practice most paused meetings are not missed. When one is, it is nearly always for a single specific function, which is exactly what you needed to find out.
Replacing what it actually did
This is the step people skip, and skipping it is why a cancelled meeting comes back.
Before you pause anything, work out what the meeting genuinely provides. It is usually one of four things, and each has a written replacement:
Status and progress. Replace with a scheduled written digest. Readable at speed, referenceable later, and it does not interrupt anyone, for the reasons set out in deciding if a meeting should be an email.
A decision point. Do not remove this without a home for it. Move it to an existing slot in your weekly operating rhythm, or set up written approvals with a deadline and a default action.
Unblocking. Frequently the real function. Replace with a named place to raise blockers and a person responsible for reading it, which is the async pattern in running a standup.
Contact between people who rarely speak. Legitimate, and worth naming honestly rather than disguising as a work meeting. A shorter, explicitly social slot serves it better.
When it is not your meeting
You cannot cancel someone else's recurring meeting, and trying is a poor use of your credibility.
Decline it, openly and with a reason. "I do not think I am adding much here, would you send me the notes?" Most organisers are relieved rather than offended, and the first person to do this openly makes it acceptable for everyone else.
Suggest a smaller version rather than a cancellation. "Would it work if I joined monthly rather than weekly?" gives them a face-saving option and usually gets agreed.
Ask what you are expected to contribute. Sometimes the honest answer is nothing, and asking is what surfaces it. Sometimes there is a real reason you are there that nobody had told you.
If it is your manager's meeting, raise the trade-off rather than the meeting. "I am struggling to protect time for the migration; would it be reasonable for me to skip this one for a few weeks?" That framing is covered in how to say no to work without damaging the relationship.
One structural fix worth adopting whatever else you do: cap the number of recurring meetings your team holds, and require that adding one means removing one. Without a cap, every new problem attracts a new weekly slot, and within a year the calendar is the reason nothing gets finished.
Frequently asked questions
- How do you know if a recurring meeting should be cancelled?
- Three questions: has it produced a decision in the last month, would anyone notice if it stopped, and could it be half as long or half as frequent? A meeting that fails all three is a habit rather than a mechanism.
- Is it better to cancel a meeting or shorten it?
- Try cutting the invite list first, then the length, then the frequency, then the meeting. Most bad recurring meetings are fine meetings with four people too many, and losing the meeting entirely loses the one thing it did well.
- How do you cancel a meeting someone else set up?
- Do not cancel it, decline it and say why. "I do not think I add much here, could you send me the notes?" Once one person does that openly, it becomes acceptable for everyone.
- What if people resist cutting a meeting?
- Ask what would be lost, listen, and then replace that specific thing in writing. Resistance is nearly always about one function the meeting performs, not about the hour itself.
- How often should you review recurring meetings?
- Twice a year, as a fixed item. Calendars only ever accumulate, because creating a meeting requires one person's decision and removing one feels like it requires everyone's.