Sloane Labs

How calendar load quietly erodes deep work, and what to do about it.

7 min readSloane Labs
In short
It is not the total number of hours in meetings that erodes deep work, it is fragmentation: short gaps between commitments that are too small to do meaningful work in but too disruptive to ignore. Reading calendar structure, rather than just counting meeting hours, is what makes it possible to protect focus time before a week fills up.

Meeting hours are the wrong metric

A week with twelve hours of meetings spread across two solid days can leave more room for concentrated work than a week with eight hours of meetings scattered as thirty-minute blocks between everything else. Total meeting time is an easy number to report, but it is a poor proxy for whether anyone actually got deep work done.

What matters is contiguity: whether there are blocks of time long enough, and undisturbed enough, to enter and stay in focused work.

Why fragmentation is so costly

Getting into concentrated work carries a real switching cost. Every interruption resets that cost, so a calendar broken into forty-minute gaps between calls can produce far less usable focus time than the raw numbers suggest, even though it looks lighter on paper.

This cost is invisible in a calendar count and only shows up in how a day feels and what actually gets finished.

Reading structure, not just volume

Understanding calendar load properly means looking at the shape of a week: the length of the longest uninterrupted block each day, how often that block gets broken by late additions, and how this compares with a person's own recent pattern.

A useful system flags a week before it fills up this way, not after the fact, so someone has a genuine chance to protect a block rather than reading a report about a week that has already happened.

What protecting focus time looks like

  • Noticing when a day's longest free block has dropped well below a person's usual pattern, and suggesting they protect what remains.
  • Flagging a run of days with no substantial uninterrupted time at all.
  • Highlighting recurring meetings that consistently fracture the same part of the day across a team.

A team-level pattern, not just a personal one

Calendar fragmentation is often structural rather than personal: a recurring cross-team meeting placed in the middle of the day, or a habit of scheduling short calls back to back. Seen at team level, in aggregate, these patterns are often easier to fix than any individual's calendar habits alone.

Frequently asked questions

Is a full calendar always a problem?
Not necessarily. A calendar with long, solid meeting days followed by protected days can support deep work well. The issue is fragmentation, many short gaps scattered through a day, more than sheer volume.
What counts as a meaningful block of focus time?
This varies by role and task, but as a general guide, blocks shorter than around thirty minutes are rarely enough to enter genuinely concentrated work.
Can this be fixed at an individual level, or does it need a team change?
Both help. Individuals can protect blocks proactively, but recurring structural causes, like a badly placed team meeting, usually need a team-level fix to resolve properly.

Continue reading

If this is the sort of thing your team is working through, we are happy to talk.

How we begin