Make at least one structural adjustment before each high-demand period — push deadlines, reduce projects, or front-load preparation

Why This Is a Rule

Knowing that November is high-demand (Audit the past 12 months of calendar data — rate each month as low/baseline/high-demand/crisis to reveal recurring seasonal patterns) is useless without a structural response. The most common non-response is: "I know it'll be intense, but I'll just push through." This is the willpower fallacy applied to seasonal planning — believing you can absorb increased demand through effort alone. The result is the same every year: overcommitment, missed deadlines, burnout, and the promise to "plan better next time."

The structural adjustment must happen before the period arrives because adjustments made during a crisis are reactive and expensive (breaking commitments, disappointing people, emergency renegotiation). Adjustments made in advance are proactive and cheap (rescheduling a deadline by two weeks, declining a project that hasn't started, completing preparation during a calm period).

Three categories of structural adjustment cover most cases: Push deadlines (move non-critical deadlines out of the high-demand period into the following calm period), Reduce project count (Reduce commitments ~30% during high-demand months vs. baseline — match project load to measured seasonal capacity, not aspirational capacity: carry fewer active projects during high-demand months), Front-load preparation (use the preceding calm period to complete preparation work so the high-demand period only requires execution, not setup + execution).

When This Fires

• After completing the seasonal audit (Audit the past 12 months of calendar data — rate each month as low/baseline/high-demand/crisis to reveal recurring seasonal patterns) and identifying high-demand periods
• 4-6 weeks before each identified high-demand period
• When you feel the familiar dread of approaching busy seasons without having changed anything
• Complements Audit the past 12 months of calendar data — rate each month as low/baseline/high-demand/crisis to reveal recurring seasonal patterns (identify the pattern) with the action that makes the pattern manageable

Common Failure Mode

Awareness without action: "I know December is always crazy, but there's nothing I can do about it." There's almost always something: a deadline that could shift by two weeks, a project that could start in January instead of December, preparation that could happen in November's calm period. The "nothing I can do" frame is usually "nothing that's easy to do" — the adjustments require proactive negotiation, which feels harder than passive suffering.

The Protocol

(1) For each high-demand period identified in your seasonal audit, list all commitments and deadlines that fall within it. (2) For each commitment, ask: "Can this be moved to a calmer period? Can it be reduced in scope? Can its preparation be front-loaded?" (3) Make at least one structural adjustment per high-demand period. The minimum is one; aim for as many as practical. (4) Negotiate adjustments early (4-6 weeks before the period) when flexibility is highest. Last-minute renegotiation is harder and more disruptive. (5) Use calm periods actively: front-load preparation for upcoming high-demand periods rather than coasting. The calm period is your buffer for doing tomorrow's setup work today.