Silent defaults
The system applies defaults without showing them. Users who need different settings find out when results are wrong.
Table of Contents
Summarize with:
Key facts
- Showing which defaults were applied lets those users catch the problem early.
- Configurations look complete and behave unexpectedly.
- Users with the same visible setup get different results.
- Limited date-range defaults keep screens fast and hide older records from users who do not know to widen the range.
- Support answers that start with a hidden setting are a sign of silent defaults.
How to spot it
- Configurations that look complete and behave unexpectedly
- Support answers that start with a hidden setting
- Different results for users with the same visible setup
- Users cannot find older records that exist
Why it happens
Defaults chosen to shorten setup. Optional settings are moved out of the first run, and the values chosen for them are not shown.
Defaults set by developers. Values chosen during development to make a feature work become product behaviour without a design decision.
Design consideration
Settings stored far from results
The screen that shows a result does not say which settings produced it.
What it costs
- Wrong results nobody notices. Users who need different settings find out when results are wrong.
- Support load. Answers start with a hidden setting, and the same answer is given repeatedly.
- Lost trust. Users who cannot explain a result stop trusting the screen and check figures elsewhere.
Where it shows up