Heuristic
Make the safe routine action the default
Defaults spend less vigilance than reminders.
When it fits
- Most cases should follow one safer or more reliable path but the interface starts from a neutral or risky state.
When to avoid it
- Defaults can manipulate behavior and can be dangerous when case variation is substantial; use them transparently.
Why it matters
Preselect or preconfigure the preferred safe path when it is correct for the majority of cases and easy to review. Require an explicit opt-out for exceptions and record the reason when stakes justify it. The default should reduce routine omission without hiding meaningful choice.
An example
New automated agents begin read-only and require an explicit permission change for write access.
Check your result
Routine cases reach the safer state without relying on users remembering to select it every time.
Keep this limit in mind
- Defaults can manipulate behavior and can be dangerous when case variation is substantial; use them transparently.
Connected ideas
Useful withUse a forcing function for the irreversible step
Evidence and sources
Supports
AHRQ reliability guidance identifies safe defaults as a way to make the preferred action easier while still permitting explicit opt-out when appropriate.
Defaults can become coercive or wrong when the preferred action depends strongly on context.
Implement the VTE Prevention Protocol: Design Reliability Into the Process · Default action