Status Quo Bias

People prefer the current state and resist change, even when change would benefit them.

stellae.design

Cognitive

Status Quo Bias was formally described by William Samuelson and Richard Zeckhauser in their 1988 paper. It's deeply connected to loss aversion — people perceive the potential losses from changing as larger than the potential gains. In practice, this means users stick with default settings, resist interface redesigns, and stay with familiar products even when better alternatives exist. For product designers, this has major implications: defaults are decisions, and most users will accept whatever the default is.

Why It Matters

Status quo bias causes users to prefer the current state of affairs even when objectively better alternatives exist. This tendency directly impacts adoption rates for new features, redesigns, and onboarding flows. Understanding this bias helps teams anticipate resistance to change and design transitions that feel safe rather than disruptive.

Real-World Examples

Default shipping option in checkout

E-commerce platforms pre-select standard shipping as the default, knowing most users will not change it. This leverages status quo bias ethically by aligning the default with the most commonly desired outcome. Users still see all options but rarely deviate from the preset choice.

Gradual UI migration with opt-in preview

Google Workspace introduced its redesigned interface by letting users preview the new look and revert at any time. This acknowledged status quo bias by removing the pressure of a permanent switch. Over weeks, users grew comfortable and voluntarily adopted the new design.

Counter-example

Forcing a complete redesign overnight

A SaaS product ships an entirely new interface without warning or the ability to revert. Users feel disoriented and frustrated, flooding support channels with complaints. The team underestimated status quo bias and lost trust by removing all sense of control.

Role-Specific Guidance

Common Mistakes

• Teams often assume that a measurably better design will be embraced immediately, ignoring the emotional attachment users have to what they already know. Another frequent error is exploiting status quo bias by burying opt-out mechanisms for subscriptions or privacy settings, which erodes trust. The goal should be to respect the bias while gently guiding users toward genuinely beneficial changes.