Defaults Are Decisions
Who chose the setting almost nobody will change?
The idea
Most people never change a default, so the default setting is the choice you are actually making for them.
In the real world
An opt-in checkbox and an opt-out checkbox produce very different rates from identical wording.
Going deeper
Most people never change a default, so the default determines the actual distribution of outcomes while the interface copy affects only the minority who engage with the choice.
A team can debate a privacy toggle's wording for a week and never discuss which way it ships set, having optimised the visible decision and defaulted the consequential one. Every default in a product is a policy — about privacy, about spend, about what people are opted into — whether or not anyone decided it. Listing them and asking which were chosen usually finds several that were inherited.
Where it stops applying
Defaults that serve the business against the user's interest are manipulation regardless of how they are framed. The power of the position is exactly why it carries an obligation.
Why it matters
It means every default in your product is a policy, whether or not anyone decided it.
Try this today
List three defaults in your product and ask whether each was chosen or inherited.
Test yourself
A team debates the copy on a privacy toggle for a week and never discusses which way it ships set. What did they leave undecided?
Show the answer
The outcome for nearly everyone. A large majority will accept whatever it arrives as, so the default determines the real distribution of choices while the wording only affects the few who look. They optimised the visible decision and defaulted the consequential one.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.