Pre-decide at activity level…
Limit pre-decision scope to meaningful activity levels—what to eat, work on, when to exercise—not to fifteen-minute blocks, to avoid replacing decision fatigue with compliance fatigue.
Why This Is a Rule
Pre-decisions eliminate decision fatigue by resolving choices in advance. But pre-decisions applied at too fine a granularity create a different problem: compliance fatigue — the exhaustion of constantly checking whether you're "on schedule" and the stress of falling behind a rigid micro-plan. A day planned in 15-minute blocks produces 64 compliance checkpoints, each a potential failure that triggers guilt or re-planning overhead.
The optimal granularity is the meaningful activity level: "I'll write from 9-12, exercise at lunch, do admin in the afternoon." This resolves the high-level decisions (what to do when) while leaving within-activity flexibility intact. You don't pre-decide "9:00-9:15 outline, 9:15-9:30 draft paragraph 1" — you pre-decide "morning = writing" and let flow states, natural pacing, and in-the-moment judgment handle the within-activity sequencing.
The mechanism parallels Csikszentmihalyi's flow research: flow requires a balance of challenge and autonomy. Pre-decisions at the activity level provide direction (what to do) without constraining autonomy (how to do it). Pre-decisions at the micro-interval level constrain both direction and autonomy, preventing flow entry and producing compliance monitoring instead of productive engagement.
When This Fires
- When designing a pre-decision system and choosing what level of detail to pre-commit
- When an existing pre-decision system feels oppressive rather than liberating
- When time-blocking has become a source of anxiety rather than focus
- When you spend more time managing your schedule than executing it
Common Failure Mode
Productivity-system escalation: "If pre-deciding activities helps, pre-deciding every 15-minute block must help more." The logic seems sound but inverts the actual effect. Each additional layer of pre-decision adds compliance overhead that eventually exceeds the decision fatigue it was meant to eliminate. The system becomes the burden.
The Protocol
(1) Pre-decide at the activity level: "Morning: deep work on project X. Afternoon: meetings + admin. Evening: exercise + reading." (2) Leave within-activity sequencing to in-the-moment judgment — your focused self is better at micro-decisions than your planning self. (3) If you catch yourself scheduling sub-hour blocks for routine activities, zoom out: what's the activity? Pre-decide that, delete the micro-blocks. (4) Reserve micro-scheduling only for external coordination (meetings with others have to be timed) or one-time complex sequences (travel logistics). (5) Test: does your pre-decision system feel like a helpful guide or a compliance monitor? If the latter, you've gone too granular.