The default matters more than the option.

Design · 5 min read

I was in a design session with a client who wanted to let users customise almost everything. Background colours. Font sizes. Layout preferences. Notification schedules. The argument was solid: different people like different things, so give them options. Let them make it their own.

The problem is that most people won't. Research consistently shows that the vast majority of users never change default settings. They use whatever the app gives them out of the box. Which means the default isn't just a starting point. It's the product. If the default is wrong, options don't save you. They just give users a maze to navigate before they give up.

Why defaults dominate

There's a well-documented principle in behavioural economics called the default effect. People tend to stick with pre-selected options, even when alternatives are available. It's not laziness. It's trust. Users assume the default was chosen for a reason. They assume someone who knows more about this product than they do made the decision. And they're usually right.

A study by Nielsen Norman Group found that users rarely explore settings screens, and when they do, they change one or two things at most. The rest stays untouched. That means every hour you spend building a settings option that 3% of users might change is an hour you didn't spend making the default experience better for the other 97%.

This is especially true in first-release apps. Your early users are forming their opinion of your product in the first thirty seconds. If the first thing they see is a configuration screen asking them to choose preferences before they've even used the app, you've already lost them.

How to design better defaults

Start with your most common user. Not your edge case. Not your power user. The person who represents the majority of your audience. What do they need the app to look like? How do they want notifications? What information should be visible first? Design for that person. Make the out-of-the-box experience perfect for them.

Then, and only then, think about options. Dark mode is a reasonable option because a significant percentage of users prefer it. Custom notification schedules might be reasonable if your users have varied routines. But custom colour themes? Custom font choices? Custom layouts? Those are version two features at best. They're not solving a problem. They're adding complexity.

The client I was working with eventually agreed. We replaced the planned settings screen with a single toggle for notifications and shipped smart defaults for everything else. The app felt faster, simpler, and more confident. Like it knew what it was doing. Because it did.

Customisation is a reward, not a starting point

Here's the way I think about it. Customisation is something you earn from loyal users. Duolingo doesn't let you customise your avatar on day one. You unlock it after using the app consistently. Spotify doesn't ask you to configure your home screen. It learns from your behaviour and adjusts automatically. The best customisation doesn't come from settings. It comes from usage.

For a first-time app, ship the default. Make it thoughtful. Make it work for most people. If users start asking for specific options after they've been using it for months, add them. But don't build them speculatively. Don't assume your users want control. Most of them just want something that works.

Sources
The Power of Defaults (Nielsen Norman Group) - Users rarely change default settings.
Aesthetic-Usability Effect (Laws of UX) - Users perceive attractive designs as more usable, reducing need for customisation.

Related blog posts:

The difference between a feature and a solution →

What is an MVP? →

Fewer screens forced better thinking →