The Most Powerful Design Decision Is the Default

Every screen with a choice on it has a default. The option that's already selected, the setting that's switched on, the value in the box before anyone types. It looks like the smallest detail on the page, and it's often the most influential.

Most people never change defaults. They're busy, they trust that whoever built the product chose sensibly, or they don't realise there's a choice to make. Whatever is pre-selected is what most of them will live with.

Defaults are decisions

A default is never neutral. When we pre-select an option, we're choosing on behalf of everyone who doesn't change it. That's a lot of responsibility for something that often gets set without much thought, usually by whoever builds the form, based on whatever was first in the list.

We try to make default decisions on purpose, as part of the design, and to write down why each one was chosen.

Choosing for the majority

The first question is what most people would choose if they thought about it. A delivery form should default to the most popular delivery option. A booking form should open on the next available date, not today if today is fully booked. A country selector on a UK site should start on the United Kingdom.

Good defaults save time. If most people would pick the same thing, making them pick it is a waste of their effort.

Choosing for safety

Sometimes the most common choice isn't the right default, because a mistake would be costly. Privacy settings should default to the more private option. Sharing should start off, not on. Destructive options, like deleting old data, should never be pre-selected. If someone skims past a setting, they should end up in the safer position.

Choosing honestly

Defaults can be used against people. Pre-ticked boxes for marketing emails, add-ons already in the basket and auto-renewal hidden in a small setting all rely on people not noticing. They might improve a number in the short term, but they erode trust, and under UK data protection rules, pre-ticked consent boxes don't count as consent anyway.

Our rule is simple: if we'd be uncomfortable explaining a default to the person it affects, it's the wrong default.

When there shouldn't be one

Sometimes the right default is none at all. If there's no clear majority and no safer option, pre-selecting one can push people into a choice they didn't consider. Questions like a person's title or how they heard about you shouldn't assume an answer. Leaving the choice open makes people think about it, which is the point.

Defaults in settings and systems

Defaults matter beyond forms. The default sort order in a list decides what people see first. The default view in a dashboard decides what they focus on. The default notification settings decide how often a product interrupts people, and therefore how quickly they decide to turn everything off.

We review these during design the same way we review layouts. In our app development work, the first-run defaults often shape how people feel about a product more than any single feature does.

Revisiting defaults

Defaults should change as you learn. If analytics show most people change a particular default, it's the wrong one. If support requests keep mentioning a setting nobody knew about, the default may be hiding something important.

The default is the choice you make for everyone who doesn't make one for themselves. If you're not sure what yours are saying about your product, let's go through them.