The Focused Week: Deep Work for People Who Manage

Deep work is usually described as a luxury of people without meetings — the novelist’s morning, the programmer’s flow state. Managers are told, implicitly, that their work is the interruptions. That is half true and wholly dangerous. A manager’s deep work is real work: thinking through the decision before the meeting about the decision, preparing the feedback conversation instead of improvising it, reading the numbers slowly enough to see what they are actually saying. When that work has no protected place in the week, it does not disappear. It gets done badly, at speed, between other things — and the whole team pays for the quality of a manager’s rushed thinking.

The week gets designed before it gets filled — or not at all

An empty calendar does not stay empty, and it does not fill in order of importance. It fills in order of arrival and insistence. So the focused week is built in the only order that works: the thinking work goes in first, as appointments with the same standing as meetings with other people, placed where your energy actually is rather than in the scraps at the end of the day. Two or three protected blocks is a realistic ambition for most managers — not a monastic schedule, just a defensible perimeter. Then the collaborative work is arranged around them: meetings batched where possible so the day is not shredded into twenty-minute fragments, the one-on-ones and reviews given their regular rhythm, and genuine slack left standing, because a week with no slack is a plan that the first emergency gets to rewrite entirely.

Defending the block is a communication act

Protected time that is a secret will be overrun, and fairly — nobody can respect a boundary they cannot see. The defense is mostly communication done in advance: the block is visible on the calendar with an honest label, the team knows what it is for and what genuinely interrupts it, and the manager keeps it often enough that keeping it is normal rather than a scandal. The emergencies clause matters: protected does not mean unreachable, it means the bar for interruption is “this cannot wait ninety minutes,” not “this occurred to me.” And the manager owes the team the visible dividend — the better-prepared conversation, the decision that arrives thought-through — because focus that never shows its work reads as absence.

End the week by auditing it

The focused week closes with ten honest minutes: which blocks survived, which were taken and by what, and whether what took them deserved them. Some weeks the answer justifies the loss — a real crisis outranks a thinking block, and the design was never meant to be a religion. But the audit is what keeps the exceptions from quietly becoming the rule. Over a month, the pattern tells you the truth about your job as it actually is: where your attention is genuinely consumed, which recurring demands should be delegated, redesigned, or refused, and how much thinking time your role truly gets. You cannot fix a week you have never looked at. Looked at weekly, it can be redesigned — which is to say, managed.

Start smaller than your ambition. One protected block, kept for three consecutive weeks, teaches more than a redesigned calendar abandoned by Thursday — it teaches you where the real pressure comes from, which defenses hold, and what the dividend feels like when a decision arrives at its meeting already thought through. Add the second block when the first is a habit rather than a hope. The focused week is not built in a planning session. It is built the way the work itself is done: in kept appointments, one week at a time.

Focus for a manager is not withdrawal from the team. It is the discipline that makes the manager worth interrupting the rest of the time.

← All Insights