A default is the state a system adopts when a person has not actively specified one. It may look as though nothing has happened, but it actually turns “no selection” into an executable outcome.
When a new document is created, for example, software may preselect a file format. Most people can continue working without deciding again each time. Yet if that format is poor for long-term archiving, the same default will also guide many files towards the same consequence. Defaults reduce the cost of repeated decisions while embedding a designer’s judgement about what normally applies.
A default is not the same as a convention. A convention depends on participants following a shared practice; a default takes effect when an individual makes no choice. Nor is it a neutral starting point, because leaving it unchanged already shapes the outcome. A good default should suit common cases, remain visible and easy to change, and require confirmation when the consequences matter. What defaults really address is the fact that a system cannot wait indefinitely for a choice.
Discover more from Geoffrey Chen
Subscribe to get the latest posts sent to your email.