Treat defaults as intentional decisions.
Design every default as a behavioral commitment, not a temporary filler.
Contents 4. System Behavior & Workflow Logic 1. Defaults
What a system chooses on users’ behalf.
First, ask yourself
“Do defaults in your system reliably help users without harming control or trust?”
Mission statement
Ensure users start efficiently by providing appropriate preset choices.
Key heuristics Defaults
- Every default must represent a deliberate behavioral commitment.
- Defaults must reduce user workload.
- The consequences of accepting a default must be clear.
- The scope of default effects must be visible.
- Defaults must be easily changeable.
- Changing or applying defaults must not silently destroy user work.
- Defaults may adapt to task or environment when appropriate.
- Defaults that users consistently correct must be removed or revised.
Executive brief
The system must treat defaults as accountable decisions on users’ behalf, not neutral conveniences.
Core questions Defaults
“Do defaults guide effectively without restricting control?”
“Can users see, understand, and override them?”
Focus areas
Agency-first
“Where is the system acting instead of asking?”
“What decisions are pre-selected for the user?”
Risk-aware
“What happens if the default is accepted blindly?”
“Is the default safe under uncertainty?”
Transparency-aware
“Are the reasons for defaults visible and understandable?”
“Can users predict the impact of accepting or changing defaults?”
AI-aware
“Is the default static or inferred from user activity by the system?”
“Does adaptation remain predictable over time?”
UX directives Defaults
Use defaults to remove effort.
Make sure defaults reduce user workload, not introduce hesitation.
Make default implications explicit.
Ensure users understand what accepting a default will do.
Clarify the scope of default effects.
Indicate whether a default applies locally, globally, or persistently.
Ensure defaults are easily overridable.
Allow users to change defaults without friction.
Protect user work when defaults change.
Prevent silent data loss or destructive resets triggered by defaults.
Adapt defaults to context when appropriate.
Use task or environment signals to refine default values responsibly.
Remove unreliable or misleading defaults.
Eliminate defaults that users consistently correct.
Executive summary
- Defaults are behavioral commitments, not placeholder values.
- They shape user action by defining what happens if no change is made.
- The system must design defaults to reduce effort while making their implications explicit.
- Defaults must be easily overridable and never silently compromise user work.
- Context-aware defaults are valid only when they align with user intent and expectation.
- Defaults succeed when users rarely need to change them and never suffer from accepting them.
Success indicators
- Default settings reduce the amount of work users must do.
- Users can clearly see what the default choice will do.
- The scope of a default is easy to understand.
- Defaults can be changed quickly and easily.
- Defaults match common user needs and rarely require correction.
One-line summary
Before users can begin efficiently, the system must make reasonable choices on their behalf.