People say they have no time to do their actual work.
Meeting Load and Fragmented Time
Fragmentation costs more than the meeting hours suggest. What to measure, what to cut, and the defaults that quietly generate the load.
Procedure
Meeting load is one of the few workload problems that can be reduced without reducing the work, which makes it the obvious first move.
Why fragmentation costs more than the hours
Recovery after interruption is not instant. Returning to demanding work takes time, so an hour meeting costs more than an hour.
The gaps between meetings are frequently unusable. Twenty-five minutes between two calls is not a working block.
Anticipation occupies attention. Knowing a meeting is coming in forty minutes prevents starting anything substantial.
A day at forty percent meetings can leave close to zero usable focus time, which is why people report having no time to work despite most of the day being technically free.
Measuring it
Meeting hours per person per week, by team and by level.
The largest uninterrupted block in a typical day. This is the number that matters and almost nobody tracks it.
Proportion of meetings with more than eight attendees.
Recurring meetings as a share of the total.
Meetings with no agenda.
Most calendar systems can report the first two, and the reporting is a half-day exercise.
What generates the load
Recurring meetings that outlive their purpose. Nobody cancels a standing meeting; it requires an act.
Inviting broadly to avoid excluding anyone, which converts a three-person decision into a twelve-person hour.
Meetings as status reporting, which is a written document performing badly.
Meetings as a substitute for a decision nobody wants to make alone.
Default durations. Thirty and sixty minutes are calendar conventions, not estimates.
Escalation by attendance. Adding senior people to a meeting to give it weight.
What to do
Audit the recurring meetings. Cancel everything recurring for one month and see what people ask to reinstate. This is blunt, effective, and the results are informative.
Default to shorter. Twenty-five and fifty minutes as the standard, which also creates gaps.
Require a purpose and an agenda, or decline. A meeting with neither is a request for other people's time with no specification.
Make attendance optional by default, with a note of who is actually needed.
Protect blocks. A shared no-meeting period, held by the organisation rather than by individuals, since an individual's blocked time gets overwritten by anyone senior.
Write instead. A status update as a document is faster to produce, faster to consume, searchable, and does not require synchronisation across time zones.
The senior calendar problem
Meeting load is worst at middle management, which is also where burnout rates are frequently highest.
Their calendars are filled by other people, which is a control problem as much as a workload one.
Their availability sets the norm. A manager who is in meetings continuously is not available to their team, which pushes the team's problems into their own out-of-hours time.
Any meeting reduction has to include this layer, or it moves load rather than removing it.
What not to do
A meeting-free day announced with no change to the volume, which compresses the same meetings into four days.
Asking individuals to decline more, which places the cost on the person with the least power in the invitation.
Replacing meetings with a message channel that then demands continuous attention, which trades one interruption pattern for another.
The recurring meeting amnesty
The bluntest intervention available and one of the most effective.
Cancel every recurring meeting for one month, announced in advance with the reason.
Anyone who wants one reinstated must ask, stating the purpose and who genuinely needs to attend.
Reinstate what is asked for, without argument.
Typically a substantial share is never requested, which is the finding.
The ones that are requested come back smaller, because the person asking has just had to justify the attendee list.
Repeat annually. Recurring meetings accumulate continuously and nothing else removes them, since cancelling a standing meeting requires an act that nobody is incentivised to take.
The default that generates the load
Small settings that quietly produce most of the calendar.
Thirty and sixty minutes as the only options, because that is what the tool offers.
Everyone invited to avoid the risk of excluding someone.
Recurring by default rather than scheduled again if needed.
Accept as the default response, so declining requires an act.
Change the defaults rather than exhorting people. Twenty-five and fifty minute standards, optional attendance marked explicitly, and no recurrence beyond a quarter without renewal.
Also in this section
- How do I know if my team is genuinely over capacity?
- How do people get demanding work done during the day?
- Why does the team collapse whenever one person is off?
- People are working hard but the wrong things keep happening.
- Why is every project a crunch at the end?
- Can people change their roles without a reorganisation?