The Default Trap: Why Customers Never Change Settings

Most people never change the default settings on anything they own.

This isn't laziness, though it looks like it. It's not stupidity, though it feels like it when you're the product manager watching users suffer through suboptimal configurations they could fix in seconds. It's something far more systematic: defaults function as invisible anchors that shape behaviour so completely that alternatives barely register as possibilities.

The phenomenon reveals something uncomfortable about how we actually make decisions. We like to imagine ourselves as rational agents who evaluate options and select what suits us best. The reality is messier. When a setting arrives pre-configured, it doesn't just sit neutrally alongside other choices. It becomes the reference point against which all alternatives are measured. Changing it requires not just effort, but a psychological shift—an acknowledgment that the current state is wrong, combined with confidence that the alternative is right. Most people never make that shift.

Consider what happens when a software company updates its privacy defaults to collect more user data. Outrage erupts. Journalists write pieces. Regulators take notice. The company reverses course, citing "user feedback." But here's what actually happened: the company didn't create new behaviour. It revealed existing behaviour. Users weren't suddenly more willing to share data. They were simply no longer protected by the default. The moment the company switched the setting back, most users returned to their original state—not because they'd reconsidered and chosen privacy, but because the default had shifted again.

This matters because defaults aren't neutral. They're decisions made by someone else, embedded into systems where they accumulate power through sheer inertia. A bank's default investment allocation shapes retirement outcomes for millions. A phone's default notification settings determines how fragmented your attention becomes. A streaming service's default autoplay setting influences how you spend your evening. None of these require active consent to take effect. They simply happen, because that's what defaults do.

The deeper issue is that defaults exploit a genuine cognitive limitation. Evaluating alternatives requires mental energy. It requires you to understand what each option means, predict how it will affect your experience, and overcome the status quo bias that makes the current state feel safer than it probably is. Most people, most of the time, don't have that energy available. They're managing work, relationships, finances, health—the actual substance of their lives. A software setting ranks somewhere below noticing.

This is where the behaviour becomes predictable. Companies that want users to adopt a behaviour set it as the default. Companies that want users to avoid a behaviour bury it three menus deep and require active opt-in. The asymmetry is stark. A telecom company that makes premium support the default will retain far more premium subscribers than one that requires customers to actively select it. A social network that defaults to public sharing will generate more data than one that defaults to private. The choice architecture does the work.

What makes this genuinely insidious is that it works regardless of whether the default is actually good for the user. A well-intentioned default—say, a conservative privacy setting—still functions through the same mechanism: inertia, not preference. Users don't stick with it because they've evaluated privacy and decided it matters. They stick with it because changing it requires effort they haven't allocated.

The implication is uncomfortable: we can't assume that widespread adoption of a setting reflects genuine user preference. It might reflect nothing more than the path of least resistance. This matters for anyone designing systems, setting policy, or trying to understand what people actually want versus what they've simply accepted.

The question worth asking isn't whether your users like your defaults. It's whether they've ever considered changing them.