To reduce recurring meetings, review the invites you already have, move routine updates to writing, and pause one low-value series for two cycles. Keep a clear way to escalate real blockers. You can run the whole experiment without adding a “Meeting Efficiency Kickoff.”
In fairness, the kickoff would be easy to schedule. Everyone is already available during the meeting you’re trying to cancel.
Audit what the meeting did last time
Start with the next two weeks of recurring invitations. Ask each organizer to write down what happened the last time their meeting ran. Look for something concrete: a decision, a blocker resolved, a useful conversation, or an update people could have read. The actual outcome tells you more than the title.
- Keep the series if it reliably produces decisions or gives people a useful space for sensitive or complex discussion.
- Shorten or narrow it if only one agenda item needs the whole room. Send the rest as a written update.
- Pause it if the same outcome can happen in a document or there’s no clear outcome at all. Name who handles exceptions.
Replace a status call before removing it
Say where updates go, who writes them, when people should reply, and where to flag a blocker. Removing the event without replacing its job leaves people guessing. They’ll solve that by making smaller meetings.
We’re pausing the Tuesday status call for the next two weeks. By Monday at 3, add what changed, what’s next, and what’s blocked to the project doc. Tag the person who can help. If a blocker needs a decision today, message me and I’ll pull in the people involved.
After two cycles, ask what got slower or fell through. If a real coordination problem emerged, fix that problem: restore a shorter call for the people it affects, or change the written handoff. If nobody missed the meeting and the work still moved, remove the series.

