Back to blog
Interruptions and Context

Protecting Focus Time When Everyone Can See Your Calendar

4 min read
protecting focus timefocus blocks calendardeep work remotecalendar blockinginterruption free time

The short version

  • A focus block on a shared calendar is visible to everyone and defended by no one. It stops meetings and does nothing about messages.
  • The block fails because ignoring a colleague has a visible social cost and breaking your own concentration has a private one.
  • Naming the block honestly, keeping it in the same slot, and having a manager defend it publicly all help.
  • None of that holds unless the person who needed you can get their answer while you are unavailable.

Blocking focus time is the standard advice and it half works. The block reliably prevents meetings, because the calendar is the system meetings are booked through. It does nothing about messages, which is where most interruptions arrive.

"Focus block on the calendar, five DMs inside it."

Why calendar blocks fail

A calendar block makes a public claim on your time with no mechanism to enforce it. It is a request, addressed to everyone, that they refrain from contacting you. Requests like that fail predictably when the person on the other side has a real need.

There is also a credibility problem. Focus blocks are the easiest calendar entry to override, because everyone knows they are self-declared. A meeting with three people carries social weight; a block called "focus" carries almost none, and colleagues who would never double-book a meeting will book over a block without hesitating.

Who defends it

This is the heart of it. Consider the two choices you face when a message arrives during your block.

Ignore it: the cost is visible, immediate, and social. A colleague waits, possibly notices, possibly mentions it. Answer it: the cost is private and deferred. You lose fifteen minutes of context that nobody else can see, and nobody will ever know it happened.

Almost everyone chooses to answer, and they are responding sensibly to the incentives in front of them. This is why individual discipline is the wrong tool for this problem: the person inside the block is the one least able to defend it, because they bear all the social cost of doing so.

Four practical moves that help

  • Name it for the work, not the mode. "Payments migration, heads down" is respected more than "focus time", because it reads as work rather than as a preference.
  • Keep the same slot every day. Predictability lets colleagues route around it without thinking, and lets you build a habit rather than a decision.
  • Have the manager defend it out loud. One public "Ana is heads down until 11:00, ask me instead" is worth more than a month of blocks, because it moves the social cost off the individual.
  • Publish where to go instead. A block that says "unavailable" invites a message. A block that says where to get the answer redirects it.

The fourth point is where most attempts stop short, and it is the one that determines whether the other three survive a busy week.

The seniority asymmetry

Focus time is distributed inversely to who needs it. Senior engineers, who hold the most context and do the most demanding work, are interrupted most, and they also have the least standing to be unreachable, because being available is part of how they became senior.

Meanwhile the people with the most protected calendars are often the ones whose work is genuinely interrupt-driven. This is worth naming explicitly with a team, because the usual framing, that focus time is an individual discipline problem, quietly asks the most interrupted person to solve it alone.

What actually removes the asymmetry is making their knowledge reachable without them. With StandIn, the ninety-second brief they confirm at the end of each day is what their StandIn answers from while they are off, in their words, with a source under every answer, clearly labelled, and never guessing. During the block, the colleague who needed to know where something stands gets it immediately. Blocked time stops being defended by nobody, because there is something else answering. See retire your out-of-office.

Common Questions

Do calendar focus blocks actually work?

They work for meetings and not for messages, so they deliver perhaps half the protection people expect. They work properly when paired with a way for colleagues to get answers during the block.

How long should a focus block be?

Ninety minutes to two hours, once or twice a day. Shorter than ninety minutes barely clears the recovery cost, and longer than two hours is hard to protect and hard to sustain.

Should I set my status to do not disturb?

Yes, and expect it to be advisory. Status indicators tell people you are busy; they do not tell people what to do instead, which is what actually stops the message. Pair the status with where to go.

What if my manager books over my focus block?

Raise it once, directly and without drama, and ask for the block to be treated as a commitment. Managers usually agree immediately, because they are booking over it out of habit rather than intent. If it keeps happening, the block is not the real problem.

When you're off, your StandIn is on.

It answers your teammates' questions from work you've already done, in your words, with a source under every answer.

You might also like