status-quo-bias_skill

Overview

This skill helps you identify and design for users' preference for the current state over change. It provides practical patterns to reduce resistance, use defaults ethically, and plan migrations or feature rollouts that users will accept. Use it to increase adoption while avoiding manipulative tactics.

How this skill works

The skill inspects user attachment to existing workflows, perceived risks, and cognitive costs of switching. It recommends interventions—smart defaults, gradual transitions, loss-framing, parallel running, and easy reversal—and maps those to concrete design steps and success metrics. It also flags ethical pitfalls and suggests measurable experiments to test adoption.

When to use it

• Planning product migrations or UI overhauls
• Introducing major new features or workflows
• Designing default settings and opt-out flows
• Onboarding users who must replace old tools or habits
• Updating pricing, policies, or account structures

Best practices

• Set beneficial defaults that protect users and require explicit opt-out
• Break big changes into incremental steps with visible progress
• Frame messaging around costs of not switching, not just feature gains
• Provide reversible trials or parallel running to reduce perceived risk
• Automate data/settings migration and preserve familiar elements

Example use cases

• Migrating enterprise customers to a new dashboard via phased rollout and one-click rollback
• Introducing a privacy-forward default while giving easy opt-out and clear rationale
• Rolling out a redesigned editor as an opt-in preview with saved drafts and side-by-side view
• Changing subscription tiers while grandfathering existing users and highlighting exact costs of staying on old plan
• Onboarding users from a competitor by importing configurations and showing a quick first success