Design Defaults Are Not Neutral Choices
Email notifications: on. Data sharing with third-party partners: on. Autoplay: on. Personalized ads: on. Marketing emails from affiliated brands: on. Location tracking when the app is in the background: on.
Every one of those was a design decision. Someone built that screen, decided the default state, and shipped it. Most users never touch it. That's not a coincidence — it's the point.
The Most Powerful Design Lever Is the One Nobody Talks About
Richard Thaler and Cass Sunstein's work on choice architecture — which eventually won Thaler a Nobel Prize in Economics — established something that every designer privately knows: the default is not a neutral starting point. It's where most people end up. Defaults exploit two overlapping tendencies: status quo bias (the preference for whatever the current state is) and decision avoidance (the cost of making an active choice). Most users, most of the time, accept the default because changing it requires noticing it, understanding it, and deciding to act.
A 2023 study published through the Society for Consumer Psychology found that default choices consistently influence downstream behavior across contexts ranging from retirement savings to organ donation. The effect isn't small and it isn't confined to low-stakes decisions. When the default was opt-in, participation rates in voluntary programs dropped significantly compared to opt-out versions. The behavior changed. The people didn't.
Designers know this. Any UX practitioner who has been doing this for more than a few years has seen the analytics — has watched the funnel data show that the percentage of users who interact with settings pages is in the low single digits. They know the default is the experience for the vast majority of the people who use the product.
And yet the conversation about defaults is almost always framed as a question of convenience: what makes it easiest for users to get started? What's the most obvious initial state? The question of who benefits from that initial state is rarely asked in the same room.
The Complicity Dodge
Here's where the industry has a terminology problem it has mostly chosen to keep.
The word "default" implies passivity. A default is what happens if you don't choose. It carries no authorial weight. Nobody "set" the default — it was just the natural starting state of the system. This framing is almost always incorrect, and designers know it's incorrect. The default was discussed, debated, tested, shipped, and in many cases A/B tested to optimize for a specific outcome. It's a decision with an author, a rationale, and often an OKR attached to it.
The reason the industry clings to "default" rather than "behavior steering" is because the latter requires accountability. If the initial email notification state is a behavior steering decision, then whoever made that decision is responsible for the outcomes it produces: the open rates, the disengagement, the resentment, the users who eventually unsubscribe from everything because they never knew where to find the settings that would have let them calibrate the volume.
The language of neutrality protects the decision-maker from having to own the choice. The design was just "obvious." The default was just "the most common use case." The opt-out was just "industry standard."
These are not lies, exactly. They're accurate descriptions of the proximate cause. They omit the structural question: what would have been different if the default were reversed, and who would have benefited from that difference?
Who Profits, Who Pays
There is a class of defaults that genuinely serve users. The system that saves your work automatically. The text editor that opens to your last document. The account that remembers your shipping address. These defaults are in alignment: what the user wants is also what the product needs, and the default state reflects that convergence.
Then there are defaults that diverge. Where the user's interest and the product's interest are different, and the default consistently resolves in the product's favor.
Marketing emails on by default. Analytics sharing on by default. The "recommended" plan pre-selected on the pricing page — and the "recommended" plan is the middle tier with the highest margin. The app that opens to the feed rather than the inbox because feed engagement drives retention metrics. The privacy setting that requires seven clicks to change. The cookie consent that puts "Accept All" in blue and "Manage Preferences" in grey text.
None of these are accidents. They are design decisions made by people who understood the choice architecture research and applied it in a direction.
The legal reckoning for dark patterns has been building since the EU DSA created enforceable standards in 2023. The defaults I'm describing aren't always illegal under those standards — but the distinction between a legal default and an ethical one is not the same line, and designers who are only thinking about the first line are not doing the work.
The Question Worth Asking
There's a useful test for any default you're about to ship: if the default were reversed — if the behavior you're currently defaulting to were the off state and the user had to turn it on — would that change your business metrics? If yes, you've found the conflict of interest. The question then is whether you own that conflict or explain it away.
This isn't a call for every product to ship in a maximally friction-inducing, privacy-preserving, opt-everything-in configuration. Defaults serve real purposes. Sane starting states matter. The argument isn't against defaults; it's against treating them as politically neutral.
The most powerful design decision you will make on a product is often invisible to the user and unacknowledged in the design review. It's the state of a checkbox they won't see. It's what happens when they do nothing.
Who was that decision for?
Photo by Davide Baraldi via Pexels