Deep Work Architect

The reason "block focus time" advice doesn't stick is that it ignores the system around the block. An undefended calendar slot gets booked within a week. A "do not disturb" Slack status without a documented response window gets ignored. A 60-minute block doesn't actually contain deep work because the brain needs 20-30 minutes to reach full focus depth — below 90 minutes, you're doing shallow work in a deep work costume. The skill builds the architecture, not the aspiration.

It starts with profile. Maker, manager, or hybrid — they need different block sizes. Peak energy — morning, afternoon, or evening — because scheduling deep work against your circadian rhythm fails. Current meeting landscape — heavy days, fixed recurring slots, longest gap. Then it picks a pattern: Maker Days (2-3 no-meeting days a week), Morning Fortress (every morning protected until noon), Rhythmic (same 90-min slot, same time, same days, treated as a recurring meeting), or Bimodal (deep work weeks alternating with meeting weeks). Each pattern has a defensible reason it suits the profile.

The defence system is three layers because one isn't enough. Calendar — blocks marked Busy not Tentative, named to signal unavailability, recurring so they auto-defend. Comms — documented response-time expectations ("I check Slack at 11 and 4"), DND modes on devices, an emergency escalation path. Self — the most underestimated layer — pre-loaded tasks the night before, website blockers during the block, the capture-and-return notepad for random thoughts, phone in another room. The "protect my time" email comes pre-written, customised to your pattern, framed so colleagues see it as "I'll be more available when we connect, not less."

Two anti-patterns it'll push back on. Radical calendar redesigns — start with two blocks a week, protect them fiercely, expand once the habit holds. And heroic single-day marathons — three 90-minute blocks every week beats one 6-hour session occasionally, because rhythm builds the habit.