Four episodes on why 'I have a great plan' and 'I'm executing the plan' are different problems. The plan is the easy part. Execution is a different skillset — sequencing, attention budget, the structural moves that make consistent action sustainable when motivation isn't reliably available. Format is conversational; the content is operational. By the end of episode four the listener has a working diagnosis of where their own execution breaks down — usually one of four patterns — and the structural fix that addresses it. Built for the operator who's tired of recommending books they read and didn't apply.

The book that treats execution as a designable system rather than a willpower problem. Covers the structural moves: how to break work into units small enough that starting isn't a decision (the actual atomic unit definition, not the marketing version), the sequence design that compounds across a week, the attention-budget model that explains why even good plans fall apart by Wednesday, and the failure mode catalog that names what's actually breaking when execution slips. Worked examples across project-based work, creative work, and the kind of operator work that's mostly recurring decisions. Built for the reader who's read the productivity canon and wants the next-level operational version.

The structured way to take a big project and break it into units small enough that starting tomorrow is automatic. Walks through the four-question decomposition that surfaces the actual first move (which is rarely the one in your head), the dependency check that catches the milestones masquerading as tasks, and the right-sizing test that distinguishes a unit small enough to start versus one that still needs decomposition. Run it once at the start of any project larger than two weeks. Most operators discover that what they thought was 'execution paralysis' was actually a decomposition problem in disguise.

The detailed framework behind the checklist. Covers the cognitive reason large projects feel overwhelming (your working memory is allocating slots to ambiguity, not to the work itself), the decomposition pattern that resolves it (concrete unit + concrete next step + concrete trigger), and the common failure modes — false granularity (units too small to be meaningful), false aggregation (units large enough to require their own planning), milestone-as-task confusion. Worked examples across launching a product, writing a book, and the recurring kind of weekly project most operators face. Pair with the habit-stacking guide for the daily-execution layer.

The structural guide to building habit chains that survive contact with a real week. Covers the trigger-anchor pattern (so the new habit doesn't compete for activation energy), the chain length sweet spot (most people try too long; the structural answer is shorter than you'd guess), the placement decision (morning versus context-dependent), and the recovery protocol for when the chain breaks (so a missed day doesn't end the system). Worked examples for morning routines, focus blocks, and the kind of recurring small actions that compound across a year. Built for the operator who's been through three productivity systems and wants the engineering version.

Twelve specific habit-stacking templates with the structural rules that make each one work. Not 'do X then Y' — the templates encode the trigger placement, the friction calibration, the recovery rule, and the typical failure mode for each. Read time about ten minutes. The value isn't picking a template; it's seeing twelve working examples close enough together that the underlying pattern becomes clear, after which you can build your own. Pair with the 'Build Your First Habit Molecule' guide for the structural framework underneath.

Seven failure modes that kill execution even when the plan is good. Perfectionism on the wrong move (polishing the email instead of sending it), unstructured time blocks (so 'work on the project' loses to whatever's loudest), missing accountability for any unit smaller than 'the project', the energy-budget mismatch (scheduling deep work into post-meeting slots), context switching tax not accounted for, the missing review cadence so wins and misses both go uncatalogued, and the absence of a recovery protocol so one missed day cascades. Each gets a specific structural fix; most operators recognise at least three.

Six daily emails, each pushing one specific structural move into your actual week. Day 1: time audit (the unflattering version). Day 2: priority surgery (the difference between urgent and important, applied). Day 3: the first habit molecule, deployed. Day 4: friction reduction on the work that matters most. Day 5: accountability infrastructure (so the system survives without willpower). Day 6: review and forward calendar. Designed to be uncomfortable in the right places — the value is in the actual mechanics, not the reading. By day seven the recipient has a working system or has identified exactly why they don't.