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.
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.