Focus for managers: protecting thinking time between one-on-ones
Where does a manager's thinking actually happen? Not in the long, clear stretches that focus advice assumes. Run the post-mortem on a typical week and the pattern is unflattering: the one-on-ones happened, the decisions got made in corridors between them, and the thinking — the follow-ups promised, the patterns across five conversations, the decision that deserved an hour — got whatever was left, which was nothing. The week did not fail for lack of time. It failed because the gaps between meetings were treated as dead time and spent accordingly.
The manager's day has no long edges
The standard prescription for managers is a 90-minute deep-work block three times a week — 4.5 hours of protected thinking time — plus at least one half-day a week with no meetings. Keep that prescription; the next section is about the block, and it matters. But notice what it leaves out. A manager's calendar is built around one-on-ones, and the spaces between them — 25 minutes here, 40 there — add up to hours a week that most focus advice simply does not address, because the advice was written for schedules with long edges. Yours has short ones. The system below uses both: the gaps for follow-through, one protected block for decisions.
The gap harvest: 25 minutes used on purpose
A gap between one-on-ones is too short for a new project and exactly the right size for the work the one-on-ones generate. The procedure:
- Defend a minimum gap when scheduling. Back-to-back one-on-ones are a choice, not a law. Where you control the bookings, leave at least 15 minutes after each; where you do not, protect the gaps that exist and stop donating them to whoever asks first.
- Give every gap a single pre-assigned job. Before the first one-on-one of the day, write one line per gap: whose recap, which decision, which note to consolidate. A gap with an assignment survives. A gap left open gets spent on email.
- Start with the capture step, below, then do the assigned job. Capture takes three minutes. The rest of the gap belongs to the job — not to messages, not to “quick questions” that are neither.
- Close the gap standing up. End two minutes early, note where the next piece of work resumes, and walk to the next conversation with a clear head rather than a half-finished thought.
Success looks like this: at day's end, every one-on-one has a recap written, every promise has a home, and no gap was spent wondering what to do with it.
Capture follow-through before the next door opens
Action items slip when the next call starts immediately — that is the mechanical fact the whole habit is built against. So the first three minutes after a one-on-one ends are reserved, every time, for three entries in a single running note: what you promised, with its date; what they promised, with theirs; and the one thing you noticed that belongs in a later conversation. Then the recap itself goes out fast: a brief recap with action items should land within 24 hours of the meeting, and the capture note is what makes that a two-minute send instead of a reconstruction.
This is also where continuity is built. The trust a one-on-one runs on comes from returning to what you said you would do — coming back with the answer, or with an honest status when there is no answer yet. A manager whose gaps feed a follow-through list does that by default. A manager relying on memory does it until the busy week arrives, which is precisely when it mattered.
Frequently asked questions, answered early
Aren't the gaps for rest? Some are, and the system should say so. Mark one gap a day as genuinely off — no capture, no job. Harvesting every minute is a burnout schedule wearing a productivity costume.
What about a one-on-one with a thin agenda — cancel it? No. Protect the agreed meeting time rather than cancelling when the agenda looks sparse; the sparse weeks are often when the real topic surfaces. The same logic sits behind the cadence choice: a biweekly one-on-one that never gets cancelled beats a weekly one that is rescheduled half the time.
One protected block for decisions, not tasks
Gaps handle follow-through. They cannot handle a decision that needs an hour of unbroken thought, and pretending otherwise turns every decision into a corridor call. So keep one block of the standard kind — 90 minutes, inside the three-times-a-week pattern if your calendar allows, or a single weekly block plus a meeting-free half-day if it does not — and reserve it by rule for decisions only. Not status writing, not inbox clearing, not the small tasks that feel productive. Decisions: the reorg question, the hiring call, the priority trade-off you keep deferring.
Feed the block from the gaps. Every capture note that surfaces a decision too big for 25 minutes gets a line on the block's agenda, so when the block arrives, the work is already chosen. A decision block that starts with “what should this be for?” spends its first twenty minutes answering that — the gaps exist to prevent exactly that leak.
Defending the gaps when the calendar fills
Gaps get eaten from two directions. Other people book into them, because an unlabelled 30 minutes reads as free. And you donate them, because a gap feels too small to defend. Against the first: label the longer gaps on the calendar with their job — “Follow-ups from one-on-ones” is a purpose a scheduler can weigh, where a blank space is not. Against the second: apply a simple decision rule. A request may take a gap only if it is urgent for the requester today and cannot be a message. Failing either test, it waits for the next real opening, and the gap keeps its assignment.
Expect the defence to be tested most in the busiest weeks. That is not a sign the system is unrealistic. The busiest weeks are when follow-through decides whether the team trusts the calendar at all.
What thinking time is not
It is not a hiding place from the team — the one-on-ones stay fixed, protected, and uncancelled, and the gaps are spent largely on the work those conversations created. It is not a second inbox shift; messages get their own time elsewhere in the day. And it is not a reward for a finished week. It is the mechanism by which the week gets finished: promises captured before the next door opens, decisions given one honest block, and a manager who walks into each conversation carrying the last one's answers.
— Sterling Cole, Money Writer — Earning Desk