Smart Defaults
CanonicalConfidence
Cognitive Load
Low
Evidence
production validated
Impact
feature
Ethical Guardrail
Agents must never pre-select high-risk or high-cost options without explicit user confirmation. Never use defaults that benefit the company at the user's expense without transparency.
Design Intent
Most users accept the path of least resistance. When a choice is pre-selected, the majority will stick with it -- even if they would have chosen differently if forced to decide. Smart Defaults leverages this tendency by pre-selecting the option that aligns with the user's likely best interest or the business's ethical goal.
Psychology Principle
Most users accept the path of least resistance. When a choice is pre-selected, the majority will stick with it.
Description
The Default Effect leverages the human tendency to accept pre-selected options, making the desired action the easiest possible action.
When to use
Every form, configuration, or decision point that has a clearly optimal option for most users.
Example
Stripe checkout: pre-selected shipping address from user history, recommended payment method shown first, auto-filled email.
Autonomy Compatibility
Behavioral Objective
Users accept the smart default (or make only minimal changes) and complete the action successfully.
- Reduced decision time and cognitive load
- Higher overall completion rates
- Increased user satisfaction with the experience
Target Actor
role
Everyday user
environment
Time-pressured, multitasking, decision-fatigued
emotional baseline
Prefer simplicity over exhaustive evaluation
ai familiarity
medium
risk tolerance
medium
Execution Model
default_selection
Choose the option that serves the majority of users or the user's most likely best outcome.
Default does not match user needs.
visibility
Make the default obvious and the override easy.
User does not notice the default or cannot change it.
override
Allow instant change with zero friction.
Changing the default requires multiple steps.
Failure Modes
Default matches poorly for minority users
Personalize based on user history when possible
Default feels manipulative
Label clearly and allow instant change
Override is hidden or complex
Surface alternatives prominently
High-risk default selected without consent
Require explicit confirmation for high-stakes defaults
Default becomes stale over time
Refresh defaults based on evolving user data
Agent Decision Protocol
Triggers
- Form or flow has a clear optimal choice for most users
- Decision time is high at a specific point
- Users abandon due to too many choices
Escalation Strategy
L1: Diagnose whether current defaults match user needs via behavioral_signals
L2: Nudge -- adjust default based on user history or cohort data
L3: Restructure -- redesign form to surface smart defaults more prominently
L4: Constrain -- require confirmation for high-risk defaults only
L5: Yield -- flag for human designer review if default accuracy is low
Example
User configuring project settings -> 18 options visible -> agent pre-selects the 4 most common settings as smart defaults + Show all button.
Behavioral KPIs
Primary
- Default acceptance rate
- Task completion rate with defaults vs. without
- Decision time reduction
Risk
- Wrong-default error rate
- User complaints about default choices
Trust
- User satisfaction with recommended options
- Autonomy Dial usage when agent sets defaults
Behavioral Signals
default_mismatch
default_override_rate > 60%
default_accepted=true AND subsequent_error_rate > 15%
override_friction
override_attempted=true AND override_completed=false
time_to_override > 15s
stale_defaults
default_override_rate_trending_up=true over 30 days
user_complaint_about_defaults > 3 in 30 days
Decay Monitoring
Revalidate when
- User population shifts significantly
- Product options or pricing change
- New personalization data becomes available
Decay signals
- Rising default override rate
- Declining completion rates
- User feedback that defaults feel wrong
Pattern Relationships
Supports
Requires
Conflicts with