# Default Everything: Where Starting Choices Hide and How to Pick Them

> Every product starts with choices already made for the user. Here is where those defaults hide, how to pick good ones, and how to check them.

**In short:** A default is a choice a product has already made for the user, and defaults hide in settings, in the order of lists and in sort-by menus.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/default-everything

## What you will learn

Almost every screen you design already makes choices for the user before they touch anything. A box may already be ticked. A list may already be sorted. A settings switch may already be on. These starting choices are called defaults. Some defaults are picked on purpose. Many are picked by accident, because nobody stopped to check them.

In this lesson you will find where defaults hide on a screen, how to choose a good default, when to leave a choice empty, and how to check your defaults before you ship a product. The examples come from public design systems used by real services in the UK and by Google's Material Design system.

- **Default:** The starting choice a product uses when the user has not picked anything yet.
- **Pre-selected:** Already chosen when the page loads, so the user does not have to pick it.
- **Checkbox:** A small square that users tick. They can tick more than one.
- **Radio button:** A small round circle. Users can pick only one in a group.
- **Drop-down (select):** A menu that opens to show a list. The user picks one item from it.
- **Placeholder:** Text or an item that tells users what to do. It is not meant to be chosen.
- **Sort order:** The order items in a list appear in, such as newest first or lowest price first.
- **Settings screen:** A page where users change how a product behaves for them.

## Where do defaults hide on a screen?

A default is not only a setting in a menu. It can sit in any place where the product must show something before the user acts. Designers often forget these hidden ones, so it helps to look for them on purpose.

- **Pre-set options:** A tick box already ticked, a radio already chosen, or a drop-down already showing a value. This is the most visible kind of default.
- **Sort order:** The order a list opens in. A product may start with the newest item, the cheapest item, or the most popular one.
- **Starting view:** The tab, page, filter, or map area that opens first when someone arrives at a screen.

Each of these was chosen by someone. If nobody wrote down why, the default is a guess that users will live with for a long time.

### What are defaults in settings screens?

A settings screen is where defaults matter most, because many people never open it. The archived Material 1 settings guidance says that settings should save user preferences, and they should be used either by most users or be essential to a smaller group who need them.

Material also advises showing the most important or most used settings at the top. A person who skims the screen should see the key values without hunting for them.

> **Tip:** Before you add a setting, ask whether most people would ever change it. If the answer is no, the default may be the only thing most users ever see.

## How do you pick a good default?

The Material 1 archive, which is no longer maintained, gives designers a short test for setting defaults. The default should match the choice most users would make, stay neutral and carry little risk, use less battery or mobile data, and interrupt people only when something is important.

- **Match most people:** Pick the option most users would choose on their own.
- **Stay neutral and safe:** A starting choice should be neutral and carry little risk.
- **Save resources:** Where two options work equally well, choose the one that uses less battery or mobile data on a phone.
- **Interrupt only for important matters:** Do not let a default trigger alerts or pop-up messages unless the matter truly needs the user's attention.

> **Tip:** Write one sentence that explains each default in your design file. If you cannot write that sentence, the default was probably not chosen on purpose.

## When should you leave the choice empty?

Some defaults are not helpful at all. When a screen asks a question, a pre-set answer can quietly answer for the user. The GOV.UK guidance for radio buttons says not to pre-select them, because the user may not notice they skipped a question or may send an answer they did not mean.

The same advice applies to checkboxes. GOV.UK asks designers not to tick any boxes in advance, for the same reasons.

### Should you use settings or questions?

The GOV.UK Design System draws the line in a simple way. A drop-down used for settings can have an option pre-selected when the page opens. A drop-down used for questions should not have any option pre-selected, in case that choice affects the answer.

Ask yourself a simple question about each screen. Is the user setting how the product behaves, or answering something about themselves? The first can have a starting value. The second should start empty.

**Quick check:** A sign-up form asks: 'Would you like our monthly newsletter?' with yes and no options. What should the starting state be?

A. Yes, already selected, so more people join
B. No, already selected, so nobody is signed up by accident
C. Nothing selected, so the user must make a choice
D. Hidden until the user scrolls to the bottom of the page

**Answer:** C. This is a question about the user, not a setting. Guidance from GOV.UK says not to pre-select options on questions, because a starting choice can change the answer or let the user skip the question without noticing.

## Why is order a default too?

The order of options also acts as a default. People often pick the first item they see, so the order can steer their choice even when nothing is pre-selected. GOV.UK says to order checkboxes and radio options alphabetically by default. In some cases, ordering from most common to least common can help, such as ordering countries by population size.

Radio options follow the same plan. The default order is alphabetical, and the common-first order is an exception that needs a good reason.

### Sort-by menus

A sort-by menu is a drop-down that changes how a list is ordered.

GOV.UK's select example is similar. It starts on 'Recently updated' and offers other choices such as 'Most views' and 'Most comments'.

> **Tip:** Match the sort order to the task. A product for finding a cheap hotel might start with lowest price. A news feed might start with newest first. Choose the start based on what the user came to do.

**Quick check:** In a drop-down, what is a placeholder item such as 'Select an option' for?

A. To be the answer that most people pick
B. To tell users what to do, and it cannot be chosen
C. To switch on a setting automatically
D. To hide the rest of the list until a search is made

**Answer:** B. It guides the user without counting as an answer.

## How do defaults work for different people?

A default that suits most people can still fail some of them.

The aim is a good start that a user can still change.

### How do you keep changes easy?

The report is about settings that users change by hand, not software that guesses what they want.

A default is only fair if the user can find the control and change it quickly. Put the setting where people will look, and keep the path to change it short and clear.

> **Tip:** Test the default by asking a real person to change it. If they cannot find the control in a few seconds, the default may be trapping them, even if it is a good starting value.

## How do you check your defaults before you ship?

Use this short walk-through on any screen you design. It takes less time than fixing a problem after launch, and it makes your defaults easier to explain to the people you work with.

1. **List every default:** Go through each screen and write down what the product shows before the user acts. Include tick boxes, radio buttons, drop-downs, sort orders, and the starting tab or view.
2. **Name who each default helps:** For every default, write down which users it helps most. If it helps the business but makes life harder for users, mark it and think again.
3. **Check the question screens:** Find every screen that asks a question. Remove any pre-set answers unless they are a true starting value for a setting.
4. **Watch real people:** Ask a few people to complete the task. Notice whether they keep the default, change it, or miss it. Their behaviour tells you more than your opinion does.
5. **Make changing easy and visible:** Place the control where people look, let the user change the value in one clear step, and show the current value so nobody has to guess what is set.

Revisit your defaults after launch. Look at how people use the product, and change any default that most people quickly switch away from. A default that everyone changes is a sign that the starting choice was wrong.

> **Tip:** This course's lesson on Defaults looks at why people tend to keep the default they are given. This lesson shows you where defaults sit across a whole screen, so you can check each one.

## Key takeaways

- **Defaults are everywhere:** Look beyond settings. Tick boxes, sort orders, starting tabs, and first items in menus are all defaults.
- **Choose on purpose:** Pick defaults that match most users, carry little risk, and interrupt only when needed. Write down the reason for each one.
- **Keep questions empty:** On question screens, do not pre-select answers. Leave the choice to the user, and let them see what they still need to answer.

## Sources

- [Material Design: Settings pattern (Material 1 archive)](https://m1.material.io/patterns/settings.html)
- [Material Design 3: Accessibility overview](https://m3.material.io/foundations/overview/principles)
- [GOV.UK Design System: Checkboxes](https://design-system.service.gov.uk/components/checkboxes/)
- [GOV.UK Design System: Radios](https://design-system.service.gov.uk/components/radios/)
- [GOV.UK Design System: Select](https://design-system.service.gov.uk/components/select)
- [NHS Service Manual: Select component](https://service-manual.nhs.uk/design-system/components/select)
- [UK Parliament Design System: Select](https://designsystem.parliament.uk/forms/select/)
- [ONS Service Manual: Select component](https://service-manual.ons.gov.uk/design-system/components/select)
- [Nielsen Norman Group: Customization Features report](https://www.nngroup.com/reports/customization-features/)
- [Interaction Design Foundation: What is Material Design?](https://ixdf.org/literature/topics/material-design)
