With no safe default, leave empty and force a choice
Aliases: no default · forced choice · empty until decide
What it is
When no preselected option can stand for “the user has not decided yet” or “harmless for most people,” the field should stay empty and require a choice at submit. No safe default covers gender, medical history, payment method, deletion scope — questions whose wrong fill is asymmetric. Ticking the first item for the user looks like one less step; it writes a false consent to the first option. Leaving empty is not laziness; it is a refusal to forge an attitude.
The force happens at submit, not as an error the moment the page opens. Empty during filling is legal indecision.
Why it happens
A preselection exploits default bias: people treat the already-lit item as a recommendation or a finished question, and attention moves to cells that still look empty. If the first item is an artefact of sort order (alphabetical, API order), the bias is amplified by structure, unrelated to the user’s interest. Blocking empty at submit puts the decision back at the moment they are still “finishing this form,” rather than letting a default steal it during a scan.
When a safe default exists (timezone from location, language from the OS), preselection is saving work. When it does not, the same preselection becomes a silent proxy. The test is not “is there a statistically common value,” but “if we pin this value on someone who has not spoken, is the worst case acceptable.” If the worst case is not, leave empty.
Where it stops holding
Immediate switch fields almost always have a current system state — an actual, not a default strategy; do not read “it is off now” as “we chose off for you.” In a wizard, a later step may depend on an earlier choice; the earlier step must stay empty and block Next, or the later step unfolds on a false premise. Legally required collection can still stay empty until submit; empty and “refuse to answer” must be stored apart — the latter is an explicit option, the former is indecision. Assistive-tech users need to know the field is still empty; visually unfilled dots are not enough, and the group label should say required and not yet chosen.
Applying it
- List the worst mistaken default for each choice field; if it is unacceptable, start empty and block on that group at submit.
- Do not use the first roster item, API order, or “what looks tidy” as a placeholder default.
- Surface the empty error at submit or on leaving the step, not as a red flash the moment the question appears.
- How to check: submit without touching any option — it should block on that field. Then preload a value, have someone fill the form, and ask “did you choose this.” If many say “it was already like that,” the default already spoke for them.