Decision Fatigue Is a Calendar Design Problem
Decision fatigue is real enough as a felt experience even when researchers argue about the lab version. By late day, people pick defaults, snacks, and safe little yeses that create big messes.
If your evenings are full of avoidable regret, look at the calendar, not your character.
Design rules that reduce decision load
- Theme the days where possible (Meetings / Make / Admin / People).
- Default the small stuff (lunch, workout slot, clothing, first task).
- Batch approvals into one window instead of dripping all day.
- Cap meetings with a hard daily number.
- Put irreversible decisions in your high-energy window, not after dinner.
The 4 p.m. rule
After your typical crash hour, only allow:
- pre-decided execution
- low-risk admin
- conversations that are restorative, not evaluative
Do not negotiate prices, fire people, or redesign strategy when your brain is borrowing against tomorrow.
DISC flavors of fatigue
- D: fatigue looks like blunt damage
- I: fatigue looks like oversharing and overpromising
- S: fatigue looks like silent yeses
- C: fatigue looks like endless re-checking
Same fuel tank, different leaks.
A one-week experiment
Pick three recurring decisions and default them for five workdays. Measure subjective evening regret. Most people do not need a sabbatical. They need fewer open loops dressed up as freedom.
If your afternoons feel stupid, redesign tomorrow's calendar tonight. Decision quality is often just architecture.