Status Quo Bias
An existing or previously chosen option can receive extra weight simply because it is the current state.
Public evidence overview
One checked source, with its limits.
This preview is not the complete evidence base. Use it as a question to investigate in your own product, not as a prediction of what an individual will do.
Revisiting status quo bias: Replication of Samuelson and Zeckhauser (1988)
Research-assisted source review
- What it supports
- Three scenarios showed strong support for status quo bias; the wagon-colour scenario did not show substantial support.
- Where it may not transfer
- The decisions remained hypothetical, covered four selected scenarios and used US online-worker samples. The mixed scenario result shows that the effect cannot be assumed from the presence of a current option alone.
See how sources and limitations are checked in our editorial method.
Member depth
Continue into the complete evidence and application.
Practitioner includes the complete checked source set, study context and practical takeaways for this ingredient. The public overview above remains available without upgrading.
Seen in real products
How teams put it to work.
Examples identified in our interface teardowns, linked back to the full product journey.
The loading state offers no alternative route, making waiting the only apparent option even if the feed stalls or is not the reason someone opened the account area.
View Bring people back without nagging →
A named current tier can become the member’s reference state, making a future downgrade or missed threshold feel like losing status rather than simply changing benefits.
View Bring people back without nagging →