Most executives can describe their company's capital allocation with precision. Few can describe how their organization allocates its scarcest resource: collective attention. Yet the calendar is a budget. Every recurring meeting commits salary, focus and cognitive energy. It is approved once and then rarely revisited. In many large organizations, meetings have quietly become the largest line item no one questions.

The problem is not that meetings exist. The problem is that they behave like an addiction. Each one delivers a small, immediate payoff: reassurance, visibility, the feeling of alignment. The costs accumulate out of sight. Deep work gets fragmented. Decisions drift upward. Senior leaders spend their days ratifying information they could have read in five minutes, then spend their evenings doing the actual work of leadership.

Treat it as a strategic problem rather than a question of etiquette, and meeting reduction becomes something more interesting: a way to reclaim organizational capacity without adding headcount or capital. The opportunity is significant because so few organizations manage it with any rigor. This article examines why meetings proliferate, how to judge whether each one deserves to exist, and how to design the ones that survive so they achieve their purpose in minimum time. The aim is not fewer meetings for their own sake. It is a calendar that reflects strategy rather than habit.

Meetings multiply for the same reason bureaucracy does. The incentives to create them are local and immediate, while the costs are diffuse and deferred. The person who schedules a meeting bears almost none of its expense. Attendees absorb the time cost, the organization absorbs the opportunity cost, and no one is accountable for the total. In economic terms, the calendar is a commons, and it suffers the predictable tragedy of overuse.

Several forces make this worse. The first is risk transfer. A meeting turns an individual decision into a collective one and spreads accountability across the room. For a manager unsure about a call, gathering stakeholders feels prudent rather than wasteful. Repeat that instinct across thousands of decisions and you get an organization where nothing moves without an assembly, and where accountability, spread so thin, effectively disappears.

The second is structural growth. Coordination complexity grows faster than headcount, because the number of possible communication pathways rises roughly with the square of team size. Organizations respond with standing syncs, cross-functional reviews and steering committees. Each is rational on its own terms. Together they form a coordination tax that rises every time the company grows, reorganizes or launches a new initiative, and it is rarely reduced when those initiatives end.

The third force follows from Clayton Christensen's work on how organizations build capabilities. A meeting created to solve a specific problem gradually hardens into a process, a routine that persists long after the original problem is gone. Processes are meant to be repeated without question. That is what makes them efficient, and it is also what makes outdated ones so durable. The quarterly review that once caught a real risk becomes a ritual no one challenges, because challenging processes is not what processes are for.

Finally, meetings carry symbolic weight. An invitation signals inclusion and status, and being left out signals the opposite. Leaders who attend everything look engaged, while those who decline risk looking detached. These signals make cutting meetings politically costly even when the operational case is obvious. Understanding these dynamics reframes the challenge. Meeting overload is not a failure of personal discipline. It is the natural outcome of the system, and it requires a systemic response rather than exhortations to be more efficient.

Takeaway

Meeting overload is not a failure of individual discipline. It is the predictable result of a system in which creating a meeting is free and cancelling one is costly, so if you change the cost structure, behavior follows.

If meetings multiply through systemic forces, they must be reduced through systematic ones. The most effective starting point borrows from finance: zero-based calendaring. Rather than asking which meetings to cut, assume every recurring meeting is cancelled and require each one to justify being reinstated. The burden of proof shifts from the person proposing change to the meeting itself. That reversal alone removes a surprising share of the calendar, because many meetings survive only through inertia.

Shopify applied a version of this logic in early 2023. It removed recurring meetings with more than two participants from employee calendars and encouraged teams to wait before adding any back. The point was not that all those meetings were worthless. It was that no one could know which ones mattered until the default was reversed. What teams choose to reinstate after a deliberate pause reveals what the organization actually needs, as opposed to what it has simply grown used to.

To decide what gets reinstated, apply Christensen's jobs-to-be-done lens: what job is this meeting being hired to do? Legitimate jobs for live meetings are narrower than most calendars suggest. A meeting earns its cost when it does one of four things. It can make a decision that needs live debate, solve a problem that benefits from rapid back-and-forth, build trust in relationships that matter strategically, or navigate conflict and sensitive conversations where tone carries meaning. Status updates, information broadcasts and routine progress reviews rarely qualify.

For every meeting that fails this test, find the better tool for the job. Written narratives, of the kind Amazon famously used in place of slide decks, force clearer thinking and can be read on each person's own schedule. Dashboards replace status reviews. Decision logs replace meetings held merely to inform. Clear decision rights replace committees that exist because no one knows who owns the call. Often the real problem a meeting hides is confusion about authority, not a genuine need for discussion.

Finally, separate the people who must contribute from those who only need to know. Most attendee lists blur the two. People who need only the outcome can receive a short written summary, which gives them back their hour without costing them alignment. Applied rigorously, these three filters (zero-based justification, a defined job, and disciplined attendance) usually show that much of an organization's meeting time serves no job that could not be done better another way.

Takeaway

Stop asking which meetings to cut and start asking which ones have earned the right to exist. When the default is reversed, inertia stops protecting the meetings that no longer do a real job.

The meetings that survive scrutiny deserve deliberate design. The core principle is simple: define the output before the agenda. An agenda lists topics. An output specifies what will exist when the meeting ends: a decision made, a plan approved, a risk resolved. Meetings without a defined output drift into discussion for its own sake, because nothing signals that the work is finished. Stating the intended output in the invitation disciplines everyone who accepts it, and makes it obvious when a meeting has no purpose at all.

Second, move information transfer out of the room. Time spent together live is the most expensive time an organization has, and spending it on presentations is a poor use of it. Circulate materials in advance, or open with a few minutes of silent reading of a concise memo so everyone starts from the same informed baseline. The meeting can then be reserved for what only live interaction provides: challenge, synthesis and commitment. Presentations inform. Meetings should decide.

Third, make decision rights explicit. Before the meeting, clarify who decides, who must be consulted and who is attending only to stay informed. Ambiguity here produces a familiar pattern: long discussion followed by no decision, or a decision quietly reopened a week later. When everyone knows who the decider is, debate becomes input rather than negotiation. The meeting can close as soon as the decider has what they need, rather than when everyone has finished talking.

Fourth, right-size time and attendance. Default calendar durations invite Parkinson's law, in which work expands to fill the time allotted. Set the length based on the job rather than the software's preset, and end early when the output is achieved. Limit attendance to decision-makers and essential contributors. Every additional participant adds coordination overhead and weakens each person's sense of responsibility for the outcome. A smaller room is usually a more accountable room.

Finally, close with commitments and build in expiry. Every meeting should end by confirming what was decided, who owns each action, by when, and who will tell the people who were not present. Recurring meetings should carry a sunset clause: an automatic review date after which they lapse unless someone deliberately renews them. This directly counters the dynamic Christensen described. It keeps today's useful routine from hardening into tomorrow's unquestioned ritual, and it keeps the calendar honest over time.

Takeaway

A well-designed meeting is defined by what exists when it ends, not by what gets discussed during it. If you cannot name the output in advance, you probably do not need the meeting.

Organizations rarely treat meeting overload as a strategic issue, which is exactly why it represents such an opportunity. Few levers can return meaningful capacity to an organization this quickly, without new investment or additional headcount. The constraint is not resources. It is the willingness to question routines that have come to feel permanent.

A practical framework follows from the analysis. Audit the calendar as you would a budget, measuring where collective attention actually goes. Test each recurring meeting against a zero-based standard and a clear job definition. Redesign the survivors around defined outputs, explicit decision rights and minimal attendance. Sustain the gains with sunset clauses and periodic review, because the forces that make meetings multiply never stop operating.

Leaders set the tone here more than almost anywhere else. When an executive declines a meeting that lacks a purpose, or ends one early because the job is done, the organization learns what the calendar is for. Strategy is ultimately about choosing what not to do. Your calendar is where that choice becomes visible.