Meeting Overload
Meeting overload fills calendars until little uninterrupted time remains for focused work, fragmenting attention and fueling burnout. Reduce it with async updates, protected focus time, minimal invite lists, and an agenda for every meeting.
What It Is
Meeting overload is the condition where so much of the workday is consumed by meetings that little contiguous time remains for actual focused work. Calendars fill with standups, syncs, planning sessions, status updates, and recurring gatherings that long ago outlived their purpose. Coordination, which meetings are supposed to enable, ends up crowding out the very work being coordinated.
The cost is especially severe for engineers and other makers, whose productivity depends on long, uninterrupted blocks of concentration.
Why It Happens
- Meetings as the default. Any uncertainty or coordination need is answered with "let's set up a meeting."
- Recurring zombies. Standing meetings persist out of habit long after they stop being useful.
- Inclusion anxiety. People are invited to avoid leaving anyone out, swelling attendance.
- Visibility theater. Status meetings exist so managers feel informed, not because the team needs them.
Why It Hurts
Fragmented calendars destroy focus time; a day broken into thirty-minute gaps between meetings yields almost no deep work. Every meeting imposes a context-switching tax on top of its own duration. Decisions diffuse across many half-attended meetings rather than being made cleanly. People do their real work after hours to compensate, fueling burnout. And large meetings multiply the cost: an hour with ten people is ten person-hours spent.
Warning Signs
- Calendars are booked back-to-back with little open time.
- Meetings routinely have no agenda and no clear decision to make.
- Recurring meetings continue even when attendees are not sure why.
- People regularly do focused work in the evenings to catch up.
Better Alternatives
- Asynchronous communication. Replace status meetings with written updates people read on their own schedule.
- Meeting-free days or blocks. Protect large, predictable windows for deep work.
- The maker schedule. Cluster meetings to preserve uninterrupted maker time, per Paul Graham's distinction.
- Written decision records. Make decisions in documents with comments rather than in synchronous meetings.
How to Refactor Out of It
Audit recurring meetings and cancel those that cannot justify themselves; default standing meetings to expire unless renewed. Require an agenda and a clear purpose for every meeting, and keep invite lists minimal. Move status reporting to asynchronous written updates. Establish protected focus time — meeting-free days or large blocks — and cluster the meetings that remain. Track the calendar's open-time ratio as a health metric. The objective is to coordinate just enough to enable the work, not so much that it replaces it.