Protect Your Deep Work

The Senior-Role Attention Trap

Preliminary statement: 1. The specific problem this article solves: Senior professionals are losing their capacity for high-quality thinking not because they lack discipline, but because they have never explicitly negotiated their way out of institutional availability expectations that are informal, assumed, and therefore invisible. 2. The portable concept at its center: The availability trap — the self-reinforcing pattern where senior professionals signal constant accessibility, teams learn to expect it, and extracting yourself becomes socially and politically costly even when no one actually required it of you in the first place.

You have a director-level role, a team that needs you, and you have not done a single piece of thinking work before noon in six weeks.

This is not a discipline problem. The calendar got there one reasonable request at a time, and now it runs you.

The standard advice is to block off two hours every morning and guard them fiercely. Some version of this appears in every productivity book ever written.

It fails in senior roles for a specific reason: the block is invisible to everyone around you. Your team doesn’t know about it. Your manager doesn’t know about it. So when they message you at 8:47am with something that feels genuinely urgent, you either break the block or you don’t — and if you don’t, you spend the next forty minutes feeling vaguely hostile toward them and producing nothing useful anyway. The block becomes a performance of focus rather than actual focus.

The deeper issue is that availability expectations in most organisations are never written down. They are signalled, inferred, and then calcified into norm. You answered an email at 9pm once during a crisis, and now 9pm emails feel reasonable to the people around you. You kept your calendar open for a quarter while onboarding a new hire, and now the team routes problems to you by reflex rather than by necessity. The availability trap is not that people are making unreasonable demands — it is that the arrangement was never explicitly designed. What was never negotiated cannot be renegotiated by willpower alone.

The fix, then, is structural. Specifically, it requires making the arrangement visible and getting the people around you to operate inside a different version of it.

availability expectations in most organisations are never written down. They are signalled, inferred, and then calcified into norm. You answered an email at 9pm once during a crisis, and now 9pm emails feel reasonable to the people around you.

The interruption audit

The interruption audit. Before you redesign anything, you need data. Gloria Mark’s research at UC Irvine found the average knowledge worker gets interrupted roughly every three minutes, and that Fortune 500 CEOs average around twenty-eight uninterrupted minutes per day — not per hour, per day. If your instinct is that your situation is better than that, the audit will confirm or destroy that assumption. For two working days, log every interruption: a Slack message, a knock, a meeting request, your own impulse to check email. Note the time, the source, and whether you regard it as genuinely urgent in retrospect. Most people who do this exercise discover that sixty to seventy percent of the interruptions were neither time-critical nor requiring their personal input. That data is not just interesting — it is the document you bring to the next conversation.

The calendar got there one reasonable request at a time, and now it runs you.

The shallow work negotiation

The shallow work negotiation. Most senior professionals have never asked their manager what proportion of their time should go to coordination, email, and reactive tasks versus actual thinking work. Because no one has ever agreed on a number, shallow tasks fill available space indefinitely. Request a specific conversation with your manager — not a passing comment, a scheduled thirty minutes — and come with three things: a plain-language definition of shallow versus deep work, a rough account of your current actual ratio based on the audit, and a proposed target. For most non-entry-level roles, somewhere between thirty and fifty percent shallow is defensible. Get the number documented, even informally. This agreement does two things: it forces both of you to be deliberate about how your time is being used, and it gives you cover when you decline something later. “I can’t take that on this quarter — I’m already at capacity on shallow overhead” lands differently when it refers to an agreed budget rather than a personal preference.

The team communication protocol

The team communication protocol. The availability trap partly closes because teams learn to route problems through whoever responds fastest, and in senior roles that is usually the most senior person in the room. This pattern does not break on its own. You need to say something explicit to your team — in a team meeting or a direct one-on-one conversation — that distinguishes your primary function from your secondary one. The primary function is setting direction, developing people, and making decisions that cannot be made elsewhere. The secondary function is answering operational questions, and for most of those, they will get a better and faster answer from a designated colleague or from working it through themselves first. This is about routing, not unavailability. Say it plainly, once, and then reinforce it consistently over the following four to six weeks by redirecting questions that arrive directly to you when they should not. Teams adjust when the new expectation is held consistently. They do not adjust when it is held occasionally.

The batched coordination architecture

The batched coordination architecture. The most credible operational argument for constant senior-leader availability is that teams need to be unblocked quickly. This is often true. It does not require fragmented attention to address. Software companies using Scrum methodology solved this problem twenty years ago: replace scattered, ad hoc messages with a short standing meeting — fifteen minutes, fixed agenda, no sitting down — that handles blockers and status updates in one hit. For a senior leader, implementing something structurally similar means one daily fifteen-minute check-in with your direct reports at a fixed time, plus a defined window of two to three hours per day where you are genuinely reachable. Outside those windows, you are working. The mechanism here is predictability: teams become anxious about unavailability when they do not know when you will be available. When the window is fixed and reliable, the anxiety mostly disappears.

The two-block calendar structure

The two-block calendar structure. With the above in place, the morning block actually works — because it now has organisational context. The minimum viable deep work architecture for a senior role is two ninety-minute blocks per week of fully protected time, sitting inside a calendar that your team can see and understand. Not five, not every morning — two. The reason to start at two rather than five is that two can be held without heroic effort, which means you will actually hold them. Schedule them on non-meeting-heavy days, set an auto-response for that window explaining when you’ll next be checking messages, and use them only for the thinking work that genuinely requires your brain: not email triage, not catch-up reading, not preparation for the next meeting. Forty-five minutes of real thinking work, twice a week, will produce more than forty-five hours of fragmented availability. That is not motivational content — it is just arithmetic.

The most credible operational argument for constant senior-leader availability is that teams need to be unblocked quickly. This is often true. It does not require fragmented attention to address.

The honest caveat

The honest caveat. None of this works if your organisation’s real culture punishes protected focus regardless of what your manager agreed to in a meeting. Some cultures are structured around visible busyness, and in those cultures, the person who is hardest to reach gets penalised — subtly, informally, persistently. You can negotiate a shallow work budget and run a clean calendar structure and still find that the unspoken rules override the written ones. If your manager agreed to the thirty-to-fifty percent shallow target and then keeps asking where you were during the 10am Slack thread, you have a culture problem, not a time management problem. The tools here will not fix that. They will, at minimum, make the problem visible.

Pick one thing from your calendar for next week and move it. Not cancel — move it to a time slot that costs you less cognitively, and protect the slot you just freed for something that requires actual thinking. One slot. See what happens.

None of this works if your organisation’s real culture punishes protected focus regardless of what your manager agreed to in a meeting.