status-quo-bias

Diagnose status quo bias and design adoption interventions with transition plans.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Chris-Maskey/opencode-config --skill status-quo-bias-chris-maskey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-quo-bias
Source: https://github.com/Chris-Maskey/opencode-config/tree/main/skills/status-quo-bias
Command: npx skills add https://github.com/Chris-Maskey/opencode-config --skill status-quo-bias-chris-maskey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many users prefer the current state and resist change, causing low adoption of new features, failed migrations, and poor uptake of beneficial defaults; this skill helps teams diagnose that resistance and design strategies to overcome it.

Core Features & Use Cases

  • Diagnosis Frameworks: Assess habit strength, perceived losses, cognitive effort, and sunk costs to identify resistance points.
  • Design Strategies: Recommend smart defaults, gradual transitions, loss-framed messaging, parallel running, and reversible migrations to lower barriers.
  • Templates & Metrics: Provide an analysis template, the EASE framework, messaging patterns, and success metrics for migrations, onboarding, feature adoption, and pricing changes.
  • Ethics Guidance: Advise on responsible defaults and warn against dark patterns like hidden opt-outs or artificial switching costs.

Quick Start

Analyze the proposed feature change, identify status quo resistance points, and recommend a stepwise transition plan with smart defaults, loss-framed messaging, safety nets, and measurable success metrics.

Frequently Asked Questions about status-quo-bias

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why do users resist new features during a product migration?

Users resist product migration due to status quo bias, where perceived losses, cognitive effort, and habit strength outweigh the benefits of adopting new workflows. This resistance causes low feature adoption and failed rollouts.

How do I design onboarding flows to improve feature adoption?

Improve feature adoption by designing onboarding flows that use smart defaults, gradual transitions, and loss-framed messaging. These behavioral design strategies lower cognitive effort and reduce user resistance to new workflows.

What is the best way to plan a product migration without losing users?

Plan a product migration by offering reversible migration paths, parallel running, and safety nets. Analyzing user habits and current defaults helps recommend stepwise transitions that prevent user drop-off during feature rollouts.

How does loss-framed messaging help with pricing changes?

Loss-framed messaging helps with pricing changes by highlighting what users stand to lose without the new plan, leveraging loss aversion to encourage adoption while maintaining responsible defaults and avoiding artificial switching costs.

Can I use smart defaults to increase adoption of new workflows?

Yes, setting smart defaults increases new workflow adoption by reducing the cognitive effort required to switch. Applying behavioral design principles ensures defaults are responsible and effectively guide users through transitions.

When should I avoid using behavioral design for feature rollouts?

Avoid using behavioral design for feature rollouts when it leads to dark patterns like hidden opt-outs or artificial switching costs. Ensure transition plans and messaging respect user autonomy and avoid unethical manipulation.