status-quo-bias

When to use

• Planning product migrations.
• Introducing new features or workflows.
• Designing defaults.
• Reducing resistance to adoption or switching.
• Explaining why users keep old behavior.

Goal

Make change feel lower risk than staying still. Reduce effort, uncertainty, and perceived loss.

Rules

• Identify what users lose by changing.
• Preserve familiar workflows where possible.
• Use smart defaults.
• Make change reversible when possible.
• Show clear benefit before asking for effort.
• Let users transition gradually for risky changes.
• Do not force change without support.

Resistance Sources

• Loss aversion: change feels like giving something up.
• Cognitive cost: learning a new path takes effort.
• Uncertainty: user does not know what happens next.
• Switching cost: migration, setup, data, or team coordination.
• Identity or habit: old way feels safer.

Strategies

• Smart defaults: make best option the easiest option.
• Gradual transition: introduce change in steps.
• Risk reversal: backup, undo, rollback, trial.
• Parallel running: old and new workflows overlap temporarily.
• Clear migration help: import, setup, checklist, support.
• Loss framing reversal: show cost of staying unchanged.

Flow

1. Define current behavior.
2. Define desired behavior.
3. List perceived losses and effort.
4. Identify risks of staying the same.
5. Design a low-friction transition path.
6. Add support, reversibility, and defaults.
7. Measure adoption and fallback usage.

Metrics

• Adoption rate.
• Migration completion.
• Time to first successful use.
• Rollback or opt-out rate.
• Support tickets.
• Feature retention after first use.

Output

## Status Quo Bias Analysis
- Current state:
- Desired state:
- Resistance points:
- Transition design:
- Defaults:
- Risk reversal:
- Metrics: