Status Quo Bias
People prefer things to stay as they are, which is why every redesign starts with a deficit.
Definition
Samuelson and Zeckhauser (1988) demonstrated a systematic preference for the current state over alternatives, beyond what the objective differences justify. The bias is reinforced by loss aversion and by the effort of evaluating change.
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
Reach for this when
- Planning any significant interface change.
- Deciding between incremental and cutover migration.
- Interpreting backlash after a release.
Common mistakes
- Treating all resistance as irrational.
- Removing the old path before the new one is proven.
- Measuring only the complaints, or only the aggregate metrics.
- Cancelling a change because of day-one volume, before any behavioural data exists.
The redesign deficit
A new interface has to be better by more than a small margin to be perceived as better at all, because the existing one carries the accumulated value of familiarity and practice. This is not irrationality on the user's part: their learned efficiency is genuinely destroyed by the change.
This is why gradual migration usually outperforms a single cutover for products with an established user base, and why the strongest predictor of backlash is how much learned behaviour the change invalidates.
Reducing the cost of change
- Migrate incrementally rather than all at once.
- Keep a way back for a defined period, and say when it ends.
- Preserve muscle memory where you can: keyboard shortcuts, URLs, key locations.
- Explain what changed and why, in the product rather than only in a blog post.
- Show the user what they gain in their own terms, not in feature terms.
Shipping a change people did not ask for
- 1
Say what is changing and why, before it changes
The reason does not have to be persuasive. Its absence is what reads as arbitrary.
- 2
Offer a period where both exist
An opt-in window converts a forced change into a choice, and produces the feedback you need.
- 3
Preserve what can be preserved
Shortcuts, saved views, terminology, positions. Every one kept is one less thing to relearn.
- 4
Watch the behaviour, not the volume
Complaints spike on day one and decay. Task completion does not lie in the same way.
- 5
Keep a way back for long enough to matter
And say when it closes, so nobody is surprised twice.
In practice
- i.
Opt-in periods before cutover
Major redesignsOffering the new interface as an option, gathering behavioural data, then switching the default with a temporary opt-out consistently produces less disruption than a hard cutover.
- ii.
Preserving shortcuts across a redesign
Professional toolsVisual redesigns that keep keyboard shortcuts and URL structure intact preserve most learned behaviour, which is the part users actually mourn.
- iii.
The complaint curve
Reading the reactionNegative feedback peaked on the first day and had halved within a week, while task success was above the old design throughout. Both were true, and only one of them was about whether the change was good.
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.
Default Effect
Cognitive biasPeople accept whatever option arrives already chosen.
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 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.
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.
Local chart
BIAS·005 · Region I · Grid B1
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]
Status quo bias in decision making
W. Samuelson and R. Zeckhauser, Journal of Risk and Uncertainty, 1988
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
Explains
The mechanism underneath these entries.
- Consistency and StandardsHEUR·004 · Heuristic
- Jakob's LawLAW·003 · Law
- Power Law of PracticeLAW·015 · Law
Applied through
Where this shows up as a concrete interface decision.
- Design System AdoptionSYS·005 · Design system
- Versioning and DeprecationSYS·006 · Design system
- A/B TestingRES·009 · Research method
Practical example
A worked decision where this was the deciding factor.
- Migrating Product Teams onto a Design SystemCASE·003 · Case study
Short definition
The one-paragraph version, for when that is all you need.
- DeprecationTERM·089 · Term
- Feature FlagTERM·099 · Term
Related concept
Connected closely enough to change how you apply this.
- Loss AversionBIAS·002 · Cognitive bias
- Mere Exposure EffectPSY·009 · Psychology