Defending focus blocks on a shared calendar
A focus block on a shared calendar is a claim on your time that other people get to vote on. Left vague — a grey rectangle titled “Busy” or “Focus time” — it loses every vote, because the person scheduling a meeting has a concrete need and you have an abstraction. The blocks that survive are the ones that do their own negotiating: the title says what the work is, the block says whether it can move, and when someone books over one anyway there is a rehearsed trade to offer instead of a silent surrender or a turf war. None of this requires permission. It requires labelling.
Name the block so it negotiates for you
The standard advice stops at categories: colour-code your calendar — Deep Work, Meetings, Collaboration, Administrative, Personal, Training — so the type of work is obvious at a glance. That helps you read your own week, but it does nothing for the colleague deciding whether your Tuesday block can absorb their meeting. They need two facts the category hides: what the block produces, and whether it can move. Put both in the title. “Draft Q3 report — firm” negotiates. “Focus” does not. A named deliverable also changes your own behaviour: a block with a product attached is harder to fritter than a block labelled with a mood, and at review time the titles double as a record of where the deep hours actually went.
Keep the details private if your calendar is widely visible. The title carries the deliverable and the tier; the sensitive content — the draft, the names, the numbers — does not need to be in the event description for the block to do its job.
Two tiers: firm blocks and flexible blocks
The fastest way to lose credibility is marking every block immovable — schedulers learn the label is bluff and start ignoring all of them, including the real ones. Split blocks into two tiers and defend them differently:
Firm blocks are tied to a deadline, a deliverable, or your one reliable peak-energy window. Guidance on team focus time suggests protecting regular blocks of at least two hours where difficult work can proceed without routine meetings or expected immediate replies — that is the scale a firm block should be: few, long, and genuinely defended. Cap them at two or three a week. A firm block that gets traded away should be a rare, visible event.
Flexible blocks are real work that can slide a day without damage: reading, planning, clearing the design-review queue. Label them as movable in the title — “Planning — can move” — and mean it. Flexible blocks are your trading currency. When a meeting truly needs a slot, you give up a flexible block, publicly and graciously, and the firm blocks gain protection from the contrast: everyone has seen you move when moving was cheap.
The decision rule for placing a block is simple. Ask: if this work slips by one day, does anything break — a deadline, a commitment to someone else, the only quiet window before a deliverable is due? Yes means firm. No means flexible, however important the work feels. Importance is not the test; slippage cost is.
Use the tools that enforce the block for you
Labels persuade people; settings handle the people who never saw the label — scheduling assistants, cross-team invites, the colleague in another time zone booking at midnight. On Google Calendar, a focus time event can mute Chat notifications and automatically decline meetings during the block; by default it declines new and existing meetings, and you can narrow that to only new meetings if declining an already-accepted meeting would cause more trouble than it prevents. Focus time events carry a headphones icon, so they read as a distinct kind of commitment rather than a blank busy bar. The feature needs a work or school Google Workspace account, and blocks must have a specific start and end time.
On the Microsoft side, the Viva Insights focus plan books focus time automatically — up to two hours a day, scheduled two weeks ahead, with Teams chats silenced during the block. Note its limit, because it shapes your expectations: automatically booked focus time never books over an existing event, which means it fills the gaps a meeting-heavy calendar leaves rather than defending space against new claims. And there is no built-in Outlook or Teams feature that hard-blocks a whole group's calendars at once — the manual fallback is a Busy or Out of Office event on each person's calendar, optionally private so others see only “Busy.” In practice: let the tools decline the routine collisions, and save your own negotiating for the exceptions.
When someone books over one: the trade protocol
- Don't decline silently, and don't accept silently. Either move teaches the scheduler that the label meant nothing. Reply within the day, in the invite thread or a quick message, while the scheduling is still fluid.
- Name the cost concretely. “That slot is the draft of the Q3 report, due Thursday.” A named deliverable with a date is a fact a reasonable scheduler can weigh; “I was going to focus” is a preference they can discount.
- Offer the trade, not the refusal. Propose two specific alternatives — ideally your flexible blocks, which exist for exactly this — or offer to take the meeting and move the firm block once, naming where it lands. The scheduler's problem is a slot, not your block; solve the slot problem and the block usually survives.
- If the meeting genuinely outranks the block, take it — and rebook the block in the same conversation. Some things should break focus: the working definition teams use for a legitimate interruption is an active customer problem, a live incident, or a decision that is blocking several people. Ordinary questions wait, or go to a written queue. When the real thing takes your block, the replacement block goes on the calendar before the meeting does its damage — a traded block with a new home is a system working; a vanished block is next week's overload.
- Count the repeats. One override is scheduling. The same person or team booking over firm blocks three times is a norms problem, and it gets raised as one — in a team meeting or with your manager, about the team's agreement, not about the last invite.
Make it a team norm, not a personal quirk
Individual blocks survive at the sufferance of the team's habits; norms change the habits. The norms that show up in team calendar guidance are plain: encourage everyone to block deep-work sessions visibly, establish no-meeting hours the whole team shares, respect blocks by not scheduling into them, and route non-urgent matters to async channels during focus time. Two of those do the heavy lifting. A shared no-meeting window means nobody defends a block alone — the calendar defends it for the whole team at once. And visible blocks from leaders matter more than any written rule: shared calendar blocks make the focus agreement visible, but leaders must also respect them and stop treating every open edge of someone's day as available meeting time. If you manage anyone, your blocks and your behaviour around other people's blocks are the norm, whatever the team document says.
Check it on yourself: at the end of the week, count firm blocks booked, firm blocks that survived intact, and firm blocks traded with a replacement booked. Survived plus properly traded is the score that matters — a perfect survival rate usually means the blocks were labelled firm but scheduled where nobody wanted the time.
Frequently asked questions
How much focus time should be on the calendar? Start with two or three firm blocks a week of around two hours — the length team focus guidance uses for work that needs no meetings and no expected immediate replies — plus flexible blocks wherever the gaps are. More firm blocks than that and the label stops meaning anything.
Isn't a labelled block just asking for an argument? The opposite. An unlabelled block invites the argument, because the scheduler has to guess what it costs to move it and usually guesses zero. A named deliverable and a firm/flexible tag answer the question before it is asked.
What if my calendar is fully shared and I don't want the work visible? Keep the title to the deliverable type and tier — “Report draft — firm” reveals a category of work, not its contents — and keep the detail in the task itself, not the event.