If you've ever sat in a meeting wondering whether anyone would notice if you quietly climbed out of the nearest window, then Patrick Lencioni's Death by Meeting is probably a book for you.
As a fan of The Five Dysfunctions of a Team, I first read Death by Meeting when it was originally published in 2004. Like many of Lencioni's books, it's written as a business fable rather than a traditional management text, which makes it surprisingly easy to absorb. Rather than hitting you over the head with theory, Lencioni wraps his ideas inside a story that most leaders will recognise immediately.
In fact, I enjoyed it so much at the time that I bought a copy for the CEO I was working with. The downside? He kept the book. The upside? He actually made some changes to the way meetings were run. That probably tells you everything you need to know about the practical value of the book.
The opening premise is wonderfully relatable. A temporary employee, Will Peterson, finds himself observing the executive team of a successful company and is baffled that these undeniably capable leaders can sit through hours of mind-numbing conversations. It's one of those moments where you immediately nod along. We've all been there, right? The people in the room are smart. The business matters. The discussions are important. Yet somehow the meeting feels like watching paint dry.
Lencioni argues that meetings aren't boring because the topics are boring. Meetings are boring because they lack structure, conflict and engagement. Even twenty years later, that's a challenge many organisations still haven't solved.
One aspect of the story I appreciated even more on this re-read was the relationship between CEO Casey McDaniel and the temporary employee, Will.
It's an interesting dynamic.
The CEO feels able to discuss concerns openly with someone who isn't a permanent member of the executive team.
Why?
Because Will is somewhat outside the system. He has no political agenda. No career ambitions within the organisation. No territory to protect. As a coach, that resonated strongly with me.
The value that an external coach often brings isn't that they necessarily have all the answers. It's that they are a neutral party. They can ask questions others can't. They can challenge assumptions without carrying organisational baggage.
Will effectively plays that role throughout the story. He's close enough to understand what's happening but detached enough to see it clearly.
Plot spoiler!
The big idea in the book comes from an unusual observation made by Will. He compares meetings with television and movies.
Now, given the book was written in 2004, some of the examples feel slightly dated today. Back then, people scheduled their viewing around TV programmes. Streaming services didn't exist. Nobody was binge-watching entire seasons in a weekend.
Yet I think there's actually an interesting modern interpretation of Lencioni's argument.
Back then we consumed content at certain times. Today we can consume it whenever we want. Likewise, meetings are no longer contained within boardrooms. We can jump on Teams, Zoom, Slack huddles or WhatsApp calls almost instantly.
The risk?
We can binge meetings just as easily as we binge Netflix (other streaming platforms are available!) We're connected to our colleagues, clients and businesses 24/7.
The original comparison may be dated, but the warning perhaps isn't. Just because we can meet all the time doesn't mean we should.
One observation in particular stood out to me. Think about a film. Within the first ten minutes you usually know whether you're settling in for the journey. Books can be similar. Meetings too.
Too many meetings begin with administrative clutter, unnecessary updates or discussions that should have been an email.
Lencioni argues that engagement starts immediately. The meeting needs tension. It needs relevance. People need to know why they should care.
That's as true in a virtual meeting today as it was in a physical boardroom twenty years ago.
One of my favourite concepts from the book is Lencioni's assertion that meetings need conflict.
Not unhealthy conflict, not personal conflict. Productive conflict. The phrase he uses is to "mine for conflict." I love that. Many leadership teams are simply too polite. People avoid disagreement because they want harmony. But what they often create instead is artificial harmony. Everyone nods. Nobody challenges. Real concerns remain hidden. Decisions lack commitment. The meeting ends feeling pleasant but ultimately unproductive.
Lencioni argues that great meetings have drama because business itself contains drama. Budgets, customers, strategy, competition, growth, risk. These are inherently interesting topics. The facilitator's job is to surface the tension, not suppress it. As someone who spends a lot of time facilitating leadership conversations, I think there's real wisdom in that idea.
Reading the book through a 2026 lens, another thing I noticed was the lack of any explicit discussion around psychological safety. Of course, the term wasn't nearly as widespread when the book was published. Yet I think the concept is hidden beneath much of what Lencioni is advocating. To mine for conflict, people need to feel safe. To challenge decisions, people need trust. To ask difficult questions, people need confidence that disagreement won't lead to punishment. The book doesn't use today's language, but many of the underlying principles point in that direction.
If I had to pick one question from the book to add to my repertoire , it would be:
"What's the real issue here?"
Simple.
Direct.
Powerful.
How many meetings drift endlessly around symptoms while avoiding the actual problem? A conversation about workload becomes a conversation about priorities. A discussion about priorities becomes a discussion about accountability. An accountability conversation becomes a discussion about leadership. Eventually someone asks the question that should have been asked twenty minutes earlier.
What's the real issue here?
It's a coaching question as much as a meeting question. And it's one worth adding to your own repertoire.
The Four Types of Meetings
The practical heart of the book is Lencioni's argument that there is more than one type of meeting. A surprisingly obvious statement that many organisations ignore. Instead, they try to solve every issue in the same meeting format.
Lencioni proposes four distinct meeting types:
1. Daily Check-In – approx. 5 mins every day.
A very short meeting designed to share schedules, activities and immediate priorities.
The objective is coordination.
Not problem solving.
Not strategy.
Just alignment.
2. Weekly Tactical Meeting – approx. 60 mins
Focused on short-term priorities and operational issues.
This is where immediate challenges are discussed and action is agreed.
The emphasis is on execution.
3. Monthly Strategic Meeting – approx. 2 hours
A longer session dedicated to major issues that require debate and deeper thinking.
This is where conflict should be encouraged.
Key decisions are explored rather than rushed.
4. Quarterly Off-Site Review – half day to full day
The longer-term reflection point.
An opportunity to assess the business, revisit strategy and explore bigger themes away from day-to-day pressures.
This brings me neatly to my favourite word in the entire book.
Boondoggle!
I'd never heard the word before.
Lencioni uses "boondoggle" to poke fun at off-site meetings that become little more than expensive get-togethers with very little substance.
In my part of the world we'd probably call them a "jolly” but I think I might add this word to my repertoire too, see what faces people pull. Regardless of the title, you know the type of event he was referring too.
Nice hotel.
Good food.
Some trust falls.
A bit of golf.
Very little actual work.
Now, don't get me wrong.
I absolutely believe there is value in relationship building and getting teams together.
Connection matters.
Trust matters.
Shared experiences matter.
But I prefer these activities to be attached to meaningful work rather than becoming the purpose of the event itself. The best off-sites achieve both. They strengthen relationships while moving something important forward.
One of the strongest messages in the book, which I believe is linked to psychological safety, is that once people became more involved, they started getting more value from meetings.
That sounds obvious.
Yet many organisations attempt to reduce meeting time rather than improve meeting quality.
Lencioni's solution isn't necessarily fewer meetings.
It's better meetings.
More intentional meetings.
Meetings with a clear purpose.
Meetings where everyone understands why they're there.
In some organisations, reducing meetings may indeed be the answer. In others, the answer may actually be more meetings of the right kind.
Of course, this is a business fable. And like many business fables, everything works out rather nicely in the end. The team adopts the approach. The meetings improve. People engage. Results follow.
My real-world experience has been a little messier. Changing meeting habits takes discipline. It takes consistency. It takes someone prepared to hold the line when old behaviours creep back in.
Most importantly, if you're the most senior person in the room, your behaviour sets the tone. Leaders can't delegate meeting culture. They create it.
When the leader arrives late, ignores agendas, cancels strategic discussions or fails to encourage challenge, everyone notices. Likewise, when the leader demonstrates curiosity, encourages debate and protects the structure, the team usually follows. The framework only works when leaders model it.
Has this book stood the test of time? That's the question I kept asking myself while reading. Some examples certainly show their age. The television analogy feels rooted in a different era. The book was written before hybrid work, remote teams and virtual collaboration became everyday realities. Yet surprisingly little of the core message feels outdated.
Whether people gather in a boardroom, on Microsoft Teams or around a conference table, they still crave the same things:
Clarity
Purpose
Engagement
Challenge
Meaningful discussion
The technology has changed. Human nature hasn't.
Would I recommend Death by Meeting?
Absolutely.
It's a quick, digestible read with practical ideas that most leaders can apply immediately.
Would I follow every recommendation to the letter?
Probably not.
I think the best approach is to adapt the principles to fit the realities of your business, culture and working patterns.
What works for a manufacturing firm may not work for a fully remote technology company.
What works for a leadership team may not work for a project team.
But the central message remains powerful:
Meetings are not inherently boring. Poorly designed meetings are.
And if a temporary employee can help a CEO realise that in a business fable, perhaps there's hope for the rest of us too. Not because it's perfect, but because twenty years after publication I'm still talking about it, still quoting it, and still asking one of its best questions:
"What's the real issue here?"