Why a default is planted exactly where attention thins
A default is planted where attention thins because a depleted user lacks resources to override it, making the pre-selected option the path of least cognitive resistance.
Filed by The Archivist 2 min read
Intuition test — answer before you read on
Why does placing a default later in a flow increase its acceptance rate?
Correct answer: A
Option B conflates noticing with overriding — users see the checkbox but lack resources to change it. Option C invokes earned trust, which is speculative. Option A is correct: ego depletion reduces the capacity for the active deliberation required to change a default.
A software installer placed its “recommended settings” checkbox on page six of a seven-page wizard. Acceptance of the default bundle — including a toolbar and a homepage change — was seventy-one percent on page six versus thirty-four percent when the same checkbox appeared on page one. The default did not change; the user’s ability to resist it did.
What everyone sees
Users believe they reviewed and accepted the settings. They describe the choice as “going with the recommended option.” The placement on page six is experienced as logical sequencing, not as a strategic decision to present the most profitable question after the user’s decision-making resources have been consumed by five prior pages.
What is actually happening
Johnson and Goldstein’s default-effect research showed that defaults are accepted at disproportionately high rates because changing them requires active deliberation — a resource that ego-depletion theory identifies as finite and consumable. Thaler and Sunstein’s nudge framework adds that defaults exploit the status-quo bias, which strengthens as cognitive resources decline. By page six, the user’s prefrontal budget for evaluation has been spent on earlier choices.
Why it stays hidden
The default hides because it looks helpful. “Recommended” implies the designer’s expertise, converting a commercial preference into an expert suggestion. The user interprets the pre-ticked box as a service rather than as a trap calibrated to the exact point in the flow where willpower is lowest.
The default is not a suggestion — it is a bet on the user’s fatigue. It sits where resistance has already been eroded, wearing the mask of a recommendation.
The default is not a suggestion — it is a bet on the user’s fatigue. It sits where resistance has already been eroded, wearing the mask of a recommendation.
Collect this card
The default is not a suggestion — it is a bet on the user’s fatigue. It sits where resistance has already been eroded, wearing the mask of a recommendation.
0 / 10,000 collected
Sources & further reading 2
- Johnson & Goldstein — Do Defaults Save Lives? (2003)
- Thaler & Sunstein — Nudge: Improving Decisions About Health, Wealth, and Happiness (2008)
Cross-references
Related files
Filed near this one in the index.
-
No visual on fileHabit Loops Entry #0310
The reason morning habits stick better than evening ones
The morning slot faces less competition. By evening the day has introduced alternatives, interruptions and a depleted capacity to override them.
MasterThe hidden part #0310The morning slot is not filled by discipline. It is defended by emptiness — the absence of alternatives that have not yet arrived.
Habit Open file -
No visual on filePrice Psychology Entry #0365
Why an annual plan hides the churn decision
A monthly cycle asks the customer twelve times whether to continue. An annual cycle asks once, and inertia answers on every day in between.
MasterThe hidden part #0365Retention is not only how much people want to continue. It is how often they are asked to decide.
Pricing Open file -
No visual on fileDecision Architecture Entry #0140
Why the checkbox already ticked is the business model
A pre-ticked box does not persuade anyone. It converts consent from something obtained into something not withdrawn, and inattention supplies the difference.
MasterThe hidden part #0140The default is not a suggestion. It is the answer given by everyone who does not answer.
Decisions Open file -
No visual on fileDecision Architecture Entry #0131
The reason you decide differently before and after lunch
Across a long session of similar decisions, the safe default is chosen more often as the session goes on. Why that happens is still argued about.
AdeptThe hidden part #0131Position in the queue is an unrecorded input. Effort-saving accumulates across a session while each case still gets a full justification.
Decisions Open file
Annotations are reserved for archive members.
Sign in to annotate