Decision Fatigue
The claim that decision quality degrades over a sequence of choices. Popular, intuitive, and on much shakier experimental ground than its usage suggests.
Definition
Decision fatigue describes deteriorating judgement across a run of decisions: more defaulting, more deferral, more avoidance. The underlying ego-depletion research failed to replicate at scale, so treat it as a plausible description of an experience rather than a measured effect with a known size.
Mixed evidence. Real research exists, but findings conflict, effect sizes are small, or the jump from the lab to interface design is contested.
On this plate
Reach for this when
- A flow asks for many consecutive judgements.
- Deciding where in a sequence to place a consequential choice.
- A setup or configuration flow asks many questions in one sitting.
Common mistakes
- Presenting it as settled research.
- Using it as cover for removing options people need.
What the evidence actually supports
The idea comes from ego-depletion research, which reported that exerting self-control on one task degraded performance on the next. A large multi-laboratory replication found effects close to zero, and the literature has been through a long public correction since.
What survives is narrower and still useful: sustained attention has costs, long sequences of comparisons are tiring, and people do default more as a session goes on. The disputed part is whether a specific reservoir is being depleted, and whether the effect size justifies designing around it.
The practical consequence is the same either way: shorten sequences of unsupported decisions. That advice is supported by choice-overload work and by basic attention research, neither of which depends on ego depletion being real.
Designing for long decision sequences
Do
- Set sensible defaults, so a decision can be accepted rather than made.
- Order decisions so the consequential ones come while attention is fresh.
- Save progress, so a sequence can be abandoned and resumed without loss.
- Reduce the number of comparisons, not just the number of options.
Do not
- Do not cite decision fatigue as established science in a design argument. The replication record will not support it.
- Do not use the concept to justify removing meaningful choice.
- Do not place the highest-stakes decision at the end of a long flow, whatever the mechanism turns out to be.
Designing a long sequence of choices
Do
- Order the decisions so the consequential ones come while attention is fresh.
- Provide defaults for the rest, and say what they are.
- Let people save and return without losing position.
- Group related choices, so one frame of mind covers several.
Do not
- Put the most important choice at the end of forty screens.
- Cite the effect as a measured mechanism. The underlying research did not replicate well.
- Use apparent fatigue as an argument for removing choices people need.
In practice
- i.
Configuration sequences
An enterprise setup wizard asking forty consecutive decisions sees rising acceptance of defaults as it proceeds. Whether that is depletion or simply declining motivation, the fix is the same: default what can be defaulted and move the irreversible choices earlier.
- ii.
The consequential choice at step nine
OrderingData retention, the one setting with a lasting consequence, sat at the end of a nine-step configuration behind eight cosmetic ones. Whatever the mechanism, it was answered with a default by almost everyone.
Commonly confused with
Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.
Cognitive Load
PsychologyThe working memory a task demands, split into intrinsic, extraneous and germane.
Key difference
Cognitive load is about capacity at one moment: how much a screen asks someone to hold at once. Decision fatigue is a claim about degradation across a run of choices, and its underlying research failed to replicate, so it carries less weight.
Use Decision Fatigue when
- The problem is the length of a run of choices, not one screen.
- You are describing an experience rather than predicting an effect size.
- The claim is stated with the replication caveat attached.
Use Cognitive Load when
- The problem is one screen asking too much at once.
- You can name what to remove, chunk or defer.
- You need an argument that will survive scrutiny.
Local chart
PSY·010 · Region I · Grid A1
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
A multilab preregistered replication of the ego-depletion effect
Hagger et al., Perspectives on Psychological Science, 2016
Found an effect size close to zero, which is the main reason this entry is not filed as established research.
- [2]
Ego depletion: Is the active self a limited resource?
Baumeister et al., Journal of Personality and Social Psychology, 1998
The original finding the popular version of decision fatigue rests on.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Explains
The mechanism underneath these entries.
- Hick's LawLAW·001 · Law
- Miller's LawLAW·004 · Law
- Progressive DisclosurePRIN·003 · Principle
Applied through
Where this shows up as a concrete interface decision.
- Multi-Step FlowsPAT·016 · Pattern
Related concept
Connected closely enough to change how you apply this.
- Default EffectBIAS·004 · Cognitive bias
- Choice OverloadPSY·002 · Psychology