Back to the Journal

Meetings Aren't the Problem. Ungoverned Coordination Is.

72% of meetings are perceived as ineffective. But eliminating meetings without designing the system just migrates the problem to Slack/Teams. The real executive question is different.

The productivity software industry has been selling the same promise for five years: cut half your meetings. Buy the app that kills meetings, install the calendar blocker, book fewer. The ad is aimed at one person alone in front of a calendar, the metric is "hours returned to focus", and the pitch fits every screen identically. It is advice that sounds great and solves the wrong problem.

It gets it wrong on three levels.

1. The data is real, the reading is lazy

Atlassian published in 2024 that 72% of meetings are considered useless by the people sitting in them (n=5,000). Harvard Business School confirms the size of the hole: executives spend between 14 and 22 hours a week in meetings (Perlow et al., 2017; Rogelberg, 2019). Microsoft's Work Trend Index, in 2023, showed 57% of working time going to communication. And none of this is a privilege of the people at the top: the middle manager burns a similar fraction, and the specialist, though spending less per head, is so many people that their pool adds up to the biggest bill.

Order-of-magnitude model for a SaaS company of around 500 people, loaded cost per hour by level. The long tail (middle management plus specialists) adds up to 3 to 5 times leadership in absolute terms, because of headcount. Run it with your own numbers.
Hierarchy level% of time in rituals without a decisionHeadcount (in a 500-person company)Cost R$/hPool R$/year
Leadership (C-level + VPs)22 to 25%18 to 25R$ 250 to 350R$ 1.1 to 1.8M
Middle management (directors + heads)18 to 22%50 to 90R$ 100 to 150R$ 1.5 to 2.7M
Senior specialist12 to 18%110 to 180R$ 70 to 110R$ 1.8 to 3.5M
Analyst8 to 12%200 to 330R$ 40 to 70R$ 1.3 to 2.8M
Aggregated white-collar pool8 to 25%~500weightedR$ 5.7 to 10.8M/year

The numbers hold up. The conclusion "so cut meetings" is what falls apart. A meeting is not the economic unit of coordination, it is the receipt for it: the visible sign of an attempt to align people. Tearing up the receipt does not change the spend. Worse: cutting the meeting without redesigning what it was trying to solve pushes the problem into Slack, into Teams, into email, and the badly done async version costs more fractured focus, not less.

2. Bloated async is the same problem upside down

Whoever cut meetings by force reaps two patterns, and they show up on every floor:

  • Chat 3 to 5 times heavier, with decisions that turned into conversations spread over days, so the time to decide grows instead of shrinking. Leadership and the long tail take the hit equally.
  • Decisions reopened because what used to close in a room is now scattered across fourteen messages. Whoever did not read did not decide, and almost no one read to the end.

Microsoft measured it: 57% of time in communication, and of that slice, 30% is people chasing a conversation that fell behind, exactly the kind that swells when you cut the synchronous side without redesigning anything. That 30% spreads evenly across the hierarchy, it does not stay concentrated at the top. You shut off the tap at the sink and the pipe burst inside the wall.

Cutting meetings is the pitch of whoever sells the scissors. Governing coordination is a decision for whoever answers for capital and margin. Redesigning the flow is the work of whoever runs operations. Measuring the before and after in money is yet another craft. These are three distinct things, and treating them as one is like demanding that the CFO write the system's code.

3. The question the board actually asks

The question the COO and CFO take to the board is not "how many meetings do we have?". It is:

  • What slice of the entire white-collar payroll runs today in rituals with no matching decision, broken out by level?
  • Which rituals were designed for the problem we have now, and which are left over from when the company was half the size?
  • Where does the real decision live and where is it just conversation, in each layer of the pyramid?
  • What cascade does each leadership ritual trigger downward, and how much does that weigh in the aggregate?

This question is not answered with an engagement survey, nor with Otter, Fireflies or Read.ai. It is answered with an economic reading of coordination: how much of the whole payroll is stuck in rituals without a decision, cut by area, by ritual and by level, with a real cost attached to each line.

The same 500-person SaaS, now by layer: leadership is 4% of headcount and burns 22% of its own calendar; the long tail is everyone else. Recovering 60 to 70% through redesign is what enters the board as a P&L line. Run it with your own numbers.
LayerHeadcount% of calendarPerson-h/yearCost R$/hPool R$/year
Leadership~2022%8,800R$ 300R$ 2.6M
Long tail (middle management + specialists + analysts)~4808% (weighted)76,800R$ 80R$ 6.1M
Aggregated pool in rituals500weighted85,600weightedR$ 8.7M/year

Notice the proportion: leadership is the visible part, but the long tail carries almost double in absolute terms, because it is far more people. Cutting only the top solves less than a third. And recovering 60 to 70% of the aggregated pool through redesign is not culture talk, it is a line you can defend at the board.

Whoever still buys the app that kills meetings is measuring the wrong thing, and looking at the wrong floor. The CFO who needs an operating-leverage story for next quarter will not open a meeting recorder. They will open the aggregated number.

Ritometrics is the economic reading that closes the gap between "we cut 30% of meetings" (which only moves the problem to another room) and "this is the slice of payroll stuck in inertia rituals, by level, and here is what can be recovered" (which enters the P&L as a defensible line). The math is yours; the reading is what is missing.

Have you measured your aggregated pool?

The Coordination Calculator estimates the order of magnitude in 30 seconds, with three inputs, triangulated against auditable public benchmarks.

Open the calculator

Sources: Atlassian State of Teams 2024 (n=5,000) · Microsoft Work Trend Index 2023 · Perlow et al. (HBS, 2017); Rogelberg (2019) · loaded cost per hour triangulated with the Robert Half Salary Guide 2025.