THE IDEA
The battery that drains
Making decisions uses a finite resource. Each choice - from what to wear to whether to approve a budget - draws from the same pool. As the pool depletes through the day, the quality of decisions deteriorates. Not because you become less intelligent, but because you become less careful. The shortcut becomes more attractive. The default becomes harder to resist. The difficult conversation gets postponed. The impulsive choice feels fine.
Decision fatigue is a property of how human cognition works, not a character flaw. Judges grant parole at higher rates in the morning than in the afternoon. Shoppers make worse purchasing decisions later in a shopping trip. Doctors prescribe more antibiotics at the end of the day - not because the patients are sicker, but because saying yes is easier than explaining why no.
The implication for systems design is significant. If the quality of decisions is time-dependent, then when decisions are made matters as much as how they’re made. Scheduling important decisions for the morning, reducing the total number of decisions required, and creating structures that compensate for fatigue aren’t luxuries. They’re rational responses to a cognitive system that degrades with use.
IN PRACTICE
When the mind gets tired
A leadership team holds its strategy review at the end of a day-long board meeting. By the time the strategy conversation begins, everyone has been making decisions for eight hours. The discussion is superficial, dissent is minimal, and the team defaults to the status quo. Not because the strategy is right, but because challenging it requires energy that’s been spent. The same conversation at 9am on a fresh day would produce a completely different quality of engagement.
A parent at the end of a long day. The child asks for screen time, another biscuit, to stay up late. Each request, earlier in the day, would get a considered response. By 7pm, the parent has made hundreds of decisions since waking. The answer to everything becomes “fine.” The rules that felt important in the morning become negotiable by evening. The child hasn’t worn them down strategically. The day has worn them down systematically.
A software developer making code architecture decisions. The morning choices are clean, well-reasoned, and future-proof. The afternoon choices are functional but shortcuts. The evening choices introduce technical debt that the morning self would never have accepted. The code quality degrades through the day because the decision quality degrades through the day.
WORKING WITH THIS
Protecting your best decisions
Schedule important decisions early. Not just “in the morning” but before the day’s accumulated choices have depleted the resource. If a decision matters, give it your freshest attention.
Reduce the total number of decisions. Routines, defaults, and automation aren’t boring - they’re protective. The famous example: leaders who wear the same outfit every day aren’t eccentric. They’re eliminating a decision to preserve capacity for decisions that matter.
Design systems that compensate for fatigue. If decisions must be made late in the day, build in safeguards: checklists, cooling-off periods, required second opinions, default-to-no for irreversible choices. Don’t rely on tired humans to maintain the standards that fresh humans set.
THE INSIGHT
The line to remember
You don’t get worse at thinking as the day goes on. You get worse at caring about thinking well - and that’s more dangerous.
RECOGNITION
When this is in play
You’re seeing decision fatigue when important decisions are rushed at the end of long meetings. When standards that were firm in the morning become flexible by evening. When people default to the easiest option rather than the best one. When the quality of choices deteriorates predictably with time. When someone says “let’s just go with it” about something they would have questioned three hours ago.