Too Many Meetings? Here's the Exact Framework to Fix It

You're not imagining it. You really do have too many meetings.

But here's the part that should genuinely alarm you: Atlassian's 2024 survey of 5,000 workers found that meetings are ineffective for accomplishing their goals 72% of the time. And 77% of meetings result in... scheduling another meeting.

So you have a problem. The question is: what do you actually do about it?

Too many meetings? Why going nuclear doesn't work

The temptation is to go nuclear. Declare meeting bankruptcy. Cancel everything. Start fresh.

This fails for two reasons. First, some meetings genuinely are valuable — 1:1s, critical decision-making sessions, incident response. Nuking everything throws out the good with the bad. Second, the meetings come back. Without a systematic approach, the same cultural forces that created the meeting overload will recreate it within weeks.

The better approach is surgical: identify exactly which meetings are the problem and address each one specifically.

The Meeting Triage Framework

For every recurring meeting on your team's calendar, evaluate it on three dimensions:

1. Value: Is this meeting producing outcomes?

A meeting has value if it consistently leads to decisions made, problems solved, alignment achieved, or relationships strengthened. A meeting lacks value if people leave without clear outcomes, if the same topics get discussed repeatedly without resolution, or if attendees routinely multitask.

2. Cost: How expensive is this meeting?

Cost = attendees × duration × frequency × loaded hourly rate. A weekly 1-hour meeting with 10 people costs roughly $40,000-$50,000 per year for an engineering team. Even a "quick" 15-minute daily standup with 8 people costs over $75,000 annually. (See our meeting cost calculator for the full breakdown.)

High-cost meetings deserve more scrutiny. A $50,000/year meeting better be delivering $50,000 in value.

3. Format: Does this need to be a meeting?

Many "meetings" are actually one-way information broadcasts, status updates, or FYI sessions that don't require real-time interaction. These are prime candidates for async alternatives.

A meeting needs to be synchronous when it requires rapid back-and-forth discussion, when it addresses sensitive interpersonal topics, or when the topic has high ambiguity that benefits from real-time brainstorming. Everything else can likely be async.

The Triage Decision Matrix

Based on these three dimensions, every meeting falls into one of four categories:

High value + needs sync → KEEP. Protect these meetings. Make them better with agendas and clear outcomes, but don't cut them.

High value + doesn't need sync → CONVERT to async. The content is valuable but the format is wrong. Replace with a written update, shared doc, or recorded video.

Low value + needs sync → SHORTEN or reduce frequency. If the meeting does have moments of value but mostly wastes time, cut it from 60 to 30 minutes or from weekly to biweekly.

Low value + doesn't need sync → CANCEL. This meeting shouldn't exist. Kill it. If nobody notices within two weeks, it was already dead.

Applying the framework: a real example

Let's walk through a typical engineering team's calendar:

Daily standup (15 min, 8 people)

• Value: Medium. Useful for surfacing blockers, but often devolves into mini status reports.
• Cost: ~$75,000/year.
• Format: Status updates don't need sync. Blockers sometimes do.
• Decision: Convert to async daily posts in Slack. Keep a weekly 15-minute sync for blockers only.
• Savings: ~$60,000/year in productive time.

Weekly team sync (60 min, 10 people)

• Value: Low. Mostly people reading their updates aloud. Decisions rarely happen.
• Cost: ~$44,000/year.
• Format: One-way information sharing. Doesn't need sync.
• Decision: Convert to async weekly written updates. Cancel the meeting entirely.
• Savings: ~$44,000/year.

Sprint planning (3 hours, 12 people, biweekly)

• Value: High. Real decisions about priorities and scope.
• Cost: ~$80,000/year.
• Format: Needs some sync for discussion, but not 3 hours worth.
• Decision: Shorten to 90 minutes. Move backlog grooming and estimation to async pre-work.
• Savings: ~$40,000/year.

Design review (60 min, 6 people, weekly)

• Value: High. Catches issues early, aligns on architecture.
• Cost: ~$26,000/year.
• Format: Benefits from real-time discussion. Keep sync.
• Decision: Keep. Add agenda 24 hours before so people can prepare.
• Savings: None, but improved quality.

"All hands" engineering meeting (60 min, 25 people, monthly)

• Value: Low-medium. Useful for big announcements, but mostly a recap.
• Cost: ~$25,000/year.
• Format: Mostly one-way. Doesn't need sync.
• Decision: Convert to async written update + recorded video. Keep a quarterly in-person all-hands instead.
• Savings: ~$19,000/year.

The implementation plan

Week 1: Audit

List every recurring meeting for your team. For each one, note: attendees, duration, frequency, and purpose. Calculate the annual cost. A meeting audit template can help you score each meeting systematically instead of relying on gut feeling. If you use Kill One Meeting, this is automated — it pulls from your Google Calendar and starts collecting team ratings immediately.

Week 2: Rate

Have your team anonymously rate each meeting on a 1-5 scale. Collecting anonymous meeting feedback takes the guesswork out of this step. You'll likely see a clear pattern: 2-3 meetings with high ratings that everyone values, and 3-5 meetings with low ratings that everyone tolerates.

Week 3: Act on the worst one

Pick the lowest-rated meeting. Apply the triage framework. Cancel it, convert it, or shorten it. Communicate the change clearly to the team: "We're experimenting with making [meeting name] async for the next two weeks. Here's how updates will work instead."

Week 4: Evaluate and move on

Did alignment suffer? Did something break? In most cases, the answer is no. Now pick the next worst meeting and repeat.

Ongoing: One meeting per month

This is the sustainable pace. Improving one meeting per month means 12 meetings fixed in a year. For a team with 15-20 recurring meetings, that means your entire calendar gets evaluated and improved within 18 months.

Preventing too many meetings from creeping back

Meetings tend to accumulate because creating them is easy and canceling them is socially awkward. Left unchecked, this becomes death by meetings — a state where your calendar controls you instead of the other way around. To prevent the problem from returning, establish a few team norms:

Every recurring meeting gets a review date. When you create a recurring meeting, set a 90-day review. On that date, the team evaluates: is this still needed? Can it be shorter? Fewer attendees?

Default to async. Before scheduling a meeting, ask: "Can this be a Slack message, a shared doc, or an email?" Make async the default and meetings the exception. When you do meet, capture decisions in meeting minutes so people who weren't in the room stay aligned.

Every meeting needs an owner and an agenda. No owner, no agenda, no meeting. This simple rule prevents the "let's just have a quick sync" meetings that nobody prepares for and nobody gets value from.

Track meeting hours as a team metric. Just like you track sprint velocity or deployment frequency, track weekly meeting hours per person. When the number starts creeping up, it's time for another audit.

Start today

You don't need a perfect plan. You need to start.

Open your calendar right now. Look at your recurring meetings. Pick the one that makes you sigh when you see it. That's your first target.

Kill One Meeting was built to make this process systematic. It identifies your worst meetings through team feedback, helps you design the right experiment, and tracks the hours you save. One meeting at a time, every month.

Because the best way to fix "too many meetings" isn't to hate meetings. It's to make every meeting earn its place on the calendar.