The ethics of the default setting

Almost no one changes a default. This is one of the most reliable findings in behavioral research, and one of the least discussed in engineering rooms, where defaults get decided in a Slack thread and forgotten by the time anyone downstream feels their effect. Whoever sets the default isn't making a small technical choice. They're making the choice for the overwhelming majority of people who will ever use the thing.

That's not an argument against defaults — a product with no defaults is a product no one can use. It's an argument for treating the default as the real decision, and the "advanced settings" as the exception that lets a few people opt out of it. If you wouldn't be comfortable defending the default as the right outcome for someone who never touches a settings menu, it's not ready to ship.

Convenience is not neutral

Every default trades something for ease of use, and the trade is usually invisible precisely because it's convenient. Auto-renewal defaults to on because it's better for the business and worse for the person who forgets to cancel. Data sharing defaults to on because more data is more useful to someone, just not necessarily to the person generating it. None of these are hidden conspiracies — they're ordinary decisions made by ordinary teams under ordinary pressure to hit a number.

Which is exactly why they need scrutiny. Bad incentives don't usually announce themselves as bad. They show up dressed as reasonable trade-offs made by people with a deadline, and the only defense against that is asking, deliberately, who the default is actually for.