Both can make one option unusually sticky, but they are not the same. A default is the option or outcome that applies if no active choice is made. Status quo bias is the broader tendency to give extra weight to the option that is already current or in place.
Ask why one option is privileged: because the choice architecture makes it happen automatically, or because it is already the person's current state?
Question
Default Effect
Status Quo Bias
What creates the privileged option?
A form, policy, system or interface defines what happens if the person does not actively switch.
The person already has, uses or occupies one option, so change must be considered relative to the current state.
Does a designer have to set it?
Usually yes. Someone or some system defines the pre-selected or automatic outcome.
No. A current bank, workflow, software system or possession can become the status quo without anyone deliberately designing it as a nudge.
What does staying tell us?
It shows that the default influenced observed choice, but not necessarily that the person strongly preferred it.
It shows persistence with the current option, but that persistence may reflect bias, real switching costs, uncertainty or a genuinely better current option.
Best diagnostic
Compare the same choice with a different default or an active-choice condition while keeping the options otherwise comparable.
Ask what would be chosen if none of the options were already current, then add genuine switching costs back into the comparison.
Decision diagnostic
Review the decision without letting the result rewrite the past.
1
Identify exactly what happens if the person does nothing. If one option is automatically selected, you have a default to examine.
2
Identify whether the person already owns, uses or occupies an option before the choice begins. That is the status quo question.
3
Separate changing effort and real switching costs from familiarity, endorsement signals and simple inattention.
4
Do not infer strong preference only because many people stayed. Compare with active choice, another default or a no-status-quo version when the decision is important.
Same outcome, different bias
Three examples where the distinction matters.
Privacy settings
Default EffectA new account starts with personalised ads enabled unless the user changes the setting. The pre-selected state is the default.
Status Quo BiasA long-time user keeps an old privacy configuration after new options are introduced partly because the existing setup is already familiar and in place.
Work software
Default EffectA new tool opens with one workflow enabled automatically, so most users begin there unless they deliberately change it.
Status Quo BiasA team keeps its existing software during a migration review even when the alternatives are presented neutrally, partly because the current system defines the starting point.
Retirement plan
Default EffectEmployees are automatically enrolled at a contribution rate unless they opt out or change it.
Status Quo BiasAn employee who has used the same allocation for years keeps it during a later review because it is already the current portfolio.
Retrospective review protocol
Separate forecast quality, decision quality, and learning.
Write the options and outcomes without marking any one as current or pre-selected.
Record what happens under inaction and whether the current state existed before the decision screen or policy.
Estimate real switching costs, effort and uncertainty separately.
Where possible, compare behaviour under active choice, alternative defaults or a neutral starting condition.
Judge welfare and preference from the full decision evidence, not from default uptake or persistence alone.