Meeting Overload Isn't the Problem. Fragmentation Is.

Key takeaways

‍

• The damage from meeting overload depends more on where meetings sit than on how many hours they take.

• Meeting time has grown sharply since 2020, and much of it lands in the hours people need for focused work.

• One meeting in the middle of a morning can split it into pieces too short for hard work.

• Clustering meetings into blocks protects longer working stretches than cutting a few meetings or clearing one day.

• Status updates and summaries can move into writing, with AI drafting them, so meetings keep the decisions that need people together.

‍

Meeting overload is real, but the usual fix of cutting meetings aims at the wrong thing: where a meeting sits costs more than how long it runs. A short call in the middle of the morning can cost the whole morning.

‍

Picture any given Tuesday: a call first thing, a check-in mid-morning, a review after lunch, and a sync late in the afternoon. None runs long, and the gaps look free. The work that needs a clear stretch, such as the plan or the forecast, slides into the evening.

‍

Cutting one or two meetings leaves that pattern in place. Moving the meetings that remain can give the day back.

‍

A full calendar, and no time to do the work

‍

Microsoft's 2022 Work Trend Index found that after two years, weekly meeting time for the average Teams user was up 252%. The figure counts Teams meetings only, during two years when a lot of in-person work moved online. It still shows how much of the week now goes to calls.

‍

Where those meetings land matters as much. Microsoft's 2025 Work Trend Index, drawn from Microsoft 365 data, found that half of all meetings take place between 9 and 11 a.m. and 1 and 3 p.m. Those are the stretches of the core day that hard work would otherwise use.

‍

People feel the cost. In a 2019 Korn Ferry survey of 1,945 professionals, 67% said too much time in meetings and on calls distracts them from making an impact at work.

‍

A leader asking for more output from the same team sees full days and steady effort. Time spent in meetings statistics count the hours. They miss the bigger loss: how little of each day is left in stretches long enough for hard work.

‍

Why "too many meetings" is the wrong diagnosis

‍

The usual answer to too many meetings is to cut some. That treats the count as the problem, and two calendars show why the count misleads.

‍

Take two people with the same 9-to-5 week and the same six hours of meetings. The first has two afternoon blocks, on Tuesday and Thursday from 2 to 5. The second has 12 half-hour meetings: one at 11 and one at 2:30 every day, plus two more.

‍

That leaves the first person eight unbroken half-days of four hours each. The second keeps none; that person's longest gap each day is three hours, and lunch falls inside it.

‍

Same hours, very different weeks. The first leaves room for work that takes a whole morning, and the second leaves no unbroken half-day at all. A clustered calendar could carry more meeting hours than a scattered one and still leave more half-days free. The two weeks are a worked example, with no measured data behind them.

‍

What fragmentation costs

‍

In a 2008 interview, Gloria Mark, an interruptions researcher at UC Irvine, said getting back to an interrupted task takes an average of 23 minutes and 15 seconds. What that number adds up to across a team is the cost of context switching. A booked meeting is expected, but it still ends one stretch of work and forces a restart.

‍

Fragmentation is what happens when enough restarts cut a day into short pieces. A day of gaps under an hour can hold email, quick replies, and small fixes. It can't hold a pricing model, a board memo, or hard analysis.

‍

This is the calendar side of fragmented work. Tools pull attention one way, and the meeting grid chops the day another. Focus time at work disappears without anyone deciding to remove it.

‍

Makers, managers, and who pays for the 11 o'clock

‍

In a 2009 essay, Paul Graham described two kinds of schedules. The manager's schedule is the traditional appointment book, with each day cut into one-hour intervals, so a meeting is one more slot. People who make things, such as programmers and writers, "generally prefer to use time in units of half a day at least." For them, Graham wrote, a single meeting "can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in."

‍

The tension in the maker schedule vs manager schedule debate is who sets the calendar. A manager can book an 11 o'clock that fits between other slots at almost no cost. The programmer whose morning it splits pays the bill, and that cost never shows up as a meeting hour. Graham was describing his own experience, but the mechanism is easy to check against your team's week.

‍

Cluster, don't cut

‍

The first half of the fix is to move meetings so they stop splitting the day. Graham's own answer was office hours at the end of his day. Because they came at the end, he wrote, those meetings "are never an interruption."

‍

For a team, that means protected mornings that stay free of bookings. Put recurring meetings into one or two fixed blocks each day. Give every recurring meeting an expiry date, so it ends unless someone renews it. The blocks have to line up across the team, or one person's cluster becomes another person's interruption.

‍

Then test each person whose job is making things: do they get at least one unbroken half-day, every day? If not, the calendar is the bottleneck, whatever the meeting hours say.

‍

This is also why a single meeting-free day can only do so much. No-meeting days clear one day, but four days out of five can stay chopped into short gaps. Clustering every day can protect at least one half-day on each of the five.

‍

Take the collaboration that doesn't need a room out of the calendar

‍

The other half of the fix is deciding what each remaining meeting is for. Status updates, reports, and routine decisions can move into writing. A written update can be read when it suits the reader, and no one's morning gets split to deliver it.

‍

AI makes that shift cheaper. It can summarize a long thread, draft the weekly update from notes and tickets already written, and surface open decisions for a lead to settle in writing. Moving status work to AI-drafted updates is a practical place to start with AI adoption, because the input already exists in writing. As updates leave the calendar, the meeting blocks shrink, and the protected stretches grow longer.

‍

What stays is the meeting that needs people together: a disagreement to settle, a plan to shape, a relationship to build. The clustered blocks give those meetings a home.

‍

Seeing where the week goes

‍

A calendar shows when meetings happen. It doesn't show whether the gaps between them were long enough for focused work. Start this week: run the half-day test on one team's calendar and move its meetings into blocks. A month later, look at the same team again to see whether the new calendar held.

‍

Insightful People Intelligence shows how people work and suggests opportunities to improve their output. With Work Patterns, it shows how each team spends the workday and suggests ways to improve focus and execution. You see how the day breaks up before you move a single meeting. Each opportunity is tracked from a starting point to a target, so the team can see whether the change worked.

‍

Insightful sees the apps, sites and AI tools your people use, and how they use them. It does not log content or capture keystrokes, messages, and documents. People Intelligence uses no screenshots or screen recordings.

‍

Start with a Work Audit. We show your first opportunities on your own data 14 days after the agent is deployed.

‍

Frequently asked questions

‍

How many meetings a day is too many?

No single number works, since what a meeting costs depends on where it falls. Three meetings back to back leave most of the day open; three spread out can leave no stretch long enough for hard work. A better measure is the longest unbroken block each person gets in a day.

‍

Do no-meeting days work?

They help, but one clear day can't offset four days that stay cut into short gaps. Grouping meetings into fixed blocks every day protects working time across the whole week.

‍

What is the 25/50 rule for meetings?

It means booking 25 or 50 minutes instead of 30 or 60, leaving a short break before the next meeting. That helps someone moving from call to call. It does nothing for a person who needs two clear hours to finish a piece of work.

‍

What is the 40/20/40 rule for meetings?

It splits the effort behind a meeting into 40% preparation, 20% in the room, and 40% follow-up. The rule improves how a meeting runs. It says nothing about whether the meeting should happen at all.

‍

What is the difference between a maker's schedule and a manager's schedule?

Paul Graham drew the distinction in a 2009 essay. Managers work in one-hour slots, so a meeting fills one more slot in the day. Makers need half-days, and one meeting in the middle can ruin the whole stretch.

‍

How much time do people spend in meetings?

Microsoft reported in 2022 a 252% increase in the average Teams user's weekly time in meetings since February 2020. In a 2019 Korn Ferry survey, 67% of professionals said spending too much time on meetings and calls distracted them from making an impact at work.

‍

What is meeting overload?

Meeting overload is more meeting time than a team's work can absorb, so work that needs focus spills into evenings or doesn't get done. The hours matter, but scattered meetings add a cost the hours don't show: they leave no long stretches for hard work.

‍