Why Growing Businesses Accumulate More Meetings Than Decisions

As a business grows, the number of recurring meetings on everyone's calendar tends to grow faster than headcount does — more people means more combinations of people who feel they should sync up. What doesn't grow at anywhere near the same rate is the number of actual decisions those meetings produce, which means a large share of that growth in meeting volume isn't buying the business any more decision-making capacity at all, just more time spent in rooms discussing decisions that mostly aren't actually being made there.

This mismatch is worth understanding mathematically, not just intuitively, because the growth in meeting pairings follows a predictable pattern that most businesses never explicitly notice until their calendars have already become unmanageable.

Why meeting volume and decision volume drift apart

Adding a person creates new possible meetings — this person with that team, this team with that stakeholder. It doesn't automatically create new decisions that need making; it just creates more opportunities to discuss the same ones.

Every new hire or new team creates new potential meeting pairings that didn't exist before — new cross-functional syncs, new status updates, new check-ins. None of that growth in meeting surface area is matched by a proportional increase in the number of genuinely new decisions the business needs to make. The result is more meetings circling the same decision volume, not more decisions getting made, because the underlying rate of genuinely novel, decision-worthy questions doesn't scale with headcount the same way the number of possible meeting combinations does.

A concrete illustration of how fast this combination math grows

A team of five has ten possible pairings for a cross-functional sync. Grow that team to twelve, and the number of possible pairings jumps to sixty-six — more than six times as many, from barely doubling the headcount.

Picture a cross-functional group that starts at five people, where the number of possible pairings between any two of them is ten. Grow that same group to twelve people — barely more than double the original size — and the number of possible pairings jumps to sixty-six, more than six times the original number. None of the underlying decisions that actually need making have multiplied by six; the sheer number of ways people could plausibly justify syncing up with each other has, which is exactly the kind of growth that tends to quietly fill a calendar without anyone deciding it should.

What this looks like inside a specific meeting

A recurring sync that used to resolve a real open question eventually keeps happening on the same schedule, long after the original open question has been resolved, simply because the slot is already on the calendar.

A recurring meeting that originally existed to resolve a genuine open question tends to keep its slot on the calendar well after that question has been settled, because cancelling a standing meeting requires someone to actively notice it's no longer needed and remove it — a small, easy-to-skip task that competes with everything else on a growing team's plate, and one that almost nobody feels individually responsible for doing.

Why this is expensive in a way that's easy to underestimate

Time spent in a meeting that isn't producing a decision is time not spent doing the work the decision was supposed to unlock — a cost that's invisible on any calendar but very real on a payroll.

A meeting that doesn't produce a decision isn't neutral — it's time the people in that meeting could have spent doing the work a decision was meant to unlock. Multiplied across a growing team and a growing number of recurring syncs, that cost becomes substantial, even though no single meeting on its own looks like an obvious waste of time, which is exactly why this particular cost tends to escape notice until someone actually adds it up across an entire team's calendar.

Why individual meetings rarely get challenged even when they're obviously redundant

Each attendee assumes someone else finds the meeting valuable, which means a meeting can quietly outlive its usefulness for years without any single person being the one to raise the question of whether it's still needed.

A meeting rarely gets cancelled through a single person's unilateral decision, because each attendee tends to assume someone else in the room still finds it valuable, even if they personally don't — nobody wants to be the one to suggest cutting something that might matter to a colleague. That diffusion of responsibility means a genuinely redundant meeting can survive for years, outliving the specific need that originally justified it, simply because no single attendee felt entitled to be the one who raised the question.

What tends to fix this once it's noticed

A periodic audit asking, meeting by meeting, "what decision did this produce last time," surfaces the ones that have quietly stopped earning their slot — and most teams are surprised by how many that turns out to be.

The fix is a periodic, honest audit of recurring meetings against a simple question: what decision did this produce the last time it happened. Meetings that can't answer that question clearly are candidates for cancellation, consolidation, or replacement with something that doesn't require a live, synchronous gathering at all — and most teams that run this audit are surprised by how much of their calendar fails the test, often finding that a substantial share of their recurring commitments had quietly stopped producing anything beyond the habit of continuing to meet.