Death by Meeting

Miles: A software company on the California coast makes a golf video game so realistic that a touring professional credits it, at a press conference, with improving his putting. Orders pour in. A decade on, the company has close to two hundred employees, a founder everyone likes, and modest profits nobody seems troubled by.

Miles: Every week the executives sit down for a staff meeting. In one of them they spend ten minutes on whether to bring the document shredding in house, which would save seventy two dollars a month. The questions about where the company goes next get rushed at the end.

Miles: The first person to say so out loud is a stand-in assistant with a graduate degree in film. The finance chief asks him at lunch what he thought of his first meeting, and he answers in four words. It was really bad.

Miles: Today: Death by Meeting, Patrick Lencioni's fable from two thousand four. In two sentences: meetings fail because the disagreement has been drained out of them, and because every kind of question gets thrown into one pot. The cure is conflict on purpose and four separate meetings for four separate jobs, and Nora's going to argue that redesigning a meeting is the quickest route anyone has to more people in the room being able to contribute.

Miles: Sixty Books. Presented by Stoar Consulting and Coaching.

Miles: Book forty six of Sixty Books, I'm Miles, and this one closes the movement on attention, and who gets to have it. The deal hasn't changed: one management book each time, sixty chosen from the best of the last hundred years, read for leaders and teams whose minds are wired to a different plan, and for a working week that has AI in it now. Nora has the research, and she's scored this author once already.

Miles: Nora, last time we shut the door on the phone and the inbox, and that left the one thing still sitting on everybody's calendar every week. You'd spotted Peopleware's third edition already circling it.

Nora: In a chapter on what DeMarco and Lister call the ultimate management sin, which is wasting people's time, with the status meeting filed right under it. So Lencioni walks into a room where the charges have already been read out.

Miles: And does he plead guilty?

Nora: To the waste, yes. To the usual cure, no. Most people's instinct is fewer meetings. Lencioni prescribes four different kinds of them, and near the end he argues that the feeling of too many meetings is a myth.

Miles: That's a bold thing to put your name to.

Nora: We'll test it before we're done. And it's his second visit. Episode thirteen was The Five Dysfunctions of a Team, and that episode gave these four meetings about four sentences. This time they have the floor.

Miles: Back to the golf company. Who's running it?

Nora: Casey McDaniel. A golf scholarship to the University of Arizona, where he studied engineering and computer science, and a professional career that ended when he developed what golfers call the yips, when the putting stroke stops obeying. So he came home and built a golf game instead, and called the company Yip Software. And the weekly executive meeting is so bad that the executives have a private name for it. They call it the staff infection.

Miles: Which nobody says in front of the founder.

Nora: Nobody says much in front of anyone, and that's the trouble. The real decisions get made afterwards, in corridors. Then a much larger game company buys Yip. Casey agrees on three conditions: he keeps running it, he keeps his team, and he keeps the name.

Miles: And the new owners come to watch.

Nora: One of them does. J.T. Harrison, from the parent company, sits in on a staff meeting, sees what the executives sit through every week, and writes to Casey that he's having doubts about his ability to run the division. Then he says he'll keep attending.

Miles: Where does the assistant come in?

Nora: Casey's assistant is out with a difficult pregnancy, and the son of a family friend fills in. Will Peterson, with some psychology and advertising behind him and a graduate degree in film. And the book gives him something else. As a teenager he was diagnosed with what the book calls a mild disorder, possibly a combination of obsessive compulsive disorder and Tourette's, and shortly before he started the job he'd stopped taking his medication.

Miles: That's a choice, for a business fable.

Nora: It is, and it drives the plot. In his second meeting the team spends close to fifteen minutes on where to hold the company picnic. Will's pen runs dry, and with it the writing he'd been using to keep himself in check, and he tells the whole table what these meetings are costing them.

Miles: And Casey?

Nora: Calls a break, hears him out, and keeps him. Will promises to go back on his medication. Then he does the more useful thing. He tells Casey why the meetings are so bad, and he takes the explanation from the movies.

Miles: The author, briefly, since episode thirteen covered him.

Nora: Briefly. Patrick Lencioni grew up in Bakersfield, California, worked at Bain, Oracle and Sybase, and in nineteen ninety seven was one of the founders of The Table Group, a consulting firm that works with executive teams. The firm puts his books at more than ten million copies across thirteen titles, in more than thirty languages. That's their count, not an audited one.

Miles: And where this one sits in the run.

Nora: His fourth book, and his fourth fable, after The Five Temptations of a CEO, The Four Obsessions of an Extraordinary Executive and The Five Dysfunctions. Jossey-Bass, March of two thousand four, in two parts: the fable first, then a shorter section called The Model. And the fable's five parts carry screenplay names: Flashback, Plot Point, Protagonist, Action, Resolution.

Miles: So the book follows its own advice about the movies.

Nora: Before it's even given the advice.

Miles: The model, in the book's order.

Nora: It opens on a paradox. Meetings are the central activity of leading anything, the book's comparison is the operating room for a surgeon, and almost everybody dreads them. Lencioni's line is that meetings aren't bad by nature. We run them badly, for two reasons.

Miles: The first.

Nora: No drama. And here's Will's comparison. A film runs about as long as a meeting does. When Harry Met Sally is ninety six minutes. The director's cut of Cinema Paradiso is a hundred and seventy, and people sit through it by choice.

Miles: Nobody's ever been asked to sit through Cinema Paradiso with a quarterly forecast on the second screen.

Nora: No, and his point runs the other way. A meeting ought to beat the film. It's interactive, and what gets decided there changes your working life. What it's missing is conflict.

Miles: So he wants more fighting.

Nora: About ideas, and on purpose, in three moves. The hook: in the first ten minutes the leader makes plain what's at stake, a competitor, a customer, people's jobs, so the room knows why it's there. Mining for conflict: the leader goes looking for disagreements people are sitting on and keeps them talking until it's all out, even if that costs some goodwill for an afternoon. And real-time permission: the first time two people start to clash, the leader stops them, briefly, to say this is exactly what the meeting is for.

Miles: And the second reason.

Nora: No contextual structure. He calls it meeting stew. Strategy, a vacation policy, last month's numbers and the picnic all go into one weekly pot, people arrive wanting different things from it, and nothing gets settled. Will's version is a television channel trying to run the news, a sitcom, a feature film and a miniseries in a single slot.

Miles: And the four meetings come out of that.

Nora: Episode thirteen gave them a sentence each, so here's the detail. The daily check-in: about five minutes, standing, purely administrative, what's everybody doing today.

Miles: Then the weekly.

Nora: The weekly tactical, forty five to ninety minutes, in three steps. A lightning round, where everyone gives their two or three priorities for the week in about a minute apiece. A progress review of four to six key measures, kept to around five minutes. And then the agenda, which isn't written in advance. It's set in the room, from whatever the first two steps turned up.

Miles: No agenda going in.

Nora: None. Hold onto that, because it comes back twice. Anything long range gets pushed out of the tactical altogether, which is the rule episode thirteen leaned on.

Miles: Then the monthly.

Nora: The monthly strategic. Two to four hours on one or two big questions, at least two hours a question, with the research done beforehand and real debate expected. If something strategic can't wait a month, you call an ad hoc strategic meeting rather than let it ambush the tactical.

Miles: Huh.

Nora: Last, the quarterly off-site review. One or two days, out of the office but nowhere lavish, on four things: the strategy, the team itself, the people across departments who are excelling or struggling, and the competition and the industry.

Miles: That's four standing meetings. People will say it's too many.

Nora: And the model's closing pages answer that by calling it a myth. The case rests on what it calls sneaker time: the emails, voicemails and corridor visits people spend afterwards sorting out what the meeting should have settled. A team of seven has twenty one pairs who can go back and forth. That time is scattered through the week, so nobody adds it up, and the meetings look like the whole cost.

Miles: Better meetings, not fewer.

Nora: Yeah. Better meetings, not fewer, is where the book lands, and it's the claim I most wanted to check.

Miles: Then check it. Start with the format.

Nora: A fable is evidence of one kind only. It's a worked example where the author writes the company, the problem and the ending, so it can show how an idea might play out, but not that it does. Casey's turnaround is a scene, not a result, and the model that follows presents no study of its own. What I can do here that the pyramid in episode thirteen didn't allow is lay each piece beside research that reached meetings from another direction.

Miles: Has anyone tested the four meetings as a set?

Nora: Not that I could find, so piece by piece. First, the big numbers you'll hear quoted about meetings. Mroz, Allen, Verhoeven and Shuffler reviewed the field in Current Directions in Psychological Science in twenty eighteen. The figure they repeat, eleven to fifty five million meetings a day in the United States, traces in their own reference list to an industry white paper from nineteen ninety eight and a company blog post from twenty fifteen.

Miles: So the famous counts are guesses.

Nora: Estimates, with a long afterlife. The peer reviewed work is smaller and more useful. Steven Rogelberg and colleagues, Journal of Applied Psychology, twenty oh six. Two internet surveys of full time workers, mostly in the United States, the rest in Britain and Australia: six hundred and seventy six describing a typical week, three hundred and four describing that day. How effective people rated their meetings tracked their job satisfaction and their enthusiasm closely, about a fifth of the variation in each.

Miles: And the sheer amount of meeting time?

Nora: That's where the myth section gets complicated. Whether more meetings went with worse outcomes depended on the person. For people who scored high on wanting to get their own work done, and in the first survey for people whose jobs didn't depend much on colleagues, more meetings went with lower satisfaction. For people low on that drive, or in tightly connected jobs, it ran the other way. Both surveys were snapshots, and the authors note they didn't record what kind of meeting it was.

Miles: So too many is real for some people.

Nora: In those surveys, for some people. Lencioni's right that quality matters most, and too sweeping in calling quantity a myth.

Miles: And the agenda that appears in the room?

Nora: Desmond Leach, with Rogelberg and colleagues, Journal of Business and Psychology, twenty oh nine. Two more internet surveys, nine hundred and fifty eight and two hundred and ninety two people who attend meetings, in the United States, Britain and Australia. In the larger one, having an agenda, written in advance or stated at the start, went with meetings people rated as more effective, and so did starting on time, ending on time and decent facilities. A spoken agenda counted, so the tactical's way of building one in the room isn't ruled out. The data still favour knowing what a meeting's for before it begins.

Miles: And the drama?

Nora: The best evidence on what happens inside a meeting comes from Simone Kauffeld and Nale Lehmann-Willenbrock, Small Group Research, twenty twelve. They videotaped ninety two regular team meetings in twenty midsized industrial companies and coded what people said. Problem solving and action planning went with more satisfied teams, better productivity, and company development rated by the chief executives two and a half years later. Criticizing and complaining did more harm than the constructive talk did good.

Miles: So conflict helps, but not every kind.

Nora: Disagreement about the problem helps. Grievance doesn't. Real-time permission only works if the leader can tell them apart.

Miles: And standing up every morning?

Nora: Allen Bluedorn and colleagues, Journal of Applied Psychology, nineteen ninety nine. A hundred and eleven groups of five students working a decision problem, half standing, half seated. The seated meetings ran about a third longer and reached no better decisions, though the standing groups liked their meetings less. And in the field, Viktoria Stray and colleagues interviewed sixty people in twelve software teams across four countries and watched seventy nine daily stand-ups. People valued them for sharing information and solving problems together, and resented them when they turned into status reports to the manager or ran too long.

Miles: Which is the Peopleware subheading turning up in the field.

Nora: Three years after that edition, from interviews and observation.

Miles: Then give us the tier statement.

Nora: Death by Meeting is practitioner literature, a consultant's fable with a model attached, not peer reviewed research, and its turnaround happens at a company its author invented. Where meeting science can check the pieces, several hold up: short regular check-ins, agendas, the damage grievance does, and the weight of meeting quality. The claim that too many meetings is a myth goes further than the surveys do, and the model as a whole hasn't been tested. None of that is a judgment of Lencioni.

Miles: Our half.

Nora: And it's an argument, so I'll mark it now. Meeting design is the lever with the shortest distance between a change and a person being able to contribute. Change how a Tuesday meeting runs, and the next Tuesday it's different for everyone at the table, without anybody having asked first.

Miles: Why does the asking matter?

Nora: Because of what asking costs. Jade Davies and colleagues, PLOS One, twenty twenty two, an online survey of a hundred and eighty one autistic adults in the United Kingdom. Fifty nine percent had asked for workplace adjustments. Of those, about three in five got them, a quarter were refused, and the rest saw them done badly. And almost a third of the whole sample hadn't asked, but thought an adjustment would have helped. People described the work of spotting the need, finding the fix and making the request as falling on them.

Miles: And a meeting change skips that queue.

Nora: That's the argument. Now look again at the fable, and at who breaks the staff infection. It's the person whose condition, in the story, stops him holding the words back.

Miles: That's an uncomfortable plot.

Nora: It's a device, and a team can't run on it. Nobody should have to be the one who can't stay quiet. What I'd credit is the move the model makes next. It takes the job of saying the hard thing away from whoever happens to blurt it and gives it to the leader. Mining for conflict and real-time permission are a role, written down.

Miles: Then the dull meeting.

Nora: Which the book treats as a failure of drama, and there's a group finding beside it. Sarah Orban and colleagues, Journal of Attention Disorders, twenty twenty five. Eighty eight young adults, average age about nineteen, thirty one of them with ADHD traits, which isn't the same thing as a diagnosis. The group with the traits reported far more proneness to boredom, a very large difference on a self report scale, and attention control and working memory explained only a small slice of it.

Miles: So a flat meeting isn't equally flat for everyone.

Nora: In that sample, staying with it costs some people more. And the hook is cheap. Ten minutes on what's at stake is a design change with no budget line.

Miles: And the agenda nobody sees in advance?

Nora: My one real worry with this model. A weekly meeting whose agenda forms in the room rewards whoever can think aloud fastest about something they heard a minute ago. Keep Lencioni's purpose and add a written channel. Post the lightning round items and the likely topics the afternoon before, and let people put a point in writing before or during the meeting. Philippa Howard and Felicity Sedgewick, in the journal Autism, twenty twenty one, surveyed two hundred and forty five autistic adults on how they prefer to communicate. For work, face to face and written channels both ranked well, and phone calls came last or near it in most settings.

Miles: Cautions.

Nora: Two. The first is that this join is my own. I didn't find a study that changed how meetings ran and measured whether neurodivergent employees contributed more. Davies, Orban and Howard each surveyed something else, and I drew the line through them.

Miles: And the second.

Nora: Drama on purpose can turn into heat aimed at whoever processes slowest. Mining for conflict should come with permission to answer later, in writing, and the standing check-in should let anyone sit. What matters about those five minutes is the five minutes, not the posture.

Miles: Fair enough.

Miles: Sixty seconds, on this show's terms. Death by Meeting says meetings fail because nobody's allowed to disagree and because every kind of question gets thrown into one pot, and that the fix is conflict on purpose plus four meetings with four jobs. So for a leader whose team includes minds wired differently, or for anyone working inside one of those minds, here's Monday. Open your next meeting with the stakes, in plain words, before anything else. Pull the long questions out of the weekly and give them a session of their own, with the reading sent ahead. Keep the daily check-in to five minutes, keep it for the team rather than a report upward, and let people sit. Post the weekly's likely topics the day before, and treat a written point as seriously as a spoken one. And when you go digging for disagreement, let people bring theirs back the next morning. A meeting is the cheapest thing on this shelf to change, and the change reaches everyone in the room at once.

Miles: Now the assistants.

Nora: The standing caution about these tools waits after the closing music, word for word, so I'll send you there and spend this on what a book about meetings asks of them.

Miles: Go on.

Nora: Start with last episode's trial, still a preprint, of an assistant built into office software: email time fell and meeting time didn't budge. So the tools won't shrink the calendar for you. The book's answer was never fewer meetings anyway. It was better ones, and there are four jobs these tools do well around that.

Miles: Which four?

Nora: Sorting the stew: give it the running list of topics and have it suggest which belong in the daily, the weekly, the monthly or the off-site, then argue with its choices. Drafting the hook: hand it the research for a strategic session and ask for three plain sentences on what's at stake. The pre-read: have it boil the background down to a short brief that goes out days ahead, so nobody meets the question for the first time in the room. And the record: have it turn the meeting into decisions, owners and dates, sent out the same day, so the people who think best afterwards have something to answer.

Miles: And what should we watch for?

Nora: A summary that smooths over the disagreement, because the disagreement was the point. Read it for what got decided and for what got argued, and if the arguing has vanished, put it back.

Miles: Give us the line to leave on.

Nora: Lencioni's test for a meeting is whether anyone cares how it ends. A tool can sort the topics, send the reading and write it all down afterwards. Caring how it ends is still the room's job.

Miles: That's Death by Meeting, and with it, the end of our movement on attention, and who gets to have it.

Miles: Next time: Getting to Yes, by Roger Fisher and William Ury, from nineteen eighty one, which opens a new movement on the conversations that decide things. We've given five books to the hours, the door, the inbox and the calendar, and everything left is what gets said in the room.

Nora: And Lencioni just handed us that room, with the hook and the argument already set.

Miles: Nora, you took a book about meetings and made it feel like the good kind. Thanks.

Nora: That was a useful one.

Miles: Till the next book.

Miles: You've been listening to Sixty Books, from Stoar Consulting and Coaching. Logan Williamson is a Licensed Professional Counselor in Texas and Louisiana. What you've heard was one book, examined for the people who lead teams and the people who work in them. It wasn't coaching or counseling, and it passed no verdict on anyone listening.

Nora: The transcript is on the episode page, with a source behind every claim. Book forty seven follows in two days.

Miles: Before the tape stops, two things you should know. Miles and Nora are generated voices. Neither of us is a person, neither holds a license, and nothing here was meant as a word about you. AI helps draft each script, which is then edited and signed off by Logan Williamson, a Licensed Professional Counselor in Texas and Louisiana, at Stoar Consulting and Coaching.

Nora: And one note about the AI segment. The evidence that these tools help neurodivergent people at work is early. There are controlled trials now, but they measure things like conversation skill rather than how a job actually goes, and for work itself most of what exists is individual providers reporting success. So take it as promising and not proven. The tools also get rebuilt every few months, so whatever you set up today is built on something that moves.