There is a specific meeting this post is about. Everyone in it privately thinks it has stopped being useful. Nobody will say so, because saying so means telling the person who set it up that the thing they set up has stopped being useful. So it runs every Thursday, at reduced attendance, and it will run until someone leaves the company.
You can cancel a meeting like that without anyone having to lose the argument. The move is not a better-worded kill. It is to pause it for two weeks and let the absence make the case, which converts a judgement about someone’s work into an observation about what happened.
Below: the question that decides which method you use, the two-week pause and the message that sets it up, the straight cancellation for when a pause is not honest, and what to do in week three when it comes back.
First, which meeting is this
Two different things get called cancelling and they need different messages.
Cancelling one instance is an operational note. It needs a reason and a replacement path, and it is done in a sentence. Most of this post is not about that.
Ending the series is the political one, and it is where people stall. Before you send anything, answer one question: does anyone still need the output, or only the slot?
If nobody can name what the meeting produces, it is a kill. If someone can — a decision that gets made there, a handoff that happens nowhere else — then you are not cancelling, you are converting, and the fix-or-kill procedure sorts which. Cancelling a meeting whose output somebody depends on is how you end up with the same meeting under a new name in five weeks, plus a reputation for breaking things.
Assume for the rest of this post that you asked, and nobody could name the output.
The two-week pause, and why it beats a kill
Announce that the meeting is paused for the next two occurrences, that nothing else changes, and that you will pick it back up if anything breaks.
This works for reasons that have nothing to do with tact.
It asks for a much smaller yes. Ending a meeting requires the organiser to agree their meeting was not worth holding. Pausing it twice requires them to agree to skip two Thursdays. The second request gets approved by people who would have argued with the first.
It produces evidence instead of opinions. After two weeks either something went wrong or nothing did. “Nothing broke” is a fact, and it is the only argument in this whole area that nobody rebuts.
It is reversible, which is what makes it safe to say yes to. The person who agrees is not staking anything, and if the meeting mattered you find out in a fortnight at a cost of two skipped sessions. Do not quietly treat the pause as a kill you are not announcing — say the reversal is real and mean it.
Two weeks is the right length for a weekly. For a fortnightly, pause one occurrence and give it a month. For a monthly, do not pause — a monthly that nobody can defend should be sunset outright, because a paused monthly is just a cancelled monthly with extra steps.
The message that pauses a recurring meeting
Send this to the group, not to the organiser privately. Private is kinder but it puts the whole decision on one person, and the point of the pause is that nobody has to carry it.
Subject: Pausing Thursday sync for two weeks
I’m going to pause the Thursday sync for the next two weeks — no session on the 9th or the 16th.
Nothing has gone wrong. The agenda has been light for a while and I’d rather test whether we still need the slot than keep holding it out of habit. Everything else stays as it is: the project channel is still the place for anything urgent, and I’m around if something needs a conversation.
If anything falls over in those two weeks, we put it straight back and I’ll say so. Otherwise I’ll check in on the 17th and we can decide properly then.
Four things in that message are doing work.
“Nothing has gone wrong.” Without it, half the room reads a pause as a signal that the project is being wound down. Say it plainly in the second line.
A named alternative. “The project channel is still the place for anything urgent” is what stops the pause reading as withdrawal. A pause with no route for the urgent case is how you get four one-off meetings instead.
Named dates, not “for a couple of weeks.” Vague pauses do not come back and do not end; they leave a slot half-alive on nine calendars. Put the dates in and take those instances off the calendar rather than leaving them sitting there greyed out.
A stated moment to decide. “I’ll check in on the 17th” makes this a test rather than a disappearance. Without it you are not pausing, you are ghosting a meeting, and people notice.
If you are not the organiser, the same message goes to the organiser first, as a proposal, and the wording changes at the opening: “Would you be up for pausing the Thursday sync for two weeks? The agenda has been light and I’d rather test it than keep asking people to hold the slot. Happy to send the note and put it back if anything breaks.” Offering to send the note and to own the reversal is what makes it easy to agree to — you are asking for permission, not for work.
Cancelling the series outright
Sometimes a pause is dishonest, and you should not use it as a euphemism. Cancel straight when the thing the meeting existed for has ended — the launch shipped, the migration finished, the team split — because there is nothing to test.
Subject: Ending the billing migration standup
We’re off the old system as of Monday, so I’m ending the daily standup — last one was Friday.
Thanks for six weeks of 9am. Anything still outstanding is in the tracker and has an owner; if you were relying on the standup for something that is not in there, tell me this week and I’ll find it a home.
Name the reason the meeting existed and say that reason has ended. That single move is the difference between a cancellation people accept and one they experience as a loss of access, and it is why putting the reason in the invite body when the meeting is created pays for itself a year later.
Then handle the loss of access explicitly. A standing meeting is often the only reliable contact some people have with a project or a person, and ending it removes that whether you meant to or not — the exit from someone else's standing invite is the individual version of the same problem. The sentence “if you were relying on it for something, tell me this week” costs nothing and catches the person who would otherwise be quietly stranded.
Do not lead with the cost arithmetic. Mention the hours the slot was consuming if someone asks, but opening with it turns a tidy-up into an accusation about other people's time.
When it comes back in week three
It comes back. Usually not as a proposal to reinstate — as an ad-hoc invite, “quick sync on the thing”, same people, same day, half an hour. That is the meeting returning under a different name, and how you handle the first one decides whether the cancellation held.
Three cases, and they are genuinely different.
One real topic, and it needed a conversation. Take the meeting. A cancellation that produces one useful meeting a month instead of four weak ones has worked exactly as intended, and defending it against a legitimate meeting is how you get a reputation for being against meetings.
A second one inside a fortnight, with a light agenda. Now say something, and say it once, in the invite thread rather than in the meeting: “Happy to do this one. If we’re finding we need the slot back, let’s just put the Thursday back rather than booking it ad hoc each week — ad hoc is worse for everyone’s calendar than a standing meeting is.” That is a real offer and you must mean it. Reinstating a meeting you paused is not a defeat; the pause answered the question, and the answer was that the meeting was load-bearing.
Someone books it because they liked the slot. This is the one to hold. Ask, in one line, what the meeting is for — not rhetorically, plainly, in the thread before it happens. A slot booked out of habit does not survive the question, and asking it before the invite is accepted costs the room nothing.
What you do not do is reinstate it silently by attending three ad-hoc versions. The meeting is back at that point and nobody has decided anything, which is worse than either outcome.
When not to cancel a meeting
Three meetings where the fact that nobody defends them is not evidence against them.
The one that is somebody’s only access. An open office hour or a skip-level looks indefensible on any agenda-density test, because most weeks the agenda genuinely is thin. The thin weeks are what make the slot available on the week somebody needs it.
The new one. A meeting set up six weeks ago has not had time to find its shape. Give it the run it was set up for before testing it.
The one you are in but do not own, where the cost is only yours. If the meeting works for the other seven people and is dead time for you, the problem is your attendance, not the meeting — and attendance by role and the downgrade ladder are the smaller moves that solve it without asking anyone to give up their slot. Cancelling a meeting that is working for other people because it is not working for you is a much bigger ask than declining it, and you will be asked to justify it in those terms.