One of the most overlooked truths in product design (and life) is this:
defaults aren’t neutral — they’re a decision.
And most people never change them.
From the brightness level on your phone to the ringtone it came with, to how your privacy settings are structured — defaults shape our experience way more than we realise. And in most cases, they decide it for us.
Think about it.
How many people actually change the notification settings on an app?
Or dig into “advanced” sections to tweak preferences?
Almost no one.
So what you set as the default — as the starting point — becomes the baseline experience for 90% of your users.
This is true in design, onboarding, even in life.
Want people to opt into newsletters? Pre-check the box.
Want users to enable dark mode? Make it the default.
Want to reduce friction? Show the most common path first.
I’ve seen this apply beyond screens, too.
- If your restaurant menu defaults to “large” drinks, people order large.
- If your checkout page makes “guest checkout” the default path, more people complete purchases.
- If your product page shows the most expensive variant first — it frames perception.
- Even in forms, if the country field defaults to “United States” for Indian users, you’re already creating micro-annoyances.
The point is: what’s automatic becomes invisible.
And when something’s invisible, it feels natural — even if it’s lazy, manipulative, or just wrong.
So if you’re building anything — a product, a process, a form, a brand — be intentional with what your defaults say.
Because your user might never change them.
And that means:
Whatever you set by default… is what they experience by design.
— Aman
