# Status Quo Bias

> Design for user resistance to change and preference for the current state. Use when planning migrations, defaults, switching paths, feature adoption, workflow replacement, or rollout risk; distinguish from loss aversion by focusing on change friction, reversibility, and transition design.

- Skill: `flpbalada/status-quo-bias` (Agent Skill)
- Install (CLI): `npx skillmds@latest add flpbalada/status-quo-bias`
- Raw SKILL.md: https://api.skillmd.com/api/skills/flpbalada/status-quo-bias/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity, Coding & Dev Tools
- Author: flpbalada (https://skillmd.com/u/flpbalada)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/flpbalada/status-quo-bias

---


# Status Quo Bias

## 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.

## Resources

- [Nudge - Richard Thaler & Cass Sunstein](https://www.amazon.com/Nudge-Improving-Decisions-Health-Happiness/dp/014311526X)
- [Thinking, Fast and Slow - Daniel Kahneman](https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555)
- [Status Quo Bias in Decision Making - Samuelson & Zeckhauser](https://scholar.harvard.edu/rzeckhauser/publications/status-quo-bias-decision-making)

## Output

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