Deep Work Blocking

Deep Work Blocking Skill

Focus blocks fail three ways: placed wrong (2pm slump hosting the hardest work), defended badly (the block that moves for every invite is decoration with a border color), and entered badly (twenty minutes of warmup-shuffling inside a 90-minute block is a 70-minute block wearing a lie). The design fixes all three: blocks land on the user's actual high-energy hours (energy-scheduling supplies the map), carry explicit defense tiers (what outranks them — almost nothing — and the decline scripts), and start with an entry ritual — the named task waiting, the environment pre-set — because a block is a container, and containers need contents chosen before the clock starts.

What This Skill Produces

• The block design — count, length (90–120 min beats the 8-hour fantasy), and placement on real energy hours
• The defense tiers — what moves a block (genuine emergencies, defined), what never does, and the decline scripts
• The entry ritual — the task named the day before, the environment checklist, the first-five-minutes rule
• The culture negotiation — making blocks legible to the team (the shared norm beats the solo fight)

Required Inputs

Ask for these if not provided:

• The energy reality — when the user's genuinely sharp hours fall (the honest answer, not the aspirational one); blocks on slump hours produce guilt, not work
• The calendar's constraints — the immovable meetings, the team's collaboration hours, the time zone spread; blocks live in the real grid
• The work that needs the blocks — the big-three outcomes (weekly-review-ritual) the blocks exist to serve; blocks without assigned work become email time with the door closed
• The interruption culture — can a block survive here socially? The negotiation section scales to the actual environment

Framework: The Blocking Rules

1. Size honestly, place on peaks: 90–120 minutes is the sustainable unit (attention's real budget); two such blocks is a strong day. The 8-hour focus fantasy collapses by 11am and discredits the practice. Placement follows the energy map — the best hours go to the hardest work first, before the calendar's entropy claims them (recurring-meeting-pruner reclaims supply this space).
2. Defense tiers, pre-decided: Tier 1 (never moves): the two weekly anchor blocks — invites get the script: "I have a commitment then — Thursday 2pm works?" (a block IS a commitment; the script just declines to itemize it). Tier 2 (moves for named things): the flex blocks, moved forward in the same week, never deleted. The emergency definition is written: production-down and boss-says-now qualify; "quick sync?" does not.
3. The entry ritual kills the warmup tax: the day before, the block gets its named task ("draft sections 2–3," not "work on the doc") · entry checklist: notifications off, the one document open, phone elsewhere · the first-five-minutes rule: start on the named task immediately, badly if necessary — momentum converts; browsing "to warm up" evaporates blocks whole.
4. Blocks are legible, not secret: the calendar shows "Focus block" (visible, normalized), the team knows the pattern ("mornings I'm deep, afternoons I'm reachable" — working-agreements material), and the async norms (async-update-format) carry what would have interrupted. The solo fight against a synchronous culture loses; the negotiated norm holds.
5. The block reviews itself: each block ends with 60 seconds — did the named task move? If blocks keep producing nothing, the diagnosis tree runs: wrong hours (re-place), wrong sizing (shrink), vague tasks (the naming discipline), or leaks (the defense failed — count what actually interrupted). Blocks that fail silently get quietly deleted by their owner within a month; the review is the early-warning.