Why Your Meetings Are Broken (And Why the Laws of Human Nature Predicted It)

Every organization I've ever walked into has the same meeting problem. Not too few meetings, but too many of the wrong kind.

Let me give you nine laws that explain your calendar and a case for rethinking where decisions actually belong.

Sayre's Law: The passion of the argument is inversely proportional to the stakes

Wallace Sayre, a political scientist at Columbia University, observed that, "in any dispute the intensity of feeling is inversely proportional to the value of the issues at stake."

Sound familiar? Think about the last meeting where someone went to the mat over the color of a slide template, the formatting of an infographic, or whether the break room coffee should be regular or bold roast. Now think about the last time anyone argued with that same ferocity over a capital expenditure decision or a make-or-break process change.

The difference isn't passion, it’s stakes. When something is too large or too complex for most people in the room to feel confident about, they go quiet. When it's small enough that everyone has an opinion, those opinions multiply into a thirty-minute argument. Sayre's Law is the reason your leadership team once spent half an hour debating the font on a quarterly report and approved a $200,000 equipment purchase in under two minutes.

Benford's Law of Controversy: Passion is inversely proportional to the amount of real information available

This folk wisdom observation, attributed to science fiction author and physicist Gregory Benford, is Sayre's close cousin, and the one that plays out most visibly in project meetings. Where Sayre is about the size of the stakes, Benford is about the quality of the information. When people have hard data in front of them, debate compresses. There's a right answer, or at least a defensible one.

But when the data is thin, or worse, when everyone feels like they know something without actually knowing it, the meeting expands to fill the uncertainty. Opinions substitute for facts. Volume substitutes for analysis. The most confident voice in the room often wins, which is not the same as the best-informed voice winning.

The antidote is preemptive. Bring the data. Force everyone to do their homework. Distribute information before the meeting, not during.

Information, if distributed where it's needed in a timely fashion and consumed, will absolutely shorten meetings and improve decision quality.

Parkinson's Law of Meetings: Time spent on an item is inversely proportional to its value

C. Northcote Parkinson was a British naval historian who published what became one of the most quoted observations in management: work expands so as to fill the time available for its completion. His meetings-specific corollary is equally sharp.To a certain degree, the time spent on an agenda item is inversely proportional to its value.

His classic illustration: a committee reviews two agenda items: a proposed parking lot and a plan to power the facility with wind energy. Everyone in the room knows something about a parking lot, (design, cost, location), so the discussion drags on. But when the wind energy proposal surfaces, almost no one has the technical background to engage, so it passes quickly. The item with the highest strategic value gets the least scrutiny.

The implication for meeting design is direct: if you schedule an hour, you will use the hour. The solution isn't discipline, it’s constraint. Shorten your meeting blocks by design, and the work will compress to fit.

Diffusion of Responsibility: The more people in the room, the less each one owns the outcome

This is the accountability killer that no one talks about openly. Social psychologists John Darley and Bibb Latané demonstrated the effect in a landmark 1968 experiment: when subjects believed they were the only one who heard a distress call, 85% helped. When they thought one other person also heard it, that dropped to 62%. When they believed four others heard it, only 31% took action.

This is among the most replicated findings in social psychology and it translates directly to your conference room. A room with twelve people and no named owner produces twelve people who each assume someone else will follow through. The fix is simple and non-negotiable: every decision that comes out of a meeting must have one name attached to it. Not "the team." One person. And that person should be identified before the meeting closes, not in a follow-up email that nobody reads.

The Decision Problem

Now we need to talk about something most organizations won't admit.

Many leadership teams convene daily, sometimes multiple times, to make the day's decisions as a group. It feels collaborative. It feels inclusive. It feels like alignment.

What it actually is, according to decades of behavioral science, is one of the worst possible environments in which to make decisions. The laws above already stack against you. The four below explain why group decision-making is specifically and systematically corrupted, not by bad intentions, but by the predictable dynamics of how human beings behave when they're in a room together.

Hick's Law: More options mean longer decisions - and worse ones

Psychologists William Hick and Ray Hyman established in 1952 that the time it takes for a person to make a decision increases logarithmically with the number of available choices. Every option added to a meeting discussion extends the time to resolution and depletes the cognitive capacity of everyone in the room. This is why the, "let's brainstorm all the possibilities" opening move, so common in collaborative meetings, is the enemy of good decisions. You generate participation, but you also generate cognitive overload, and the decision that emerges from an exhausted group is rarely the best one available.

Fredkin's Paradox: The decisions that take longest matter least

Physicist and philosopher Edward Fredkin identified something that will ring uncomfortably true for anyone who has sat through a lengthy meeting: the more equally attractive two alternatives seem, the harder it can be to choose between them - no matter that, to the same degree, the choice can only matter less.

The more similar two options are, the more difficult it is to decide between them and the less consequential the decision becomes. In a group setting, this paradox is amplified. When two options are genuinely close in value, the group will debate endlessly, not because the decision matters, but because the similarity of the options makes it feel unresolved. Meanwhile, the truly asymmetric decisions, the ones where one option is clearly superior but requires courage to choose, get either rubber-stamped or avoided entirely. The meeting optimizes for the wrong things.

The Paradox of Choice: More options produce worse outcomes, even after you decide

Barry Schwartz documented in his 2004 research that the explosion of available choices doesn't improve decision quality, it undermines it. When groups generate and debate multiple options, members leave less satisfied with the outcome regardless of what was decided because they're haunted by the roads not taken.

This matters operationally. Decisions made in option-rich group settings produce less committed implementation, because people are still second-guessing the choice while they're supposed to be executing it. Doubt sown in the meeting room becomes drag on the shop floor.

The Abilene Paradox: The group decides what nobody wanted

Management professor Jerry Harvey named this in 1974 after a miserable family car trip to Abilene, Texas that nobody had actually wanted to take but that everyone agreed to because each person assumed the others were enthusiastic. They drove 53 miles in 104-degree heat, ate bad cafeteria food, and drove home to discover that not one person in the car had wanted to go.

It happens in your decision meetings constantly. Someone floats an idea. A few people nod along to avoid being the one who kills the momentum. Others stay quiet because they assume the nodders represent the room. Before anyone has formally committed, the group has "decided" and marched off in a direction nobody would have chosen individually.

It's important to distinguish the Abilene Paradox from groupthink, because they are often confused and they require different fixes. In groupthink, people actually convince themselves the consensus is right, judgment is corrupted from the inside. In the Abilene Paradox, nobody believes the idea is good, but nobody says so, communication breaks down in the presence of assumed agreement. Groupthink is a problem of flawed reasoning. The Abilene Paradox is a problem of suppressed honesty. You can't solve the second one by improving the quality of analysis. You solve it by making dissent structurally required.

As Harvey later wrote, the inability to manage agreement is, "the single most pressing issue of modern organizations." Before any group decision closes, ask explicitly: "Is there anyone in the room who has a concern they haven't voiced?" Then wait. The silence after that question is often the most important moment in a meeting.

Ashby's Law of Requisite Variety: Why the room is working against you — and what to do about it

Cybernetician W. Ross Ashby formulated one of the most important and least-cited laws in organizational management: only variety can absorb variety. A control system — whether a thermostat, a military command structure, or a leadership team — must possess at least as much complexity as the environment it is trying to regulate. If it doesn't, it will be overwhelmed by a problem space larger than its own response capacity.

Here is where the daily decision meeting reveals its deepest flaw.

Leaders bring decisions to group meetings with a sincere belief that they are increasing the variety of the decision-making apparatus. More minds, more perspectives, more responses available. Surely the group is more capable than any individual. In theory, Ashby would agree. A group should have higher requisite variety than a single person.

But look at everything we've just catalogued. Diffusion of responsibility narrows the range of people willing to act on what they know. The Abilene Paradox suppresses honest dissent, people who privately disagree stay silent, so the group's output converges on false consensus rather than reflecting the actual range of views in the room. Hick's Law and Fredkin's Paradox cause the group to burn its energy on low-consequence decisions while high-stakes ones slip through on momentum. Benford's Law ensures the loudest voices fill the gaps left by missing data. Sayre's Law guarantees the trivial consumes the time that should go to the consequential. Parkinson's Law ensures the clock runs out before the important work is done.

Every one of these dynamics is a variety reducer on the organization's decision-making capability. The group that was supposed to increase decision-making capacity has instead compressed it. The meeting room, packed with leaders who each carry genuine expertise, functions at a fraction of its theoretical capacity because the social environment has crushed its effective variety down to whatever the most dominant voice, the path of least resistance, or the clock will allow.

Ashby's Law tells us this is not a morale problem or a culture problem. It is a structural problem. And it has a structural solution.

Distribute decisions to where the variety actually lives — and build the system that makes those decisions good.

The answer is not to pack more people into a room. That experiment has already failed, for all the reasons catalogued above. The answer is to distribute decision authority across the organization, anchored to the roles that have the clearest, most direct access to the information that drives each decision.

This does two things simultaneously. It expands the total variety of the organization's decision-making apparatus. More of the organization's relevant knowledge is engaged at the point where it is sharpest and most current. And it reduces the complexity burden on any individual decision-maker. Each person is responsible for a bounded, well-defined problem space that matches their role, their visibility, and their information. Neither overwhelmed nor underutilized. That is requisite variety working as designed.

But distribution alone is not enough. Handing authority to the person closest to the problem without equipping them to use it well just relocates the dysfunction. This is where leadership's real work lies, not in attending every decision, but in building the system that makes distributed decisions fast, consistent, and sound.

That system has two components.

The first is a well-designed Standard Operating Procedure (SOP). If the organization has identified, vetted, and documented the legitimate responses to a given condition ranked by situation and then assigned them to the role best positioned to see it, the decision-maker at the point of impact doesn't face an open-ended choice problem.

The SOP directly counters Hick's Law by limiting the option set to what has already been determined to be appropriate. It counters Fredkin's Paradox by eliminating the near-equivalent alternatives that generate endless deliberation - the organization has already done that cognitive work, upstream, without the pressure of the moment. And it counters the Paradox of Choice by removing the doubt that follows option-rich decisions, replacing it with the confidence of a protocol built by people with full information and no time pressure.

The second component is information flow. A decision-maker can only act on what they can see. Leaders must ensure that the information driving each decision - the signal, the threshold, the condition - reaches the right person at the right time, by process, not by accident. This means designing the flow of operational information as deliberately as the SOPs themselves. When the right data reaches the right role automatically, the decision-maker doesn't need to attend a meeting to find out what's happening. They already know. They act. They document. They move on.

This is precisely how aviation, medicine, and the military handle high-stakes decisions under time pressure. They don't convene a group to brainstorm when the enemy attacks. They build the decision into the system before the moment arrives because the cognitive work must happen upstream, in a calm environment, by people with full information and no time pressure. The pilot executing the checklist is not making a decision in the moment. They are applying one already made by people smarter, calmer, and better-informed than anyone in a hectic and rushed cockpit.

Only decisions that genuinely cannot be resolved at a lower level (because they require cross-functional coordination, resource allocation above a certain threshold, or judgment that exceeds what any SOP can anticipate) should arrive at the management level. And when they do, they should be brought by the person closest to the problem, deliberated by people who actually know the content, and resolved against the best available framework. Not crowdsourced from whoever showed up to the morning standup.

The quality of your daily decisions is largely determined before the meeting starts. If your SOPs are current, condition-specific, and trusted, and if the right information reaches the right people by process (that means you have reporting requirements which are followed), your meeting becomes a brief exception-handling exercise for the things that genuinely couldn't be resolved lower down. If that infrastructure doesn't exist, your team will improvise under Hick's Law and Fredkin's Paradox every single day, and your best people will spend their sharpest hours on decisions that should have been made two levels down by someone who could actually see the problem.

The meeting is a symptom. The SOP, paired with deliberate information flow, is the cure.

The Operational Prescription

These aren't abstract theories. They are behavioral patterns that play out in every organization, every week, regardless of industry or size.

The accumulated weight of these laws points to a conclusion that most organizations resist: the daily leadership meeting built around group decision-making is not an efficient use of your best people's time or judgment. It is a context engineered, almost by design, to produce arguments about trivial things, ignore high-stakes decisions, exhaust people with options, diffuse accountability, and ratify choices nobody actually wanted.

The most valuable thing you can do before your next meeting is not sharpen your agenda. It's build the decision architecture that makes the meeting shorter, faster, and harder to derail.

Invest in your SOPs. Make them condition-specific, current, and trusted. Design the information flows that deliver the right signal to the right person before the decision is needed.

Distribute decision authority to the people closest to the problem. Reserve the management meeting for genuine exceptions, decisions that could not be resolved at a lower level and that require the judgment of people who actually know the content. When those decisions do arrive in the room, bring a recommendation rather than a blank agenda, name one accountable owner before the meeting closes, and ask explicitly whether anyone has an unvoiced concern before you adjourn.

The meeting isn't the problem. The absence of the work that should have happened before the meeting is.

The Challenge

Take your next recurring meeting and look at how much of the time is consumed by information distribution that could have happened before the meeting, arguments because people aren't informed or prepared, and human nature time-wasting from the laws described above.

My guess is you're going to see some shortening that could happen. Maybe some reporting requirements that need to change. Maybe move some of those decisions to be made outside the room.

If you give decisions to the floor, make sure you give them an SOP that describes options/constraints and implement reporting requirements that inform those decisions. Your employees are smart. They will make all of those decisions faster and better than you can.

Many minds make light work.

If you find waste, cut it. And try shortening the meeting. If you make it shorter, your people will fit the work into that window. That's Parkinson's law.