When to Check Willpower
Five moments when knowing your battery level changes the next move.
Decision Fatigue fires before every heavy call — and after every bad one, for diagnosis.
Willpower is a budget you do not see until you have spent it. The tool fires at five specific moments — before the big calls, to protect capacity; after bad calls, to diagnose. Outside these moments, daily battery-watching becomes its own anxiety.
Quick answer
Decision Fatigue fires before every heavy call — and after every bad one, for diagnosis.
Key points
- ▸ Before a heavy decision. Check the battery first. Below 45%? Defer if possible. You will default, and defaults from a low battery are usually wrong.
- ▸ Scheduling important conversations. If the hard talk falls at 4pm after a day of meetings, move it to 10am. Free willpower is the same as an extra hour of prep.
- ▸ After a bad decision. Was the battery drained when you made it? If yes, the fix is scheduling, not character.
- ▸ During a run of small decisions. Meal choices, wardrobe, trivial work decisions. At some point batching them (meal prep, uniform wardrobe) protects heavy-decision capacity.
- ▸ End-of-day retrospective. What decisions did you make in the last 2 hours? If they were heavy and the battery was < 30%, revisit them with fresh capacity tomorrow.
Examples
- Pre-negotiation checkBattery at 35% before 2pm salary call. Defer if possible; otherwise eat, walk, rehearse. Every restored 10% is worth hours of prep.
- Post-bad-decision diagnosisMade a weird hire at 6pm Friday. Battery was ~15% by then. The hire is a willpower artifact; revisit Monday morning with a full charge.
- Small-decision batchingBreakfast + outfit + lunch decisions = ~3 trivial drains daily. Batch (meal prep Sunday, wardrobe uniform) → +9 willpower/week available for heavy calls.
When to use which tool
- Decision Fatigue · Willpower BatteryAt the five triggers. Not daily — daily tracking is itself willpower drain.Model remaining willpower across the day. Every decision draws from the same finite reserve — trivial × 1, moderate × 5, heavy × 10.
- Deep Work Capacity · Focus HorizonWillpower and focus decay on overlapping curves — low battery + low horizon = stop working.Exponential decay model of focus quality. e^(−0.01×min) half-life ≈ 69 minutes — the horizon shows how long until quality drops below usable.
- Task Switching Tax · Context OverheadContext switches drain willpower; batching them protects the battery.Calculate the hours per day you lose to juggling concurrent projects. Each additional context costs 20% of remaining capacity — CPU-usage view.
Related
- Decision Fatigue · Willpower BatteryModel remaining willpower across the day. Every decision draws from the same finite reserve — trivial × 1, moderate × 5, heavy × 10.
- Deep Work Capacity · Focus HorizonExponential decay model of focus quality. e^(−0.01×min) half-life ≈ 69 minutes — the horizon shows how long until quality drops below usable.
- Task Switching Tax · Context OverheadCalculate the hours per day you lose to juggling concurrent projects. Each additional context costs 20% of remaining capacity — CPU-usage view.
- What Decision Fatigue CalculatesWillpower = 100 minus Σ(decisions × weight). Trivial ×1, moderate ×5, heavy ×10.
- Five Decision-Fatigue MistakesThe errors that make your battery look fuller than it is.
- When to Set a Focus HorizonFive situations where marking the decay curve changes what you ship.
Frequently asked questions
› Should I track willpower hour-by-hour? Trust & accuracy
No. Hourly tracking is micromanagement that drains the battery it measures. Check at the five triggers; trust the pattern between them.
› What if I cannot defer a heavy decision on a low battery?
Restore before deciding where possible (glucose, 20-minute break, sleep on it if hours-not-minutes allow). If truly forced, write the decision down with the reasoning; heavy decisions made under low battery should be reviewed within 24 hours.
› How should I use a decision framework in real life? How-to
Use a decision framework to expose the tradeoff, not to outsource the decision. Write down the inputs, compare the output with your constraints, then ask what would change the answer. The strongest use is scenario testing: base case, conservative case, and failure case.
› Is this financial, legal, or tax advice? Trust & accuracy
No, this is not legal, financial, tax, medical, or professional advice unless the page explicitly says that use case is supported. It organizes assumptions so you can inspect them. Verify high-stakes choices with qualified people who can review facts, contracts, regulations, and downside risk.
› What assumption matters most in a decision model? Edge case
The most important assumption is usually the one you are least certain about and most emotionally attached to. Change that input first. If the recommendation flips after a small change, the decision is fragile and needs more evidence before you treat the model as useful.