Why meetings multiply (and what actually reduces them)

Executives now spend 23 hours per week in meetings, more than double the figure from the 1960s. Hours wasted in unproductive meetings have doubled since 2019, reaching 5 hours per week per employee. Workers are interrupted by meetings, messages, or notifications every 2 minutes on average. And 52% of employees multitask during virtual meetings, which suggests that even the people physically present aren't mentally engaged.

Everyone agrees there are too many meetings. Nobody seems able to reduce them. The reason is that most meeting-reduction efforts target the meetings themselves (shorter agendas, strict time limits, no-meeting days) rather than the underlying cause: undocumented knowledge that can only be shared synchronously.

Why meetings exist

Meetings serve four purposes, and understanding which purpose each meeting serves is the key to deciding which can be eliminated.

Context transfer. "Here's what happened, here's the status, here's what's coming." Standups, status updates, all-hands, sprint reviews. These exist because the information isn't available anywhere else. If it were documented and searchable, the meeting wouldn't need to happen.

Decision-making. "We need to choose between A and B." Architecture discussions, strategy debates, planning sessions. These require discussion, though the discussion is more efficient when participants have read the context and options in advance rather than hearing them for the first time in the meeting.

Alignment. "Are we on the same page?" Kickoffs, retrospectives, cross-team syncs. These exist to ensure shared understanding, which documentation provides more reliably than a meeting (docs reach everyone, not just attendees, and persist beyond the meeting's duration).

Creative collaboration. Brainstorms, design sessions, pair programming. These require real-time interaction to generate something new through the combination of different perspectives.

Only the last category, and parts of the second, require people to be synchronous. The first and third, which in most organisations account for the majority of meeting time, can be handled with documentation and async processes.

The documentation dependency

Each replaceable meeting has a documentation equivalent:

Daily standup → project status in the self-writing wiki. The status is generated from GitHub activity and project discussions, visible to everyone, updated continuously. No meeting required.

Sprint review → change log generated from merged PRs. What was shipped and why, available to anyone who wants to read it.

Context-sharing meeting → searchable documentation. The context is available on demand rather than delivered in a scheduled session.

Decision meeting → decision document with async comment period. The options and reasoning are written up, shared, and open for comment. If no substantive objections arise, the decision is made without a meeting. If they do, the meeting starts from shared understanding rather than spending twenty minutes establishing it.

Each replacement requires documentation that's current, searchable, and trusted. Self-writing docs from Slack, GitHub, and meetings provide this, because they update automatically and stay accurate without manual maintenance.

The multiplication mechanism

Meetings multiply with team size because of the same communication path explosion that drives all coordination overhead. At 10 people, one standup covers the whole team. At 30, you need three team standups plus a leads sync. At 50, you need team standups, pod syncs, cross-team syncs, and an all-hands, each creating its own scheduling overhead and consuming more aggregate time.

The multiplication is self-reinforcing: more meetings mean more things discussed in meetings, which means more context that's only available to meeting attendees, which means more meetings to share that context with people who weren't there. The meeting becomes the knowledge system, and the knowledge system requires ever more meetings to function.

Breaking this cycle requires making the knowledge available outside meetings, which requires documentation infrastructure. The meeting problem is, at its root, a documentation problem.

Frequently asked questions

How many meetings per week is reasonable? Research suggests that knowledge workers who maintain at least 3.5 hours of daily focus time report being productive and satisfied (Worklytics 2025). Work backwards from that: protect 3.5 hours of focus, allocate time for necessary creative and decision meetings, and let the remaining time handle async coordination and shallow work.

Won't people miss important information if we cancel meetings? If the information is documented, searchable, and current, coverage is actually better than meetings. Everyone has access (not just attendees), the information persists (rather than fading from memory), and it's searchable later when someone needs it for a specific purpose.

What about team culture and morale? Preserve social connection deliberately through dedicated social time rather than using informational meetings as a proxy for it. A weekly team coffee is better for culture than five daily standups.

Related reading: How to reduce meetings, The coordination tax, The meeting that should have been a doc, Work about work. Related pages: Self-writing docs, Decision log.