Decision default design: practical guide
Decision default design is the creation of a reversible rule for a recurring choice with a known owner and exception condition.
Quick answer
Write the recurring choice as an if–then rule with an explicit exception.
What this guide is best for: readers who need to make a concrete decision about decision default design.
How do you put this into practice?
Use the following sequence as a starting plan, then adjust it to the work you are responsible for.
- Write the recurring choice as an if–then rule with an explicit exception.
- Test the default against a recent real case before applying it routinely.
- Record the action you chose, its intended result and the next occasion on which you will check it. Keep the record in a place you can return to without rebuilding your setup.
How do the options compare?
| Checkpoint | Record |
|---|---|
| Failure to avoid | Do not use a default to override safety, consent or an obligation requiring individual review |
What would this look like in practice?
A coordinator defaults routine updates to a shared document but makes an exception when an urgent deadline requires direct contact. This is an illustrative scenario, not a customer result or evidence of a measured improvement.
Which planning principle supports the method?
The National Cancer Institute’s archived implementation-intentions resource describes if–then plans that connect a situational cue with an intended action. Spry’s examples here are editorial applications of that planning idea, not evidence that this particular guide or product produces a measured outcome. The source is retained for reference and is no longer maintained.
Source reviewed 2 November 2026.