Time-Blocking for Executives: A Calendar System That Survives Real Weeks

The CEO of a 200-person SaaS company in Dublin shared his calendar with me in March. It was, by any objective measure, a disaster. Sixty-three meetings in the week, average length 38 minutes, gaps between them rarely exceeding 15 minutes. He had recently read Cal Newport's Deep Work, tried to implement time-blocking, and — three weeks in — had given up. "The blocks just don't survive contact with the week," he told me. "By Wednesday, everything's been rescheduled on top of what I planned."

This is the complaint I hear more than any other about time-blocking. The technique is straightforward on paper: block your calendar into pre-committed categories of work, stick to them, protect the blocks. The problem is that most time-blocking advice was written by people whose jobs were structurally compatible with time-blocking. Cal Newport is a tenured professor. Tim Ferriss is a self-employed author. Both have extraordinary control over their own calendars. Executives don't, and the standard advice breaks within a week under the pressure of a real operating role.

Here's the version that actually holds up for senior operators. It's less ambitious than the canonical time-blocking models and more robust in practice.

The Mistake at the Heart of Most Time-Blocking Systems

Most time-blocking advice tells you to block your calendar for the coming week on Sunday evening, in detail. Morning: deep work. Late morning: email. Afternoon: meetings. Evening: exercise. This works for people with predictable weeks. It fails for executives because the executive's week is fundamentally reactive — an unpredictable percentage of it will be consumed by things nobody knew about on Sunday evening.

The executive who plans Sunday evening with architectural precision spends Tuesday feeling like the plan is collapsing, Wednesday feeling guilty about the collapse, and Friday in a doom loop about whether time-blocking is a scam. The issue isn't the technique — it's that the technique assumes stability the job doesn't have.

The fix: plan the week in two layers. A fixed layer for the things that absolutely must happen, and a floating layer that flexes around reality. This is a smaller claim than full time-blocking, and it's the only version that actually survives.

The Two-Layer Model

Layer 1: Fixed — the non-negotiable blocks

These are blocked on Sunday evening and defended with near-military discipline. There should be three to five of them per week. Examples:

• Two or three deep-work blocks of 90 minutes, in the morning, on the mid-week days (Tuesday to Thursday)
• A weekly planning session (Monday 08:00 or Sunday 21:00 — pick one, commit)
• A physical activity block that matters to you — my current version is three gym sessions, 06:30 on Monday, Wednesday, Friday
• A weekly review block on Friday afternoon, 30 minutes

These are the skeleton of the week. When someone wants to book on top of them, the answer is no. Not "let me see" — no. The defence of these blocks is what makes the whole system work. If you move your deep work for a "quick catch-up" with a colleague on Tuesday, the next week your colleague will try it again, and within a month you've lost the block.

I keep the fixed blocks titled specifically in my calendar. "Deep work: Q3 strategy memo" is harder for a colleague to disrespect than "Focus time." The specificity signals you know what you're doing and you're not padding the calendar.

Layer 2: Floating — the everything-else

The rest of the week is filled tactically, day by day. On Sunday, I don't plan Thursday in detail. I plan Monday in detail, Tuesday in outline, Wednesday onwards in sketch. Then on Monday evening I plan Tuesday in detail, and so on.

This rolling 24-hour planning horizon is what absorbs the unpredictability. The Thursday that got hijacked on Wednesday by an urgent board call doesn't destroy the plan, because the plan for Thursday wasn't written until Wednesday evening anyway. You've effectively pre-committed only to the skeleton, and the muscle adjusts to what the week actually delivers.

The Categories That Should Exist in Every Executive's Week

Your floating blocks should cover a specific set of categories. If any of these is missing, something is going to fail.

• Deep work — the hard cognitive work that moves the business. Target 6-8 hours per week at minimum. This is already partially covered by your fixed blocks; add more if the calendar allows.
• 1:1s and team time — your direct reports need consistent access. Block consistent slots per person per week. These can flex, but the slot pattern should be reliable month to month.
• External meetings — customers, investors, partners. Cluster these into specific days to reduce context switching. Tuesday and Thursday are common choices.
• Admin and email — explicitly blocked, twice a day (mid-morning, mid-afternoon), rather than continuous.
• Thinking time — not deep work, but reflection. 30 to 60 minutes a week, usually a walk, to process where things stand. This is almost always the first thing that gets cut and the thing you miss most when it's gone.
• Buffer — deliberate unscheduled time. At least 10% of the week. This is where the overruns go, where the urgent calls happen, where you process what's really happening.

The buffer category is the one most executives refuse to create because it looks unproductive. It is not unproductive. It's insurance. Without it, the overruns push into your fixed blocks, and the whole system collapses.

The Calendar Hygiene Habits That Keep It Running

Decline, reschedule, or shorten

For any meeting invite that arrives, the first question is whether to decline. The second is whether to reschedule to a better slot. The third is whether 30 minutes can be 15. Most executives say yes by default and regret it. The default answer should be a polite push-back, with a specific alternative when declining outright.

A useful phrase: "I can do 20 minutes on Tuesday at 14:00. If we need longer, we should find time the following week." This signals your calendar is expensive, without being rude.

The weekly tidy

Friday afternoon, 30 minutes. Open next week's calendar. Look at everything that's been booked onto it by other people. Move, shorten, or decline the items that shouldn't be there. Block the deep-work sessions for next week before anyone else can see them.

This is the single most leveraged 30 minutes in the executive week. The Monday-morning you will thank you. The specific thing to look for: double-bookings the system has accepted, meetings that got rescheduled and are now adjacent to another commitment without a break, and the creep of standing meetings onto your protected morning time.

Auto-decline after a certain hour

I don't accept meetings after 17:00 unless there's a specific business reason (Americas timezone, emergency). Google Calendar and Outlook can both enforce this automatically. It seems rigid; in practice it saves you about three hours a week and trains your team to respect the hours that matter for home life.

What to Do When the System Breaks — Because It Will

Every four to six weeks, something will happen that blows the system up. A board crisis. A critical customer escalation. A reorganisation. The right response is not to blame the system — it's to run a contained recovery.

Contained recovery means: for one to two weeks, abandon the floating layer entirely and treat the calendar as reactive. But — this is critical — hold the fixed skeleton. If the three deep-work blocks and the weekly review survive the crisis, the system will reassemble inside two weeks. If they don't, you'll spend a month trying to rebuild the whole thing from scratch.

In the Dublin CEO's case, the fix wasn't more rigorous time-blocking. It was reducing his fixed layer from "90% of the week" to four specific blocks. He kept those four and let the rest float. Six weeks in, the deep-work output had tripled. The rest of the week was still chaotic. He didn't mind — he was getting his real work done.

The One Tool That Matters

The calendar app you use matters less than the habit. Google Calendar, Outlook, Cal.com, Calendly, Fantastical — they all work. The one feature that actually pays for itself is colour-coded categories. Deep work is one colour, external meetings another, 1:1s a third, admin a fourth. At a glance, on Monday morning, you can see whether the coming week is balanced or collapsing toward one category.

When the week looks heavily weighted toward meetings (which it will, most weeks), the visual cue is the prompt to decline or compress a few of them before the week starts rather than during it. Reactive defense works worse than preventive defense, every time.

The Limit to Honesty About

Time-blocking, even done well, doesn't solve the problem of too much work. If your role honestly has 65 hours of work a week and you're planning a 50-hour calendar, no amount of blocking rescues you. The system will collapse because the underlying demand is miscalibrated against the supply.

The only real fix there is to renegotiate scope — with your board, your CEO, your team. Time-blocking can reveal that the scope is wrong, because the blocks start overflowing with no slack. That's useful information. The response is not to block harder. The response is to cut scope. The executives who never do this are the ones who eventually burn out, and their time-blocking system did not fail them — their scope calibration did.