Too Many Meetings — Or Just the Wrong Ones?

One of the most common frustrations I hear from leaders across industries is some version of the same sentence: I can't get anything done because I'm always in meetings.

It shows up in coaching sessions, in team conversations, in offhand comments after a long Thursday. And it's real — the meeting load in most organizations has become genuinely unsustainable. Research consistently shows that executives spend upwards of 60% of their time in meetings, and a significant portion of that time is experienced as unproductive, unclear, or simply unnecessary.

But here's what I've come to believe after years of working with leaders on this: the problem usually isn't the number of meetings. It's the lack of discipline around what kind of meeting you're in — and what it's actually for.

Patrick Lencioni addresses this directly in his book Death by Meeting, and it's one of the most useful frameworks I share with clients navigating meeting overload. His argument is simple: bad meetings aren't inevitable. They're a symptom. And the solution isn't fewer meetings — it's the right meetings, run with clarity and intention.

The Real Problem: Mixing Everything Together

Lencioni identifies two core reasons most meetings fail.

The first is that they're boring. There's no tension, no stakes, no reason to be genuinely present. People check out because there's nothing compelling them to stay in.

The second — and this is the one that creates the most damage — is that they lack context and purpose. Most organizations throw everything into one long staff meeting: administrative updates, tactical problem-solving, strategic decisions, and personnel conversations all in the same 90 minutes. The result is a meeting that resolves almost nothing, because the room is constantly shifting gears without anyone acknowledging it.

The fix isn't to eliminate meetings. It's to know exactly what kind of meeting you're convening — and protect it fiercely.

The Four Meeting Types (Lencioni's Framework)

1. The Daily Check-in — 5 to 10 Minutes

This is purely administrative. Its purpose is alignment: what's happening today, any schedule changes, quick logistical updates. Lencioni is specific about how to run it — standing, not sitting, and kept ruthlessly short. Don't cancel it because a few people can't make it. Don't let it drift into problem-solving or strategy.

This meeting's value is in its consistency. It keeps the team coordinated without eating the morning.

What it's for: Schedules, logistics, brief activity updates.

What it's not for: Problem-solving, decisions, strategy.

2. The Tactical Staff Meeting — 45 to 90 Minutes

This is your weekly team meeting, and it's where most organizations go wrong. The instinct is to build a detailed agenda in advance — but Lencioni actually argues against that. Instead, start by having each person briefly share their current priorities and review the team's overall scorecard. Then decide together what deserves discussion time.

This approach keeps the meeting focused on what's actually critical right now, rather than a pre-planned list that may no longer be the most pressing thing. The discipline here is identifying when a topic has grown too big for this container — and postponing it rather than letting it hijack the whole meeting.

What it's for: Near-term priorities, obstacles, tactical problem-solving.

What it's not for: Big strategic questions (save those for below).

3. The Ad Hoc Topical Meeting — 2 to 4 Hours

This is your strategic deep-dive. One or two topics maximum. Enough time to actually think, debate, and reach a real decision. Lencioni calls this the most important indicator of a company's strategic health — and it's also the most skipped.

When strategic conversations get jammed into a tactical staff meeting, they get 20 minutes of surface-level discussion with no resolution. The ad hoc topical protects those conversations by giving them the time and environment they actually require. Come prepared. Expect real disagreement. Reach a conclusion.

What it's for: Big decisions, long-term strategy, complex issues with no easy answer.

What it's not for: Routine updates or tactical troubleshooting.

4. The Quarterly Off-site — 1 to 2 Days

This one is about stepping back entirely — from the building, the inbox, the day-to-day noise — to look at the bigger picture. Team dynamics, strategic direction, talent, culture, competitive landscape. It's developmental in nature, not operational.

Lencioni's keys: actually get out of the office, keep the focus on meaningful work (not forced social activities), and don't over-schedule it. Leave room for real conversation.

What it's for: Team health, strategic recalibration, organizational reflection.

What it's not for: Regular business updates or tactical problem-solving.

Start Here: The Meeting Audit

Before you redesign anything, spend 30 minutes doing a meeting audit. Pull up the last two weeks of your calendar and look at every recurring meeting you attended.

For each one, ask:

• What type of meeting was this supposed to be?

• Was that clear to everyone in the room?

• Did it stay in its lane — or did it drift?

• Was the right outcome achieved?

• Did I need to be there?

That last question is one of the most underused tools leaders have. Not every meeting on your calendar requires your presence. Some can be handled by someone on your team. Some can be reduced to an email. Some can be eliminated entirely. The meeting audit helps you see that clearly — and gives you language to make changes intentionally rather than reactively.

What to Do With What You Find

Meetings that are mixing types: Separate them. A strategic conversation that keeps getting squeezed into a tactical meeting needs its own time and its own container.

Meetings without a clear purpose: Before the next one, send a simple question to the organizer: What's the intended outcome of this meeting? If no one can answer that, the meeting probably isn't ready to happen yet.

Meetings where your presence isn't essential: Consider delegating attendance. This is a development opportunity for someone on your team, and a protection of your most focused time.

Meetings that should be async: Status updates, information sharing, and simple approvals rarely need live time. A shared document or a brief voice note often does the same job in less time.

A Note on 1:1 Meetings

I get asked about this often: Who should set the agenda for a 1:1?

My answer: the team member, not the manager.

When a manager sets the agenda for every 1:1, it shifts the meeting into a check-in or a performance conversation — useful sometimes, but not the full picture. When the team member owns the agenda, the 1:1 becomes something different: a space where they bring what's actually on their mind, the obstacles they're navigating, the decisions they're sitting with, the development questions they want to think through.

This shift does two things. It develops the team member's ownership and self-direction. And it gives the manager a much more accurate view of what's actually happening — because the conversation is driven by what matters to the person doing the work, not by what the manager assumes is relevant.

A simple prompt to get started: at the end of each 1:1, ask your team member to send you three agenda items before the next one. It doesn't have to be formal. It just has to be theirs.

One more practice worth building in: keep a shared notes document for each 1:1 relationship — a single running file, organized by date, where both of you can capture agenda items, key themes, decisions, and follow-through commitments. Update it together during the meeting or immediately after (Ai makes this simple).

This does two things. First, it creates continuity — you can see patterns over time, track what's been recurring, and notice growth or stagnation in a way that a single conversation never shows you. Second, it builds a solid employee record without any extra administrative effort. When it comes time for a performance review, a development conversation, or a difficult discussion, you're not working from memory. The record is already there, built organically from real conversations over time.

Action Items to Take This Week

Do the meeting audit. Block 30 minutes, pull your last two weeks of calendar, and ask the questions above. Just look at what's actually there.

Categorize your recurring meetings. Using Lencioni's four types, label each one. Are they clear? Are they being run as intended?

Identify one meeting to exit. What's on your calendar that doesn't require your direct involvement? Who on your team could attend in your place — and benefit from doing so?

Have the 1:1 agenda conversation. If you manage people and you've been setting the agenda, try handing it to them. Give it two or three sessions before you evaluate whether it's working.

Protect one strategic block. If you don't have a regular container for big-picture strategic thinking — either solo or with your team — put one on the calendar. Tactical urgency will always crowd it out if you don't.

Offering this Reflection

• What percentage of your meeting time last week felt genuinely productive and worth the time?

• Which meetings on your calendar are you attending out of habit rather than necessity?

• Are there strategic conversations that keep getting postponed because there's no protected time for them?

• What does your team experience when they leave your meetings — clarity, or more questions?

• If you could reclaim five hours of meeting time each week, what would you do with it?

The Bigger Picture

Here's something Lencioni says that I think every leader needs to sit with: A leader who hates meetings is a lot like a surgeon who hates operating. Meetings are where leadership actually happens — where direction gets set, problems get solved, and teams either build trust or erode it.

The goal isn't to have fewer meetings. The goal is to have meetings worth being in.

That starts with knowing what kind of conversation you're convening, protecting it from becoming something else, and giving the people in the room a clear reason to be genuinely present.

If your meeting culture feels like something your team is surviving rather than benefiting from, that's worth looking at. It's one of the highest-leverage shifts a leader can make — and it's one of the things I work on directly with clients. Let's have a chat!

Framework reference: Patrick Lencioni, Death by Meeting: A Leadership Fable About Solving the Most Painful Problem in Business (Jossey-Bass, 2004)