Heuristic
Make the safe routine action the default
Defaults spend less vigilance than reminders.
Before you use it
- Use when
- Most cases should follow one safer or more reliable path but the interface starts from a neutral or risky state.
Keep this limit in mind
- Defaults can manipulate behavior and can be dangerous when case variation is substantial; use them transparently.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
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.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMake the safe routine action the default
Evidence and sources
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
Edition and review
Version 0.1.0
No review details are supplied for this edition.