Why Some Teams Do Better Work With Fewer Meetings on the Calendar

When I ran operations for a distributed software company, I inherited a calendar that no single person had designed. Every recurring meeting had been added by someone, for a reason that made sense at the time — a weekly sync to fix a coordination problem that no longer existed, a status update whose purpose had migrated to a shared document nobody read aloud anymore. Nobody had ever removed a meeting once it existed, because removing something requires someone to notice it, and calendars are remarkably good at hiding in plain sight.

The team had grown from six people to nearly thirty over two years, and the meeting schedule had grown along with it, but not proportionally. New meetings were added at every stage to solve a problem specific to that stage — early coordination gaps, then cross-team dependencies, then a management layer that needed its own updates — and none of the earlier meetings were ever re-evaluated once the problem they solved had been absorbed into some other process. By the time I looked at it properly, a fairly ordinary engineer was spending close to a third of a working week in some form of recurring meeting, most of it inherited from a version of the company that no longer existed.

The audit I eventually ran was almost embarrassingly simple: list every recurring meeting, note who actually needed to be in the room versus who was there out of habit, and ask, for each one, what would break if it simply stopped happening. Roughly a third of the meetings had no good answer to that question. Cutting them didn't just free up time. It changed how the team talked about its own work.

What meetings are for

Most recurring meetings exist to solve one of three problems: information needs to move between people, a decision needs to get made, or people need to feel coordinated with each other even when no specific information or decision is on the table. The first two are legitimate, and a meeting is often a reasonable tool for them. The third is where most calendars quietly bloat, because "feeling coordinated" is a real need that a meeting satisfies poorly and expensively.

Teams that have not examined their own meeting habits tend to default to synchronous time for all three problems, even though only the middle one — decisions — reliably benefits from everyone being in a room, real or virtual, at the same time. Information can move through a written update, read at whatever moment suits each person's actual working rhythm. The feeling of coordination, it turns out, comes more reliably from visible, shared progress than from a shared calendar slot; a team that can see what everyone else did this week feels coordinated without needing to hear it said aloud.

It is worth being honest about why the third category persists despite being the weakest justification. A meeting that exists mainly to produce a feeling of coordination is rarely defended in those terms — nobody schedules a recurring call and calls it a "reassurance meeting." It gets defended as a status update or a sync, borrowing the legitimacy of the first two categories while doing the emotional work of the third. Spotting the substitution requires asking a slightly uncomfortable question: if this meeting were cancelled and replaced with nothing, what specifically would go wrong? Often the honest answer is "nothing would go wrong, but it would feel like something was missing" — and that feeling, while real, is a different problem than the meeting was ever designed to solve.

The real cost of a meeting

The direct cost of a meeting — the time it occupies — is the easiest cost to see and the least significant one. The larger cost is what a scheduled meeting does to the unscheduled time around it. A single hour blocked in the middle of a working day doesn't just remove that hour; it fragments the time on either side of it, because most people cannot drop into genuinely focused work knowing an interruption is coming in forty minutes. Three scheduled meetings, spread through a day, can effectively destroy most of that day's capacity for deep work, even though the meetings themselves account for a fraction of the actual hours.

This cost compounds across a team faster than it compounds for an individual. A meeting that costs one person ninety minutes of fragmented focus costs a ten-person team fifteen person-hours, most of which never shows up anywhere as a line item, because nobody tracks the cost of interrupted concentration the way they track the cost of the meeting itself.

That invisibility is precisely why the fix rarely comes from measuring harder. Nobody needs a more precise number to know that a day cut into four pieces produces less than a day left whole; the evidence is available to anyone willing to compare a meeting-heavy week against a quiet one and notice, honestly, which produced more finished work. The audit matters less as an accounting exercise than as a forcing function — a scheduled moment to ask the uncomfortable question before the calendar quietly answers it by default.

What changes when the calendar empties out

The teams that go through a genuine meeting reduction rarely describe the immediate aftermath as smooth. There is usually a period of real discomfort, because meetings had been doing quiet emotional work — reassuring people that everyone was still aligned, still paying attention, still on the same page — that a written update does not automatically replace. Teams that cut meetings without replacing that reassurance with something else, usually a more disciplined habit of visible written progress, often end up recreating the meetings within a few months, because the underlying need for coordination was real even if the meeting itself was an inefficient way to meet it.

The teams that make the reduction stick tend to replace synchronous coordination with asynchronous visibility rather than with nothing. A shared weekly written update, genuinely read rather than skimmed, does more to sustain a sense of alignment than most standing meetings manage, because it can be read at the moment it is useful rather than at whatever time a calendar happened to reserve.

None of this argues for a meeting-free organisation, which is its own kind of dogma and just as capable of causing harm as an overscheduled one. Some decisions genuinely need real-time discussion, and some relationships genuinely need face time to function well. The argument is narrower: most recurring meetings were added to solve a specific problem that has since either resolved itself or migrated to a better tool, and almost nobody goes back to check. The audit is uncomfortable, mostly because it requires admitting that a meeting someone cares about might no longer be necessary. It is also one of the highest-leverage changes available to almost any team, precisely because so few teams ever run it.