The daily two-hour execution block

A daily two-hour execution block is a fixed, recurring calendar appointment — same time every working day — reserved for the one piece of work that moves the business forward rather than merely keeps it running. Two hours is long enough to finish something meaningful and short enough to defend against a client-facing diary. Protected properly, it produces roughly ten hours of genuine progress a week, which is more than most founders of 5–50 person firms currently get.

I run Total Format on this block. It is the load-bearing habit in my personal operating system, and everything else — reviews, decision rules, boundaries — exists partly to keep it intact.

Why two hours and not four?

Because two hours survives contact with a service business and four hours does not. A founder with clients, staff and a pipeline cannot reliably clear half a day; the block gets moved, then moved again, then quietly abandoned. Two hours fits before the first client call or after the last one, and a block that happens daily at 80% reliability beats a heroic block that happens twice a month.

There is also a focus argument. Most people get one, perhaps two, stretches of genuinely sharp attention per day. Scheduling more deep work than your attention can fund is planning fiction. Two hours matches the asset you actually have — which is why I treat energy, not time, as the real constraint and place the block where my energy peaks, not where the diary has a gap.

What goes into the block?

One category of work only: building. Not email, not admin, not client delivery — those have their own homes in the day. The block is for work that compounds: writing the sales asset, building the outbound campaign, documenting the process, fixing the system that keeps generating the same problem.

The test I use: if I stopped doing this task for a month, would the business be structurally worse, or just untidier? Structural work goes in the block. Untidiness gets batched elsewhere.

The block also holds exactly one task per day, decided the evening before. Choosing at 8am is a decision made with your worst judgement of the day, and an undecided block becomes an inbox session within minutes.

How do you actually protect it?

By rule, not willpower. The mechanism runs like this:

1. When the week is planned, the block goes into the calendar first, before any meeting — it is the anchor, everything else fits around it.
2. When someone requests that slot, then the booking link simply does not offer it; nobody is refused, because nobody sees it as available.
3. When a genuine emergency lands, then the block moves within the same day rather than being cancelled — moved is recoverable, cancelled is precedent.
4. When the block starts, then the phone goes in another room and every inbox tab closes; the task file is already open from the night before.
5. When the block ends, then I write one line on what got done and what's next, so tomorrow's block starts warm rather than cold.

None of this requires discipline in the moment. The decisions were all made earlier, which is the point — the block is a boundary designed as a system, not a daily act of assertiveness.

What happens when the block gets broken?

It will get broken, and the system should assume so. My rule is a repair standard, not a purity standard: a missed block is rescheduled within 24 hours or explicitly written off with a reason. Two consecutive written-off blocks trigger a diary review, because two misses is not bad luck — it is a scheduling defect.

What I do not do is extend tomorrow's block to four hours to "catch up". Debt-based scheduling collapses quickly. The block's power is its sameness; treat every day as a fresh two hours.

How do you know it is working?

Count outputs, not hours. Over a month, ten blocks should produce visible artefacts: pages shipped, campaigns launched, processes documented. If the blocks are happening but nothing ships, the problem is task selection, not focus — you are polishing rather than finishing.

The other measure is what the block frees you from. Once the building work has a protected home, delegation and automation become easier to justify elsewhere in the week. I am direct with clients about this: most AI automation succeeds or fails on whether the owner has the standing capacity to specify and review it. The two-hour block is where that capacity comes from.

Start Monday. Same two hours, five days, one structural task per day, decided the night before. Review after four weeks and count what shipped.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.