Open weekly planning by reviewing plan vs. actuals — identify the single biggest gap without judgment, then make one structural fix

Why This Is a Rule

Weekly planning without retrospective review is flying blind — you make the same planning errors every week because there's no feedback loop connecting your plans to their outcomes. You chronically overcommit on Mondays, discover this on Fridays, and repeat the identical overcommitment the following Monday because no mechanism forced you to confront the gap.

The plan-vs-actual review creates this feedback loop by making the gap between intention and reality explicit and visible. "I planned 5 deep work sessions; I completed 2." "I planned to finish the proposal; I got through the outline." These gaps aren't failures to guilt about — they're data points about your planning accuracy and structural constraints. The "without judgment" framing is essential: judgment triggers defensiveness ("But the meeting was unexpected!") that prevents honest pattern recognition.

The "single biggest gap" constraint implements Exactly one improvement per execution cycle — not zero, not three — so you can attribute changes to effects's one-improvement-per-cycle principle at the weekly level. Multiple gap analyses produce overwhelm and scattered fixes. The single biggest gap focuses attention on the highest-leverage adjustment: the one structural change that would have the largest impact on next week's plan-actual alignment. Over 50 weeks of single-gap-focused improvements, your planning accuracy transforms.

When This Fires

• At the start of every weekly planning session, before creating next week's plan
• When weekly plans consistently don't match reality but you're not sure why
• When planning feels futile because "nothing goes as planned"
• Complements Exactly one improvement per execution cycle — not zero, not three — so you can attribute changes to effects (one improvement per cycle) and Give each workflow change 3-5 executions before deciding to keep, modify, or revert — distinguish signal from noise and prevent oscillation (3-5 cycle stability test) at the weekly cadence

Common Failure Mode

Forward-only planning: jumping straight into next week's plan without reviewing last week's outcomes. This feels efficient ("I don't want to dwell on the past") but ensures you repeat every planning error indefinitely. The 5-minute review is the cheapest learning investment in your weekly practice.

The Protocol

(1) Open your weekly planning session by pulling up last week's plan alongside this week's actuals. (2) Compare each planned item against what actually happened: completed, partially completed, not started, or replaced by something else. (3) Identify the single biggest gap — the one item where plan and reality diverged most significantly. (4) Ask: "What structural factor caused this gap?" Not "why didn't I do it?" (blame) but "what structural condition prevented this from happening?" (schedule conflict, underestimation, missing prerequisite, energy mismatch). (5) Design one structural adjustment for next week's plan that addresses this factor. Then proceed with planning. The review should take 5-10 minutes, not the entire session.