Why Your Manager Keeps Interrupting Your Focus Time

What each one is actually for

Deep Work

Concretely, Deep Work means picking a recurring slot on your calendar, the same hours on the same days if you can manage it, and removing everything that could interrupt it before the slot even starts: phone in another room, chat app closed, a signal on your door or your status that means not now. You show up to that slot often enough that getting started with the actual hard task stops being a decision you make each time and becomes simply what happens at that hour. The work inside the block has to genuinely tax you, the kind of task that a text message actually derails, not email or anything you could do half-attention.

Managing Up

Concretely, Managing Up means building a standing rhythm of telling your manager what you're doing before they ask: a short update at the same time every week, a heads-up the moment a deadline looks shaky, a two-line note before a meeting instead of an answer produced on the spot when you're put on the spot. It also means paying attention to how this specific manager actually wants that information, some want a bullet list waiting before the meeting starts, some want it said out loud, some barely want it until they ask, and matching that instead of defaulting to whatever format is easiest for you to produce.

What you get out of pairing them

Protecting a block buys you the difference between four scattered hours that produce a rough, half-finished draft and ninety genuinely uninterrupted minutes that produce something you'd actually call done, because every return from an interruption costs real minutes of the previous task still occupying part of your attention before you're truly back on the new one. Telling your manager what's happening in that block, on a schedule they can come to expect, buys you something different but just as necessary: a manager who already knows roughly what you're doing and when you'll next report in has less reason to check on you mid-block, and nobody defends an employee's unsupervised two hours as reliably as a manager who already trusts what tends to come out of it. Put the two together and each one is supplying the thing the other one needs to actually work: the block needs your manager's cooperation to survive, and the update is what earns that cooperation instead of leaving it to luck. Over a quarter, the difference compounds in a way a single week doesn't show: the deep-work side accumulates into actual finished projects rather than a rotating stack of half-started ones, and the managing-up side accumulates into a manager who stops needing a performance review to tell them what you've been doing, because they've already heard it, on schedule, the whole time.

What Deep Work rests on

• Attention is trainable randomised trials
  Repeatedly practicing directing and redirecting attention strengthens the ability to control where it goes, making that control more available over time.
• Context switching has a residue cost observational studies
  Part of the attention paid to a previous task lingers and degrades performance on the next one so fewer switches preserve more usable cognitive capacity.
• Environmental friction protects focus plausible mechanism
  Deliberately removing or blocking access to distracting cues in the immediate environment reduces the number of attention-switches before they can happen rather than relying on willpower to resist them.

What Managing Up rests on

• Perspective taking expands frame randomised trials
  Deliberately adopting a vantage point other than one's own default view widens the range of interpretations or options available for a situation.
• Adapting to anothers style improves collaboration observational studies
  Matching communication frequency and format to a manager's stated preferences produces smoother collaboration than expecting them to adapt to yours.
• Proactive disclosure builds trust observational studies
  Volunteering relevant information and progress updates before being asked builds a manager's trust and reduces their need to monitor closely.

Where they actually meet

Environmental friction, blocking a distraction before it can reach you, and proactive disclosure, telling your manager something before they have to ask, are the same design instinct pointed at two different problems. Neither practice waits for the unwanted thing to happen and then reacts to it. Both arrange the conditions ahead of time so the response they want doesn't depend on remembering to resist a ping, or remembering to speak up, once the moment has already arrived. Neither is really about hiding: deep work isn't disappearing, and managing up isn't reporting for its own sake. Both are about making a specific kind of protection legible enough that it survives someone else's legitimate need to know what's going on.

The principle underneath both

Deciding a structure while you're calm and clear about what matters, and then simply running that structure when the moment shows up, beats deciding fresh in the moment, because the in-the-moment version of you is tired, interruptible, or trying to look responsive right now, and none of those states produce your best judgment about what deserves protecting or what's worth saying. This is also why generic willpower advice so often fails at exactly this problem: it tells you to try harder in the moment, when the actual fix is deciding earlier, before the moment, so trying isn't required at all.

What that makes the real goal

Put plainly, both are chasing the same thing: removing yourself as the single point where something valuable could fail, your own attention in Deep Work's case, your manager's confidence in you in Managing Up's case, so the outcome doesn't hinge on you remembering, resisting, or performing correctly under pressure in real time. Reframed that way, the problem stops being "how do I focus better" or "how do I communicate better" and becomes a narrower, more solvable one: what structure, decided once, makes the behavior you want close to automatic when the moment shows up.

Other practices that serve the same goal

For protecting attention from a specific, predictable interruption, deciding in advance exactly what you'll do when it happens, "if a message comes in during my block, I won't look until eleven", is a form of if-then planning with a substantial experimental base showing it closes the gap between intending to ignore something and actually doing it. For the manager side specifically, a written weekly status document a manager can read on their own time serves the same trust-building function as a live check-in, and some managers respond to it even better, precisely because it doesn't cost them a meeting to receive. A shared team calendar that marks focus blocks visibly for everyone, not just your manager, extends the same idea sideways: it turns an individual agreement into a norm other people can see and route around on their own, without you having to explain it each time it matters.

A tradition that already does this

Peter Drucker's The Effective Executive, one of the source texts underneath modern time-management practice, already ran both halves of this move together in 1966: he told executives to consolidate their most important work into large, defended stretches of discretionary time, and in the same book told them to find out directly what their own boss actually needed rather than guessing at it. He wasn't describing two separate techniques, he was describing one discipline, protecting your best hours and understanding what they owe to someone above you, aimed at two fronts of the same job.

Using a protected block to make your update worth sending

The fastest way for a status update to become worthless is for it to summarize four scattered, interrupted hours, busy-sounding language covering very little actual progress, because there wasn't much progress to report. A protected block gives you something specific and closer to finished to put in that update: not "worked on the proposal" but "the second section is done and the numbers are checked," because you gave it ninety uninterrupted minutes instead of grazing at it between messages. Put your block earlier in the week than the update is due, so the update describes a block that already happened rather than one you're promising will happen. This also hands you something concrete to ask for: when you tell your manager what got finished in that block, name the block itself, "Tuesday mornings with the door closed are when the hard parts of this get done," which turns your calendar preference into something backed by work your manager has already seen, rather than a request they have to take on faith.

Using an update to buy the block that Deep Work actually needs

A protected block nobody outside your own calendar knows about is fragile, the first urgent-looking message, meeting invite, or quick question that lands during it will win, because your manager has no reason to route around a block they don't know exists. The actual move Managing Up teaches, telling someone what you need before you need them to already know it, fixes this directly: tell your manager, in the same rhythm you already use for updates, which specific hours are your focus block and what kind of work happens there, and ask what they'd actually want to hear about in that window versus what can wait for the next check-in. Most managers, once they can see the block reliably produces the finished work they were going to ask about anyway, end up defending it rather than interrupting it, not because they've become more patient, but because you've given them proactive information instead of leaving them to guess whether you're reachable.

It's 9:40 on Tuesday, your block runs until eleven, and your manager's name just lit up your phone

Six weeks ago this would have ended the block: you'd have checked it, answered, and spent the next fifteen minutes finding your way back into the document, only to notice ten minutes after that part of your attention is still on whatever the message was about. Instead you glance at the screen, see it isn't the word you and your manager agreed means genuinely urgent, and keep writing, because two weeks ago in your Monday update you told her this block runs nine to eleven every Tuesday and that anything short of urgent can wait for the two o'clock sync. At eleven-oh-five you check the message, a question about a different project, easily answered, and reply. What changed isn't your discipline, you were just as capable of ignoring a phone six weeks ago. What changed is that she now has a reason to expect you'll answer by two, so a ping that sits for ninety minutes reads as "he's in his block," not "he's ignoring me."

When this is worth reaching for

The focus block keeps losing to a manager who doesn't know it's happening — not to your own distractibility, and not to a manager who is genuinely and constantly firefighting. If interruptions come from your own phone or your own habit of checking things, Managing Up won't fix that; you need the environmental-friction half of Deep Work on its own. And if your manager is drowning in a real crisis where every message really is urgent, no update rhythm will buy you a clean block this week, and that's worth naming rather than pretending a system fixes what a bad week doesn't allow. It's also specifically useful in the first few months of a new manager relationship, before the two of you have built the shared history that would otherwise let them predict what you're doing without being told.

Where this does not apply

If there's no manager in the loop at all, you're a freelancer, a solo founder, or your role has no one whose expectations you're managing, there's nothing to manage up to, and the two practices simply don't meet; Deep Work still stands fine on its own. And if your job genuinely doesn't allow control over blocks of your own calendar, shift work, a live support queue, a role where being reachable is the job itself, no amount of proactive communication earns an uninterrupted block, because the structure of the work, not your manager's trust, is what's blocking it.

What the evidence does and does not support

The claims under Deep Work about training attention and about the cost of switching between tasks both draw on a substantial experimental literature on sustained attention and task switching, though Deep Work as a named, packaged practice, blocks plus a defended environment together, hasn't itself been tested as a bundled intervention against an alternative; the environmental-friction piece rests on behavioral-design reasoning rather than a dedicated trial. On the Managing Up side, perspective-taking has strong experimental support in general, while adapting to a specific person's communication style and building trust through proactive disclosure are both well-observed patterns in organizational research rather than randomized findings, since randomizing how someone manages their own boss isn't practical in most workplaces. Nobody has studied whether telling your manager about your focus block specifically increases how long that block survives interruption-free; the claim on this page is a mechanism argument, not a measured effect.