How to Run an Effective Meeting

Drucker's Uncomfortable Truth About Meetings

Peter Drucker wrote what remains the most honest thing anyone has said about meetings: "Meetings are by definition a concession to deficient organization. For one either meets or one works. One cannot do both at the same time."

Drucker identified four organizational time wasters that generate excessive meetings. Two are particularly relevant: malorganization (excessive meetings are a symptom of structural problems, meaning people can't get clarity any other way) and malfunction in information (people meet because they don't have access to what they need without asking someone).

The implication is uncomfortable: some meetings shouldn't be made more efficient. They should be eliminated, and the organizational failure they compensate for should be fixed instead. If your team holds a weekly update meeting because people otherwise don't know what others are working on, the solution is a shared project management system, not a shorter update meeting.

Lencioni's Four Meeting Types: The Framework Most Organizations Ignore

Patrick Lencioni's Death by Meeting argues that most organizations don't have too many meetings. They have too many structurally confused meetings. When strategic topics get jammed into tactical meetings and administrative updates get jammed into decision meetings, every meeting becomes shapeless and nothing gets resolved.

Lencioni's solution is not fewer meetings. It's four distinct meeting types, each with its own purpose, duration, and rules:

The Bezos Running Rules

Jeff Bezos banned PowerPoint at Amazon and replaced it with a requirement for written six-page narrative memos. At the start of every substantive meeting, attendees read the memo silently for 30 minutes. Discussion begins only after everyone has read.

The rationale is structural: "You can hide a lot of sloppy thinking behind bullet points." A bullet point can assert without supporting. A sentence must connect to a following sentence. Narrative structure forces the author to reason, and forces the reader to evaluate that reasoning rather than fill in gaps with their own assumptions.

Bezos also introduced the two-pizza rule for meeting size: if a meeting requires more food than two pizzas to feed, it has too many people. Beyond five to eight attendees, meetings transform from decision-making sessions into performances. People speak to appear informed rather than to resolve the question at hand. The fix: remove one person at a time until the meeting would break. The last person you couldn't remove is the minimum viable attendee list.

Grove's Preparation Principle

Andy Grove identified arriving unprepared to a meeting as a high-leverage negative act. It wastes every attendee's time while simultaneously depriving them of whatever they would have done instead. Grove called this negative leverage: one person's failure producing costs multiplied across everyone in the room.

The preparation standard Grove applied: every meeting should have a defined purpose, an agenda, an expected output, and a pre-read if necessary. Not as bureaucracy, but as respect for everyone's time and alternative uses of it.

Apply Grove's pruning test to every meeting invite you send: "What would happen if the people I am inviting did not attend this meeting at all?" If the honest answer is "they would be informed by email," send the email. If the answer is "they would miss a decision they need to make," you have a real meeting.

Mining for Conflict: The Facilitator's Most Important Skill

Lencioni's most counterintuitive insight: most meetings fail not because they have too much conflict but because they have too little. People hold back to avoid awkwardness, keep the peace, or protect relationships. The real conversation happens in the hallway afterward.

The facilitator's job in a monthly strategic meeting is to surface the hallway conversation inside the meeting room. Lencioni's technique, "mining for conflict," requires asking directly: "What is the one thing we are not saying that we should be saying?"

This question does two things simultaneously: it names the pattern (something is being withheld) and it creates explicit permission to say it. Most people know what the unspoken thing is. They're waiting for someone to open the door. The facilitator opens the door.

Step-by-Step: Run a Meeting That People Actually Value

What to Do With Recurring Meetings

Jim Collins, in Good to Great, introduced the stop-doing list as a discipline equal in importance to the to-do list. The principle applies directly to your recurring meetings. Every quarter, apply Collins's question to each recurring meeting on your calendar: "If we were starting from scratch today, would we schedule this meeting?"

Then apply Grove's pruning test: "What would happen if this meeting didn't exist?" If the answer is "we would email the status update," cancel the meeting and send the email. If the answer is "we would lose the only structured forum for this team to make decisions together," keep it, but redesign it using Lencioni's types.

Collins also noted that good is the enemy of great. Every "good enough" recurring meeting crowds out the time and attention that a genuinely important meeting needs. The quarterly calendar audit is the mechanism that keeps the good from accumulating at the expense of the great.

How alfred_ Supports Meeting Effectiveness

The administrative overhead around meetings (scheduling, follow-up emails, action item tracking) is one of the most significant costs of meeting culture. alfred_ handles the before and after so you can focus on the during.

Before meetings, alfred_'s Daily Brief surfaces any relevant email threads, outstanding action items from prior meetings, or context you need to prepare. After meetings, alfred_ drafts the follow-up email with key points and action items. This is the critical step that most professionals skip because something else pulls their attention before they send it.