Most users do not change default values

What it is

The default effect is the tendency to retain an option, setting, or flow selected in advance by a system rather than change it actively. People may save time, avoid decision, trust a recommendation, fail to notice the option, or fear the risk of change. A default is therefore not a neutral starting point: it converts product judgment into most people's actual outcome, especially in low-attention, repeated, or complex tasks.

Why it happens

Changing a default requires finding an option, understanding a difference, assessing consequence, and taking extra action. With incomplete information or time pressure, people often read the default as a system recommendation, common practice, or safe choice, so choice inertia operates. Defaults also shape later behavior: people who first adopt a setting may build workflow around it and find later switching harder. The effect strengthens when combined with hiddenness, complexity, or power imbalance.

Studying it

Measure retention and change rate, understanding before change, later satisfaction, error, and long-term outcome under different default options rather than final conversion alone. Use interviews or task replay to distinguish active approval from not seeing, not understanding, or not daring to change. Include newcomers, experienced users, devices, and assistive contexts, since accessibility of changing defaults may be unequal.

Where it stops holding

A default is not automatically manipulative. For frequent, low-risk settings with broadly similar preferences, a suitable default can reduce repeated work greatly. The problem is disguising an uncertain, highly individual, or consequential choice as one that requires no decision. Offering choice also need not force configuration of everything at the start; a system can ask progressively in relevant context and allow change at any time.

Applying it

• Treat each default as a product decision, not technical placeholder; state the user task, evidence, scope, and potentially affected groups it serves.
• Let people see the current default, understand its consequence, and change it with low friction, especially for personalization, privacy, fees, and settings affecting others.
• Review retention rate with outcome quality continuously; high retention does not automatically mean satisfaction. Use segmented feedback to revise defaults or provide contextual choice when needed.

Related

• Same group: B2.16.2 Defaults are equivalent to a product's value proposition · B2.16.3 Defaults should serve users rather than metrics · B2.16.4 Preselecting high-consequence options is manipulation
• Nearby: B2.15 Simplicity and feature creep · B2.12.2 Irreversible actions must be explicitly marked
• Search terms: default effect · default value · choice architecture