Decision Fatigue
Decision fatigue is a design problem, not a discipline problem.
Repeated choices drain the ability to make good calls. The result: impulsive, avoidant, or overly conservative decisions as the day wears on. The fix is not willpower. The fix is fewer decisions routed through you.
Three Layers
Think of decision architecture as three stacked layers:
| Layer | Job | Effect |
|---|---|---|
| Principles | Clear rules for what matters | Options ruled out by default |
| Systems | Routines, automations, delegation | 80-90% of decisions happen without fresh thought |
| Surface | The remaining live decisions | Scored and batched at peak energy |
Most founders operate only at the surface layer. They burn decision fuel on choices that should never reach them.
Decision Constitution
Define 3-5 filters you always run non-trivial decisions through:
| Filter | Question |
|---|---|
| Stage goal | Does this move us toward cash, product maturity, or credibility this quarter? |
| Asymmetry | Is the upside meaningfully larger than the downside if we are wrong? |
| Reversibility | Easy to reverse? Bias to shipping fast. |
| Compounding | Does this improve a system or standard that pays repeatedly? |
For any non-trivial decision, you do not think from scratch. You run it through the filters and pick the highest score.
Standardize Defaults
Every trivial micro-choice costs fuel. Test: if you decide the same thing more than twice a week, it should become a rule, template, or automation.
- Food: Weekly meal pattern, 2-3 breakfast rotation
- Clothes: Weekday uniform, outfits picked the night before
- Admin: Autopay, default calendar blocks, recurring lists, saved tool presets
Time-Block Modes
"What should I do now?" is one of the most expensive invisible decisions.
- Block your day into modes: deep work, shallow work, meetings, admin, rest
- Assign categories, not tasks, to each block
- Put highest-stakes decisions in your best-energy window
- Run a schedule, do not reinvent it hourly
Delegate Decisions
Founders burn out when every road leads back to their judgment.
- Give people decision rights with guardrails: "You own X metric and can decide within Y budget without checking with me"
- Codify "if X, then Y" playbooks for recurring situations
- Hire for outcome ownership, not micro-approval
Your metric: how many decisions per week still require you personally? That number should trend down.
Pre-Commit on Surfaces
For recurring decision surfaces (what to build, who to hire, which leads to chase), pre-decide the process once:
- Clarify the decision in a single sentence
- Predefine inputs: specific metrics, feedback, constraints
- Score options with your filters
- Set a deadline so decisions do not squat in your brain
This turns decisions into a repeatable scoring game. Probabilistic at the edges, hardening into rules once you see what works.
The Hardware
Mental fatigue directly degrades decision quality and increases risk aversion.
- Sleep, food, movement as non-negotiable platform habits
- Intentional breaks between blocks
- Weekly review: how you actually spent time and energy vs what you say you value
You are designing a feedback loop where your week teaches your system where decision load really is.
Context
- Priorities — What you stop doing matters more than what you start
- First Principles — Strip to what must be true
- Systems Thinking — Feedback loops shape outcomes
- Process Optimisation — Standardize the repeatable
- Chain of Thought — Make reasoning visible
- Standards — The Principles layer is applied standardization. Rules you set once eliminate decisions forever
Links
Questions
Which decisions, once made, eliminate the most future decisions?
- If you mapped every decision you made this week, how many were genuinely novel vs repeated choices wearing a new mask?
- At what point does pre-commitment become rigidity — and how do you build the override valve?
- When your decision constitution conflicts with your gut, which signal is more trustworthy — and how do you know?