cognitive psychology
Decision fatigue
What is decision fatigue?
Decision fatigue is the way the quality of your choices degrades the more decisions you've had to make. Each one spends a little mental energy, so by the end of a long string of choices you're more likely to pick whatever's easiest, default to "no", or give up - not because you stopped caring, but because deciding itself is tiring.
Also known as: decision fatigue, choice fatigue
Prefer to watch?
Watch the recap 0:53
The demo
Set up the same order two ways. First answering every little question yourself - watch your energy drain. Then with the trivial choices defaulted away, so only the one that matters is left.
What this demo shows (text version)
The same order is set up two ways. In "every choice" mode you answer ten trivial decisions in a row - wrapping, this or that small option, and so on - and an energy meter drains a little with each one, so by the end you're worn down and inclined to just accept anything. In "designed" mode the trivial decisions are handled by sensible defaults and the screen asks only the single choice that genuinely matters, so the meter stays full and that decision gets your real attention.
That's decision fatigue: choices cost mental energy and the quality of later decisions falls as they pile up. The lesson is to treat decisions as a budget - remove, default or batch the ones that don't change the outcome, and spend the user's limited decision-making where it actually counts.
Every decision has a cost, and they add up. Make people choose too many times in a row and they don't get more careful - they get depleted: they take the default, pick the first acceptable option, or abandon the task entirely. So a flow stuffed with decisions late on (a checkout that asks question after question) bleeds completions near the finish. Spend the user's decisions where they matter, and remove, default, or batch the rest so the important choices land while there's still energy to make them well.
By the tenth trivial choice your patience is gone and you just want it over - that's decision fatigue, not impatience. The streamlined version makes the same outcome happen with a fraction of the decisions: smart defaults and batching carry the load, so your attention is left for the one choice that actually matters. Fewer decisions, better decisions.
The effect is why important choices are best made early and trivial ones removed entirely. As decisions accumulate, people shift toward the lowest-effort path - accepting defaults, choosing the first "good enough" option (satisficing), or quitting - so a process that front-loads easy decisions and saves a big one for the depleted end tends to get a worse answer or no answer at all.
In interfaces it shows up as drop-off near the finish line: long checkouts, multi-step sign-ups and settings walls that demand decision after decision lose people not at the start but late on, when the well is dry. The fix is to cut the number of decisions - sensible defaults, progressive disclosure, batching related choices, and pre-filling whatever you can - so each remaining decision is worth the user's energy.
Treat the user's decisions as a budget, not a free resource. Audit a flow by counting how many genuine choices it forces and where; eliminate the ones that don't change the outcome, default the common case, and reserve real choice for moments where it adds value. Reducing decisions usually raises both completion and the quality of the decisions that remain.