Defaults are the real interface
Almost nobody changes a setting. Whatever you ship as the default is what nearly everyone lives with, permanently — which makes it a product decision, not a placeholder.
By Shashi Kumar ·
Here is a number that should change how you build software: for most settings in most products, well over 90% of users never touch them.
Not "most users". Nearly all users.
Which means the value you typed in as a placeholder — the one you meant to revisit — is the experience for almost everybody who will ever use the thing.
Defaults are a decision you make on the user's behalf
That sounds obvious written down. It rarely feels obvious in the moment, because defaults get chosen at the least considered point in the process: while you are wiring up the form and want to move on.
Some defaults I have watched cause real damage:
- Notifications on. Chosen because it demos better. Result: users disable notifications at the OS level, permanently, and you lose the channel entirely.
- Public visibility. Chosen because it makes the product look active. Result: a slow drip of people sharing things they thought were private.
- Auto-renew on, with the checkbox pre-ticked. Chosen because it improves retention. It does, briefly, followed by chargebacks and a reputation you cannot buy back.
Each of these was a real decision, made carelessly, that shaped the product more than any feature shipped that quarter.
The test I use
Before shipping a default, one question:
If this value never changes for this user — ever — is that a good outcome for them?
If yes, ship it. If no, you have one of two problems: either the default is wrong, or the setting should not exist and you should just make the decision properly.
That second case is more common than people expect. A setting is often a decision the team could not agree on, pushed onto the user. Users do not want to arbitrate your internal disagreement.
Where this bit me
In InnenFlow — a journalling app I built — I originally shipped with a daily reminder on by default. It seemed obviously helpful. Journalling works better with a habit; a reminder builds a habit.
What actually happened: people who missed a day got a notification that read, to them, as an accusation. The reminder was not building a habit. It was building a small, daily reminder of failure.
I turned it off by default. Retention went up. The feature was fine; the default was the bug.
The wider point
Every technical decision is a decision about a person. A default is the purest form of that — it is you deciding, on behalf of a stranger, what normal looks like.
Treat it with the weight that deserves. It is not a placeholder. It is the product.
Contact Acquiretech Software Solution: info@acquiretechsoftwaresolution.in · WhatsApp +91 80786 33912 · Send an enquiry