People tend to accept whatever option is presented to them as the default. Not because they've evaluated it and agreed, but because changing it requires effort — and effort has a cost that inaction doesn't. The default is always a choice made by the designer, whether or not it's acknowledged as one.
In 2003, economists Eric Johnson and Daniel Goldstein published a study comparing organ donation rates across European countries. The differences were striking. Germany: 12%. Austria: 99%. Denmark: 4%. Hungary: 99%. The countries weren't that different culturally. What differed was their default: countries with opt-out systems had rates near 100%. Countries with opt-in systems had rates near 10%. The decision was the same. The effort required to make it was different. And that difference in effort produced a 90-point gap in outcomes.
This is default bias: the tendency to accept whatever option is presented as the status quo. It operates through loss aversion, effort avoidance, and implied endorsement. Together these forces are powerful enough to determine whether millions of people become organ donors, whether software collects your data, and which subscription plan the majority of customers end up on.
The designer who sets a default is not making a neutral choice. They're making the most powerful choice available to them — selecting which outcome most users will end up in without ever consciously deciding. This power comes with a corresponding responsibility.
“Setting a default is not an act of neutrality. It is an act of choice about who benefits when people don't decide.”
— Thaler & Sunstein, Nudge, 2008
Notification and email settings are where default bias is most directly visible. Both pages below show the same settings for the same product. What changes is which options are on by default — and therefore who captures the value of the 80% of users who never visit this page.
All five settings on by default. The 80% of users who never visit settings leave them all on — including advertising partner data sharing.
Useful notifications on. Marketing, analytics, advertising off. Users keep their data private by default.
The two pages are identical in structure. The only difference is which settings are pre-enabled. In the bad version, users are enrolled in marketing campaigns and data-sharing arrangements they never chose. In the good version, they receive only what's genuinely useful to them. The designer made that decision on their behalf through default placement.
On pricing pages with multiple tiers, the default-highlighted plan significantly influences which plan most users choose. This is partly anchoring, partly loss aversion relative to the highlighted option, and partly pure default bias — the plan that looks most like the “normal” choice gets treated as the baseline. The highlighted plan is the default.
Below are two versions of the same three-tier pricing page. The plans are identical. What changes is which one is highlighted as the recommended option.
Pro at $49 is highlighted as default. Default bias pulls users there even if $9 of product is all they need.
Starter at $9 is highlighted as right for most. Users start where they belong and upgrade intentionally later.
The left page maximises initial revenue per user: the highlighted plan is the $49 Pro tier, and default bias pulls most users there even if they only need $9 of product. The right page maximises long-term relationship quality: users who start at the right level churn less, upgrade intentionally when they need more, and have a fundamentally different relationship with the product than users who were default-biased into overpaying.
Every default is a policy decision about whose interests the designer is optimising for. This isn't always a binary — there are genuinely neutral defaults, beneficial nudges, and exploitative ones. But there are no accidental defaults. Every unset default is a default.
The practical test for any default: if most users knew what this default was and how it worked, would they feel that it was set in their interest? If the answer is clearly yes — product updates on, marketing emails off, the plan that fits most users highlighted — the default is well-aligned. If the answer is clearly no, the default is exploiting inertia at the user's expense.
Johnson, E. J., & Goldstein, D. (2003). Do defaults save lives? Science, 302(5649), 1338–1339. · Thaler, R. H., & Sunstein, C. R. (2008). Nudge: Improving Decisions About Health, Wealth, and Happiness.Yale University Press. · Samuelson, W., & Zeckhauser, R. (1988). Status quo bias in decision making. Journal of Risk and Uncertainty, 1(1), 7–59.