Deep Work in a Distributed Team: Defending Focus Blocks When Everyone's Always "Online"

Remote work was supposed to kill the open-office interruption problem. Instead it replaced tap-on-the- shoulder interruptions with something harder to say no to: a little green dot next to your name that implies you're reachable at all times, on every channel, from whoever happens to be awake right now. Nobody explicitly agreed to that standard — it just accumulated, one quick Slack question at a time, until the default expectation on most distributed teams is that "online" means "interruptible," full stop.

Presence status isn't a schedule

The core problem is that chat tools conflate two different things: whether you're at your computer, and whether you're available to context-switch right now. A green dot tells a teammate you're logged in — it says nothing about whether you're mid-way through debugging something that took 40 minutes to load into your head, and where a two-minute Slack question costs a lot more than two minutes. Most teams never separate these, so the default assumption becomes "green means ask," and the person doing deep work either eats the interruption or feels vaguely guilty for muting the channel.

This is the same mechanism behind the gap between what surveys say about meeting fatigue and what the actual timing data shows — the stated policy ("we're async-first") and the lived default (constant interruptibility) drift apart quietly, and nobody notices until someone burns out or a hard problem takes three times longer than it should have.

Response-time tiers, not blanket availability

The fix isn't telling people to "just block focus time" — calendar blocks get overridden constantly when there's no shared agreement about what they mean. It's giving every channel and message type an explicit, team-wide expected response time, so a focus block isn't a personal negotiation every time — it's just what the tier already promises.

Once this is written down and genuinely shared, a calendar-blocked focus window stops being a personal request for special treatment and becomes exactly what Tier 3 and Tier 4 already promised: it's fine that it waits, because everyone already agreed it would.

Why this matters more across time zones, not less

It's tempting to assume time zone spread naturally protects focus time — if your teammates are asleep, they can't interrupt you. In practice it does the opposite for a large chunk of the day: distributed teams tend to compress their few hours of live overlap into meetings, which pushes async messages to fire off constantly during everyone's solo hours instead, arriving from whichever region is currently awake. Without explicit tiers, "solo hours" becomes indistinguishable from "always-reachable hours," and the focus time the time zone gap was supposed to protect gets eaten by drive-by pings from people who genuinely don't know they're interrupting anything.

What actually erodes focus blocks

• Meetings scheduled inside a stated focus block because the calendar shows the person as free, not busy. Blocking the time as a real event, not a note, fixes this mechanically rather than relying on people remembering.
• "Quick call?" as the default response to a Slack message instead of writing the question down, which converts an async-tolerant question into a synchronous interruption purely out of habit.
• No shared tier system, so every individual has to personally negotiate what "urgent" means with every teammate, which quietly favors whoever is most comfortable pushing back — usually not the newest or most junior person on the team.

Setting this up

1. Write the response-time tiers down somewhere permanent — a wiki page, not a Slack message that scrolls away — and get explicit buy-in in a team meeting, not just a doc nobody reads.
2. Block real calendar time for focus work, not a status note, and default new meeting invites to check for conflicts against it.
3. Normalize writing the async question down first, and reserve live calls for the genuinely synchronous cases outlined in the async-first decision framework.
4. Revisit the tiers after a quarter — teams that skip this step tend to let Tier 2 quietly absorb everything, because "just this once" is easier to say than "actually, that's a Tier 3."