Who this guide is for
Teams and managers auditing recurring meetings that may be wasting time or growing stale.
Use this guide when
Recurring meetings become expensive because they are easy to ignore and hard to question once they are established. This guide is for people who suspect their calendar is full of default meetings that no longer justify the interruption they create.
The Recurring Meeting Problem
Recurring meetings are like subscriptions—they accumulate until your calendar is full of commitments that no longer serve you.
The average professional has 8-12 recurring meetings per week. How many are truly necessary?
The Quarterly Meeting Audit
Every quarter, review each recurring meeting:
Ask These Questions
- •What's the purpose? Can you articulate it?
- •What would happen if we stopped? Anything?
- •Does everyone need to attend? Or could it be smaller?
- •Is the frequency right? Weekly might be too often
- •Is the duration right? Could it be shorter?
Decision Matrix
| Action | When to Use | |--------|-------------| | Keep as-is | If it's working and necessary | | Reduce frequency | Weekly → biweekly, biweekly → monthly | | Shorten | 60 min → 30 min, 30 min → 15 min | | Make async | Replace with Slack update or doc | | Kill | If nobody would miss it |
Common Meetings to Cut
Status Update Meetings
Replace with async written updates. Use meetings for discussion, not information transfer.
"Just in Case" Meetings
Meetings held even when there's nothing to discuss. Make them conditional.
Too-Large Meetings
Every person added reduces effectiveness. Split into smaller groups.
Historical Meetings
Created for a reason that no longer exists.
How to Kill a Meeting
- •Propose an experiment: "Let's try canceling for a month"
- •Offer alternatives: "I'll send a weekly update instead"
- •Start small: Reduce frequency before eliminating
- •Get allies: Others probably want this too
Protecting the Meetings That Matter
Not all meetings are bad. Protect:
- •1:1s with direct reports
- •Strategic planning sessions
- •Team retrospectives
- •Cross-functional coordination (when needed)
The Meeting-Free Default
Flip the script: Instead of meetings being the default, make async the default. Only meet when synchronous communication adds clear value.
Action Step
This week, pick one recurring meeting. Ask: "What would happen if this disappeared?" Act on the answer.
Before you act on this advice
- Review the purpose, frequency, attendees, and recent outcomes of each recurring meeting.
- Test smaller changes first, such as shorter duration or lower frequency.
- Replace information-sharing meetings with async updates whenever possible.
Common traps to avoid
- Teams often keep meetings because canceling them feels socially harder than admitting they no longer help.
- A quarterly audit fails if nobody is empowered to change scope, frequency, or attendance.
- Killing a meeting without offering a replacement communication path can create confusion instead of clarity.
Best next step
Pick one recurring meeting this week and run a real audit on it. A single successful cleanup usually gives the team confidence to question the rest of the calendar too.
Why you can trust this page
Productivity pieces focus on scheduling as an operational habit: protecting calendar time, reducing coordination overhead, and making recurring planning easier to repeat.
Public guides on WhenWorks are tied to the product and support context behind the site. We explain our editorial process publicly so readers can judge whether the page feels complete and trustworthy for their use case.
Want the policy context behind this article? Review our editorial standards or contact the team.
Questions people usually ask
What is the easiest way to improve a bad recurring meeting?
Reduce either the frequency or the attendee list first. Those two changes are often easier to test than full cancellation and still reveal whether the meeting creates enough value to keep.
How do I suggest canceling a meeting without sounding difficult?
Frame it as an experiment tied to a better outcome, such as more focus time or clearer async updates. People respond better when the proposal sounds constructive instead of purely negative.
