Decision fatigue is what happens when the number of choices you route through one person — you — outruns your capacity to make any of them well. It doesn't announce itself. It looks like a stalled afternoon, a tab you keep reopening, a decision you have "almost made" for three weeks, a 9pm scroll instead of a real call on pricing. It is a volume problem before it is a willpower problem, and volume is measurable.
Key takeaways
- Decision fatigue is a throughput problem: too many choices are routed through a single decision-maker, and the fix is structural, not motivational.
- The five mistakes that quietly amplify it are treating reversible decisions as irreversible, having no default for recurring choices, deciding without a named owner, keeping no record of what you decided, and spending your sharpest hours on low-stakes calls.
- Every one of those mistakes has a countermeasure — a rule, a default, a boundary, a log, an energy map — that lowers the count instead of merely reorganising it.
- You cannot fix a number you have never measured, which is why the first step is counting your decisions and putting a weekly cost against the queue.
The five mistakes that amplify decision fatigue
Almost every founder can describe their busy. Very few can describe their decision load, because it never appears on a calendar. It hides inside meetings, inside replies, inside the tiny approvals you make between two other things. Here is where it accumulates.
1. You treat reversible decisions as irreversible
The cost of a reversible decision is rarely the decision itself. It's the queue behind it. A call that takes ninety seconds to make and ninety seconds to undo gets parked for two weeks, and while it sits there it generates secondary decisions: should I follow up on that, should I chase the vendor, should I mention it on Friday. One parked decision becomes five.
The fix: before you open a decision, ask what it costs to undo. If the answer is an email and an apology, make it now. Write the rule down: any decision that can be reversed in under an hour gets made the same day it's raised.
Where to see the cost: most of what shows up in your urgent-problems column is debris from decisions that sat too long. When you put a weekly figure against that column, you're pricing your own hesitation rather than someone else's failure.
2. You have no default for recurring choices
Recurring decisions get re-decided from scratch every time. Which meetings you accept. What your intake email says. Whether you take calls before ten. Whether you approve spends under a certain amount on the spot. Each one is trivial. Collectively they are the background hum of your entire week.
The fix: give every recurring choice a default. A default is not a rigid rule you can never break — it's a starting position you override deliberately, and only once, instead of negotiating with yourself daily.
3. You decide without a clear owner
"We should sort out the pricing." Who decides? If the answer is "us, at some point," the decision will be reopened at least once, usually in a different meeting with slightly different people and slightly different information. Shared ownership is not ownership; it's a subscription to the same conversation.
The fix: every open decision gets one name and one date. The name isn't the person who does the work — it's the person who makes the call. Everyone else supplies input, not a veto.
Where to see the cost: loops like this are exactly what the free RADAR calculator at https://tools.exiuss.com/radar is built to price. It takes six inputs and turns the hours you lose to re-litigated decisions into an annual figure you can actually argue with.
4. You keep no decision journal
Without a record, you re-litigate. Six weeks later someone asks why you chose that vendor, and you rebuild the reasoning from memory — usually while quietly second-guessing it — and the decision opens back up. The thinking was done once and paid for once; without a log, you buy it again.
The fix: a decision journal is one running document with five columns: date, decision, owner, reasoning in a single line, and the condition that would make you revisit it. That last column is what stops the reopening.
5. You ignore your energy peaks
Decision quality is not flat across a day. If you spend your sharpest two hours on inbox triage and then make the pricing call at four in the afternoon, you have inverted your own org chart.
The fix: protect your peak block for the one or two decisions that genuinely move the business. Push everything reversible and low-stakes into the trough.
The arithmetic, with your own numbers
Consider an illustrative week, not a benchmark: a founder logs eighty decisions across five working days — replies, approvals, small purchases, "should I say something" moments. Apply the fixes. Twenty recurring choices get defaults. Fifteen get delegated with a written boundary. Twelve collapse because a decision rule says reversible calls get made the same day. Six stop being decisions at all, because the owner column now contains a name that isn't theirs. The count drops from eighty to the mid-twenties.
The percentage matters far less than the mechanism. The load was countable, the levers were specific, and the reduction came from structure rather than from trying harder. Run the same exercise with your own numbers and you get your own figure — then multiply the reclaimed hours by what an hour of your attention is actually worth to the business.
| Mistake | Structural fix | What it removes |
|---|---|---|
| Reversible decisions treated as permanent | Two-way door test, same-day rule | The queue behind small calls |
| No default for recurring choices | Written defaults you override deliberately | Daily re-negotiation with yourself |
| No named owner | One name and one date per decision | Reopened conversations |
| No decision journal | Five-column log with a revisit condition | Rebuilding reasoning from memory |
| Ignoring energy peaks | Peak block reserved for high-stakes calls | Bad calls made at the wrong hour |
A 30-day plan to cut your decision count
Week 1 — Count and cost. Log every decision you make for five working days. No editing, no filtering. At the end, mark each one recurring or one-off, and put a weekly cost against the hours the queue consumed.
Week 2 — Rules and defaults. Pick the three mistakes doing the most damage and write the countermeasure: a same-day rule for reversible calls, a default for each recurring choice, a named owner on everything still open.
Week 3 — Boundaries and delegation. Hand over the decisions someone else should be making, and write the boundary explicitly — what they can decide alone, what comes to you, and what triggers a check-in. Vagueness is what pulls the decision back to your desk.
Week 4 — Log and protect. Start the decision journal. Block your peak hours for the highest-stakes call of the week and defend the block. Recount your decisions and compare it to week one.
Where to start
The first move is not a new system; it's visibility. Put your six inputs into the free RADAR bottleneck cost calculator at https://tools.exiuss.com/radar and let it price the weekly chaos cost, the urgent problems, the missed revenue and the tools you're paying for and not using. The numbers are yours, which is precisely why they're hard to argue with.
Quick checklist
- Log every decision for five working days in one document, unfiltered.
- Tag each entry as recurring or one-off.
- Write defaults for the ten recurring choices that appear most often.
- Put one name and one date on every decision still open.
- Create a decision journal with a revisit-condition column.
- Reserve your peak two hours for the highest-stakes call of the week.
