Design defaults for your actual self under realistic conditions — they must hold when capacity is low, not just when motivation is high

Why This Is a Rule

Most personal systems fail not because they're poorly designed but because they're designed for the wrong person: the idealized version of you who wakes up energized, has no competing demands, and never experiences low motivation. This aspirational self exists maybe 20% of the time. The other 80% — tired after poor sleep, stressed from work, depleted by emotional demands, fighting low energy — is your actual operating self, and it's the self your defaults must serve.

The mechanism is what behavioral economists call the planning fallacy applied to self-models: when designing systems, you systematically overestimate your future capacity and motivation. "I'll meditate for 30 minutes every morning" sounds reasonable from the planning self's perspective. But the executing self faces the 30 minutes at 6am after a rough night, and the default breaks instantly. A 5-minute meditation default would have survived because it was designed for the realistic worst case, not the aspirational best case.

Defaults that hold under low-capacity conditions automatically scale up under high-capacity conditions (on good days, you'll naturally exceed the minimum). Defaults designed for optimal conditions collapse under realistic ones, producing failure, guilt, and system abandonment. The asymmetry is critical: underspecify for resilience, not overspecify for ambition.

When This Fires

• When designing any personal default, routine, or behavioral system
• When a previously designed system keeps failing on "bad days"
• When you notice that your plans work well on weekends but collapse during stressful work weeks
• When reviewing why a habit streak broke — usually the default was calibrated to peak capacity

Common Failure Mode

The "good day" design trap: building your entire system around how you feel on your most productive, motivated day. The system works beautifully for a week (the novelty-motivation period), then collapses the first time life applies normal pressure. Each collapse erodes trust in systems generally, making the next attempt harder.

The Protocol

(1) For each default you're designing, ask: "Would I follow this after a terrible night's sleep, on a stressful workday, while fighting a cold?" If no → recalibrate downward until the answer is yes. (2) Use the 70% day as your design target: not your worst day, not your best — the day that represents your actual typical capacity including normal life variability. (3) Build expansion room: "Default is 10 minutes of writing; if energy permits, continue to 30." The minimum is the default; the maximum is the aspiration. (4) Test defaults for two weeks including at least one genuinely bad day. If the default survived the bad day, it's calibrated correctly. If not, reduce further. (5) Resist the urge to raise defaults after a string of good days — the next low-capacity period will break them.