Can a manager's one-on-ones actually be the thing that protects a report's deep work time?

What each one is actually for

Deep Work

Deep Work names a specific kind of block, not a general philosophy of trying harder: a scheduled period, ideally the same time most days, spent on one cognitively demanding task with every likely interruption removed in advance — phone in another room, notifications off, calendar marked busy, and, where possible, a small ritual that signals the block has started, like closing a door or putting on the same pair of headphones every time. Newport's argument is that this kind of undistracted attention produces a rare, high-value kind of output that shallow, interrupted attention structurally cannot, no matter how many total hours get logged; a fragmented day made of forty five-minute focused stretches broken up by messages does not add up to the same result as two genuinely unbroken hours, because a mind that's just been interrupted needs real time to reload the problem it was holding before the interruption arrived. The mechanism the whole practice depends on is protection: the block only works if nothing is actually allowed to interrupt it, which is a much harder condition to secure in most workplaces than simply deciding, alone, that you value focus.

Effective One-on-Ones

Effective one-on-ones are recurring, protected meetings between a manager and a direct report, run on a fixed cadence — weekly or every other week is typical — and deliberately built around the report's own agenda, not primarily as a status update flowing upward to the manager. Practices like the ones described by Andy Grove and later popularized in management writing such as Julie Zhuo's and Camille Fournier's work treat the meeting's real job as surfacing whatever is actually going on for that person — a blocker, a frustration, something they're unsure how to raise in a group setting — early enough that a manager can actually help with it, rather than discovering the same problem three weeks later once it's become a resignation letter or a missed deadline. The mechanism is protected, dedicated time functioning as a standing invitation: because the meeting recurs reliably and is explicitly theirs to set the agenda for, a report doesn't have to judge, each time, whether a given issue is important enough to interrupt the manager for — there's already a slot reserved for exactly that.

What you get out of pairing them

Deep Work's payoff, when the block actually holds, is real: two protected hours on one hard problem regularly produce something two hours split across a dozen interruptions simply cannot, in writing, coding, analysis, or anything else where holding a complex problem in mind matters. What the practice does not solve on its own is the organizational half of the problem — an individual can block their own calendar, but they usually cannot unilaterally stop a manager, a teammate, or a norm of instant chat replies from treating that block as available anyway, and in most workplaces that's exactly what happens within a few weeks of trying. A one-on-one's payoff is that it gives a report a structured, expected, non-awkward place to actually raise that exact problem — 'my focus time keeps getting eaten by meetings you're scheduling' — and gives a manager a specific, recurring moment to actually do something about it, rather than the issue floating as a vague, never-quite-raised frustration that shows up eventually as burnout or quietly declining output nobody can name the cause of.

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 Effective One-on-Ones rests on

• Small wins compound randomised trials
  Repeating a small consistent action accumulates over time into a result too large to produce in a single step.
• Early surfacing prevents escalation observational studies
  Regular structured check-ins surface small issues while they are still cheap to address before they compound into larger problems.
• Protected time signals priority observational studies
  Consistently protecting recurring time for a direct report's agenda signals that their concerns matter and increases psychological safety and disclosure.

Where they actually meet

Both practices depend on the same scarce resource actually being defended against the same predictable threat: something else claiming the calendar. Deep Work defends a block of time against interruption so that one person's attention can stay on one hard problem long enough to produce something real. An effective one-on-one defends a different block of time against exactly the same pressure — cancellation for a 'more urgent' meeting, getting shortened to ten distracted minutes — so that a report's actual concerns get a reliable slot instead of being squeezed out by whatever feels most urgent that particular week. Neither works if it exists only as an intention; both only work if someone, on a given day, chooses to protect the specific block over the thing trying to eat it.

The principle underneath both

Protected time is not something an individual can reliably secure alone when other people control the calendar around them. Deep Work assumes a person can defend their own block, but in most jobs that block sits inside a calendar other people, mainly a manager, can override; the block's survival depends on whether the person with that authority treats it as legitimate. A one-on-one is one of the few places that authority actually gets exercised in a report's favor on a recurring basis — it's a manager consistently choosing, week after week, to hold a specific slot open for someone else's stated priorities rather than letting it get absorbed by whatever feels urgent that day.

What that makes the real goal

If protection has to come from someone with real calendar authority, not from personal discipline alone, then the actual goal both practices are chasing is the same one: get a scarce, valuable block of time reliably defended against the constant pressure to fill it with something that feels more urgent in the moment. Named this way, the goal isn't specific to knowledge work or to management technique — it applies to any recurring commitment, professional or personal, that keeps losing to whatever shows up that day feeling more pressing, and it explains why 'just block your calendar' advice so often fails on its own: it asks an individual to solve a problem that actually requires someone else's cooperation.

Other practices that serve the same goal

Team-level 'no-meeting' policies — a day or block of hours a whole organization agrees to keep clear of internal meetings — pursue the identical protection goal by making the defense structural and default rather than dependent on any one manager's judgment case by case, and several companies report meaningful drops in reported interruption when they adopt one, though rigorous outcome research on this specific policy is thin. Explicit team working agreements, common in agile software teams, where a team collectively decides and writes down when focus time is sacred versus when interruption is acceptable, pursue the same goal through peer accountability instead of managerial authority, with some observational support in software-team research for reducing context-switching. And a simple visible status signal — a calendar block genuinely marked busy, a closed door, a physical sign — pursues a narrower version of the same goal by making the existing protection legible to people nearby, without requiring anyone new to actually grant permission for it.

A tradition that already does this

Academic sabbaticals are close kin to this exact pairing, formalized long before either practice had its current name: a scheduled, protected block of time, sometimes a full year, explicitly defended by an institution against the ordinary pull of teaching and committee work, granted specifically because sustained, undistracted attention on a research problem produces something the same hours spent in fragments across a normal semester reliably do not. The sabbatical only works because the institution, not just the individual professor, agrees to protect it — the same dependence on someone with real authority actually holding the line that a deep work block needs from a manager, just scaled up to a year instead of a two-hour block.

Using deep work's own logic to change what a one-on-one is actually for

Most one-on-ones default to status updates because nobody has specifically claimed the time for anything else, which means the calendar-protection conversation deep work actually depends on never comes up on its own. A manager can deliberately put it on the agenda: ask, directly, 'what's currently eating your focus time that shouldn't be,' and mean it as an actual question to act on, not a rhetorical one. When a report names something specific — a recurring meeting they don't need to be in, a habit of pinging them mid-task for things that could wait for the next standup — the manager's job in that moment is to actually remove it, on the spot if possible, rather than sympathizing and moving to the next agenda item. Treating calendar protection as a standing, named topic, not a one-off complaint someone has to work up the nerve to raise, is what makes the one-on-one useful to deep work at all, rather than just another meeting competing for the same block it's supposed to be defending.

Using the one-on-one to make deep work more than a personal habit

An individual's deep work block is fragile precisely because it usually depends on nobody else deciding to interrupt it, which is a bet that quietly loses more often than people admit. The one-on-one is the specific, recurring venue where a report can convert that fragile personal habit into something closer to an actual agreement: naming the exact block — Tuesday and Thursday mornings, nine to eleven — and asking the manager directly to treat it as unavailable for meetings, and, just as importantly, to model that same protection by not pinging during it themselves. A manager who agrees, and then visibly holds to it over several weeks by never scheduling into that block and not messaging during it, does something an individual's own willpower cannot do alone: makes the block real to everyone else on the team too, since a manager's calendar behavior is usually the strongest signal in the room for what's actually allowed to be protected.

The recurring 2pm meeting that keeps landing in the middle of Wednesday's focus block

For three weeks running, a recurring 2pm sync has landed directly inside the two-hour focus block you'd set aside for Wednesday afternoons, and each week you've quietly let it happen rather than making an issue of it. In this week's one-on-one, your manager asks what's currently getting in the way of your best work, and instead of giving the usual vague answer, you name the specific thing: 'the Wednesday 2pm sync keeps cutting my focus block in half, and I end up not getting back into the work afterward.' Your manager, instead of just noting it, opens the calendar right there and asks whether you actually need to be in that sync every week or whether an async update would cover it. It turns out you don't need to be there most weeks. Your manager removes you from the recurring invite on the spot and tells the two other people on it they'll get a written update from you instead. The following Wednesday, the block is actually clear for the first time in three weeks, not because you found more willpower, but because the one person who could remove the obstacle from the calendar finally knew it was there and did something about it in the same conversation.

When this is worth reaching for

Cognitively demanding work sits inside a role where a manager controls or influences the calendar — true for most knowledge work — and deep work blocks keep getting interrupted or double-booked no matter how hard they're individually protected. That's the moment this matters most. It's also the right moment for a manager already running solid one-on-ones to add this specific question to the standing agenda, rather than waiting for a report to raise calendar problems unprompted, which many people are reluctant to do without being asked directly.

Where this does not apply

If someone works independently with no manager or scheduling authority over their time — freelance, solo, or self-employed — this pairing doesn't apply in its literal form, since there's no one-on-one relationship to use; the underlying goal of defended time still matters, but the mechanism has to be something else, like a client-facing boundary instead. And in a genuinely crunch-driven period with a hard, fixed deadline bearing down on the whole team, insisting on protecting a personal deep work block against every other demand can read as, and sometimes actually be, a poor read of the moment; that's a short-term trade worth naming honestly rather than defending on principle.

What the evidence does and does not support

The value of protected, uninterrupted time for complex cognitive work has observational and experimental support in attention research, including studies on the real cost of resuming a task after an interruption, though Deep Work as a named, packaged practice has not itself been tested in a randomized trial. Structured one-on-ones have solid observational support in organizational and management research linking regular manager check-ins to earlier problem detection and better reported employee engagement, though causal, controlled evidence specifically isolating the one-on-one format from other forms of manager attention is thinner than the popularity of the practice would suggest. No study has examined whether one-on-ones specifically improve an individual's protected focus time, or the reverse; the connection drawn here is a reasoned one between two separately supported practices, not a finding from research that studied them together.