Defaults & starting states
Before anyone changes a setting, software has already made a choice.
The starting point
A default is the value or behavior used when someone has not selected an alternative. It can make a first encounter simpler, but it can also pass unnoticed. Language, sort order, visibility, and reminder frequency all shape what happens before a person begins customizing an experience.
The visible choice
A setting is easier to evaluate when its current value and effect are both clear. Labels such as “recommended” need context: recommended for whom, and under what conditions? A starting state should remain distinguishable from a deliberate choice the person has made.
The return path
Changing a default raises another question: can the person restore it later? Resetting one preference is different from resetting an entire workspace. A clear explanation of the scope helps prevent a small adjustment from becoming an unexpected loss of personal setup.
Defaults deserve attention because they can become habits. Examining them is a way to understand the experience before adding more options.
Continue to recovery ↗