Skip to content
UX Atlas
Plate BIAS·004 · Cognitive biasGrid A1 · Rev. 2026-08-14

Default Effect

Most people accept whatever is preselected, which makes defaults the most powerful control in an interface.

Cognitive biasEstablished researchFoundational

Definition

The tendency to stay with a preselected option. Johnson and Goldstein's 2003 analysis of organ donation rates across European countries found dramatically different participation between opt-in and opt-out defaults, with otherwise similar populations.

Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.

On this plate
  1. 1Definition
  2. 2Defaults are decisions you make for people
  3. 3Choosing a good default
  4. 4Choosing a default
  5. 5In practice
  6. 6Commonly confused with
  7. 7Local chart
  8. 8Sources
  9. 9Continue from here

Reach for this when

  • Setting any initial value, toggle or sort order.
  • Designing consent, privacy or billing choices.
  • Auditing settings for defaults nobody chose deliberately.
  • Any setting, sort order or preselection that most people will never change.

Common mistakes

  • Pre-ticked consent.
  • Defaults chosen for implementation convenience.
  • Asking again after the user has already expressed a preference.

Defaults are decisions you make for people

Every preselected value, every toggle position and every sort order is a decision the product makes on the user's behalf, and most users will accept it. Treating defaults as an afterthought means shipping a large number of unexamined decisions.

The design obligation is to choose the default that is best for the user in the common case, and to make changing it easy and visible.

Choosing a good default

  1. 1.Identify the most common case with data, not intuition.
  2. 2.Prefer the safest option where the cases are close, particularly for anything involving privacy, money or data sharing.
  3. 3.Make the default visible rather than implicit, so acceptance is informed.
  4. 4.Make changing it a single obvious action.
  5. 5.Remember the change, so a user who chose differently is not asked again.

Choosing a default

QuestionIf the answer is unclear
What would most people choose with full information?You do not have a default yet. Find out
Who benefits from this default?If the answer is only you, it is not a default, it is a nudge
What does being wrong cost the reader?High cost means no default. Make them choose
Is it reversible?If not, it should not be preselected
Is it lawful?Consent, marketing and tracking have explicit rules. Check them

In practice

  1. i.

    Privacy defaults

    Social products

    Defaulting new accounts to the most private setting and letting users open up deliberately is the choice that respects the effect rather than exploiting it.

  2. ii.

    Sensible sort orders

    Lists and tables

    Most users never change the sort. Choosing the order that answers the most common question, rather than the one that is easiest to implement, is a meaningful design decision.

  3. iii.

    The sort order that was a business decision

    Invisible defaults

    A results page defaulting to sponsored first is a default nobody chose and most readers never notice. It is also the single most consequential design decision on the page.

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.

vs.

Status Quo Bias

Cognitive bias

People prefer the current state to alternatives, beyond what the difference justifies.

Key difference

The default effect is about the preselected option being accepted. Status quo bias is the broader preference for however things are now, which persists even when nothing is preselected and is why redesigns start in deficit.

Use Default Effect when

  • There is a specific preselected value you control.
  • The question is opt-in against opt-out.
  • The ethical weight sits on which default you picked.

Use Status Quo Bias when

  • The complaint is about a change, not about an option.
  • You are planning a migration, a rollout or a deprecation.
  • Nothing is preselected and people still will not move.

Learn about Status Quo Bias

Local chart

BIAS·004 · Region I · Grid A1

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Hick's LawLAW·001 · EXPLAINSParkinson's LawLAW·013 · EXPLAINSTesler's LawLAW·005 · EXPLAINSDeceptive PatternsPRIN·011 · EXPLAINSCheckboxCMP·005 · APPLIED THROUGHRadio GroupCMP·006 · APPLIED THROUGHSelectCMP·004 · APPLIED THROUGHSettings and PreferencesPAT·025 · APPLIED THROUGHSortingPAT·005 · APPLIED THROUGHPermission RequestsWRT·014 · APPLIED THROUGHStatus Quo BiasBIAS·005 · COMMONLY CONFUSED WITHReducing Notification Volume Without Losing SignalCASE·007 · PRACTICAL EXAMPLE

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    Do defaults save lives?

    E. J. Johnson and D. Goldstein, Science, 2003

  2. [2]

    General Data Protection Regulation, Article 4(11) and Recital 32

    European Union, 2016

    Establishes that consent requires a clear affirmative act, ruling out pre-ticked boxes.

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.

Applies when you are designing

Settings

Explains

The mechanism underneath these entries.

Applied through

Where this shows up as a concrete interface decision.

Practical example

A worked decision where this was the deciding factor.

Check your work

Review passes that test whether this was done properly.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.