Pre-fill fields and pre-select options with intelligent guesses to save user effort and reduce errors. Defaults also serve as examples, showing users the expected answer format.
Types of defaults
Mass defaults
Apply to all users universally.
- Benign defaults: The “best guess” for the majority (e.g., standard shipping).
- Occasional-use interfaces: In installers or setup wizards, users often prefer “whatever the system decides” to save effort.
- Smart defaults: Optimization based on general data (e.g., current location, time, or session metadata).
- Random defaults: Arbitrary assignment when no preference exists.
Personalized defaults
Tailored to the individual actor.
- Persistent defaults: Based on the user’s past choices (e.g., “Use my last address”).
- Adaptive defaults: Updated in real-time based on immediate context or behavior.
Risks & ethical considerations
- Dark patterns: “Hidden options” or pre-checking consent boxes (e.g., for marketing) exploits the default effect to the user’s detriment.
- Social signaling: In some contexts, the default changes the meaning of the choice (e.g., opting out feels like a stronger rejection than not opting in).
- Sensitive data risks: Avoid defaults for identity (gender, citizenship) or sensitive choices. Pre-filling these can make users uncomfortable or imply assumptions.
- Status quo bias: Users rarely change defaults.
- Invisibility: Users might not notice a default value and submit incorrect data.
- Blindness: If a user can skip a field, the question might not “register” mentally, reducing their understanding of the system settings.
Resources
- UI Patterns - Good Defaults
- NN/g - The Power of Defaults
- Wikipedia - Default effect
- Tidwell, Brewer, Valencia (2020) Designing Interfaces, 3rd ed.
Related patterns
Precedes
- Localization — locale detection and sensible starting configuration
- Autocomplete — fields hold the system's best static guess — which serves only until the actor starts typing a value of their own; completion then has to happen in flight rather than up front
- Autofill — a good default is a guess made without the actor's stored data; where the system already holds the actual value, pre-filling from the record takes over from guessing
- Assisted task completion — pre-population ends where the task needs the system to participate in the work itself — the assisted-completion spectrum picks up where a static guess stops sufficing
Enacts
- Agency — a default is the system making the small decision so the actor doesn't have to; the actor still has the final say but doesn't have to spend it on this field
Complements
- Bounded choice — pre-selecting the likely value can resolve the choice before the actor engages with it
- Progressive disclosure — what is visible by default is the first disclosure decision
Alternatives
- Data entry — The alternative when a default cannot be guessed
Related
- Onboarding — Often sets the initial state and defaults for the application
- Settings — Where global defaults are managed and overridden
- Suggestion — A weaker form of default ("Did you mean X?") or a dynamic default
Hosted by
- Form — form fields are the primary surface where defaults are encountered