i

Description

Un sentier de terre battue qui traverse la steppe d'armoise, sur le tracé d'une ancienne piste de pionniers.

Source

BLM Oregon & Washington · original page

Licence

PD Public domain

Original photo, unretouched. The background is a version of it stylised by the site.

The status quo bias

What already exists gets a head start: the default option is chosen more often, simply because it is there.

In brief

• What: an option is chosen more often when it is the current situation or the default option, regardless of its value.
• Why: loss aversion, the effort cost of making a decision, fear of regretting having acted, and the idea that “the default is what most people choose.”
• Detect: “we've always done it this way”; the current solution has never been compared to another; a default setting never changed.
• Avoid: ask whether you would choose the current setup if starting from scratch, periodically review what exists, and carefully design default values.

On this page

1. Definition
2. The mechanism
3. Where you encounter it
   1. In project management
   2. In management
4. Famous cases
   1. Automatic enrollment in retirement savings 2001
   2. Organ donation: presumed or explicit consent 2003
   3. Where to invest an inheritance 1988
   4. UIMM: a fund financed since 1972 (France) 1972-2015
   5. The Pinel scheme: three successive extensions (France) 2014-2024
5. Detection signals
6. Avoidance reflexes
7. With AI: detect, fix, mitigate
   1. Detect
   2. Fix
   3. Mitigate
   4. Prompts to integrate into your practices
   5. How to integrate them
   6. Precautions
8. Limits
9. Sources and verification
10. See also
    1. Combines with, or reinforces
    2. Related biases
    3. Counterweights and related reflexes

Definition#

Fictitious illustration

Fictitious illustration

Fictitious illustration

Fictitious illustration

The status quo bias is the tendency to prefer the current situation, or the default option, over an alternative, even if the latter would be better. William Samuelson and Richard Zeckhauser described it in 1988 based on experiments where the same option was chosen more often when it was presented as “the current situation.”

It appears in two related ways: inertia (not acting, not changing) and the default option effect (choosing what is offered automatically). Kahneman, Knetsch, and Thaler (1991) tie it to loss aversion and the endowment effect.

It is not synonymous with laziness. Sticking with what exists can be a thoughtful choice; bias appears when what exists is preferred because it exists, without comparison.

The mechanism#

Several explanations complement one another:

• Loss aversion: changing makes concrete losses (habits, acquired benefits) stand out more than the promised gains (see Loss aversion).
• Decision cost: choosing requires time, information, and attention; the default option saves all three.
• Anticipated regret: a mistake made by acting is felt more strongly than a mistake from inaction (see Omission bias).
• Implicit signal: the default is read as a recommendation (“if it's there, it's because it suits most people”).
• Familiarity: what we know feels safer; the risks of the unknown are easier to imagine than those of what already exists.

Where you encounter it#

In project management#

• Architecture evolution: the current monolith, database, or framework is kept not because it fits, but because “everyone knows it”; the alternative must prove superiority, while the current setup has nothing to prove.
• Method change: a delivery process or ceremony is kept without even knowing what it is for anymore, because removing it would look like taking a risk.
• Tool choices: the same tracking, continuous integration, or monitoring tool is renewed year after year, with no comparison to recent options.
• Contract renewal: the vendor or license is tacitly renewed; the RFP is set aside “to avoid disruption.”
• Default values: settings shipped with software (timeout, logging level, access rights) remain as-is, even when they are unsuitable or insecure.
• Updates: teams stay on an old component version until end of support, because upgrading requires a decision.

In management#

• Team organization: the org chart, roles, and recurring meetings are carried over as-is, even though no one has evaluated them in years.
• Assignment allocation: the same people are assigned to the same topics, which slows cross-functionality and knowledge transfer.
• Compensation and evaluation policy: a grid or schedule is kept because “that's the rule.”
• Personal decisions: the employee stays in their role, team, or company out of inertia, more than by choice.

Famous cases#

Detection signals#

• “We've always done it this way.”
• “It works, let's not touch it”: with no measurement of what it costs not to touch it.
• The existing solution has never been compared to another one since adoption.
• A default setting has never been changed since installation, and no one knows why.
• The alternative must provide overwhelming proof; the current solution does not.
• Tacit or automatic renewals (contracts, licenses, recurring meetings) are never questioned.

Avoidance reflexes#

1. Start from scratch. “If we had nothing today, would we choose the current option over the alternative?” Reversing the starting point removes the status quo's head start.
2. Require the same proof from both sides. If the alternative must demonstrate costs and benefits, the current solution must too (operating cost, debt, risks, end of support).
3. Quantify the cost of staying put. Maintenance, licenses, wasted time, obsolescence risk, hiring difficulty: this cost is real, but invisible until written down.
4. Plan periodic reviews. Once a year, each tool, contract, process, or recurring meeting is justified or stopped; renewal becomes a decision.
5. Handle default values carefully. When you design a product, template, or process, choose the default you would want for the majority (Thaler and Sunstein's “choice architecture” principle).
6. Use end dates. A contract, pilot, or rule with a deadline forces a decision on what comes next instead of letting the status quo settle in.
7. Try it on a small scope. A reversible pilot reduces perceived loss and provides data on the alternative.

With AI: detect, fix, mitigate#

Prompts to integrate into your practices#

1. Compare the current state and alternatives on equal footing. Before renewing a tool, contract, or architecture.

Here is the current solution: [description, cost, usage, known issues]. Here is the need and constraints: [need, constraints, timeline].
1. Assume we have not deployed anything yet. Propose three plausible alternatives, including the current solution, and compare them using the same criteria (two-year cost, risks, transition effort, required skills, long-term support).
2. For each criterion, indicate what is measured and what is assumed.
3. Say which option you would choose starting from scratch, then what it would cost to move from the current one to that one.
Do not cite any product or number you are not sure about: flag what needs to be verified.

2. Default values review. During an annual review of a product, environment, or process.

Here is the list of parameters, rules, or rituals we have never changed since implementation: [list with values].
For each one: (1) what it does and who benefits, (2) what a different choice could change, (3) the question to ask its owner to know whether it is still appropriate.
Classify them into three groups: keep as is, verify, change. Do not assume that “default” means “good.”

How to integrate them#

• Before a renewal: prompt 1 produces the comparison; the team adjusts the values using its own numbers.
• Every year: prompt 2 prepares the review of inherited settings and rituals.
• For every new product: document the chosen default and why it was chosen.

Precautions#

• AI favors the most widespread solutions in its data: a proposed “safe choice” is not a recommendation tailored to your context.
• The quantified comparisons it proposes are orders of magnitude; measure before deciding.
• Verify cited references and features: they may be inaccurate or outdated.
• Do not send confidential contracts, pricing, or architectures to an unauthorized tool.

Limits#

• Inertia can be rational: changing has transition, learning, and risk costs; keeping what works is often the right decision. The bias is preferring the current state regardless of those costs.
• Defaults also act as information: a vendor default setting was often chosen for good reasons. The problem is never checking it.
• Part of default effects is explained by distraction or procrastination rather than a preference for the status quo; the mechanisms are hard to separate.
• Field studies (retirement, organ donation) concern specific populations and systems; the size of the effect varies by context, and enrollment rates are not actual donation rates.
• The boundary with the The endowment effect and Loss aversion is blurry: the status quo is often presented as their consequence.

Sources and verification#

• Samuelson & Zeckhauser (1988), “Status quo bias in decision making,” Journal of Risk and Uncertainty — experiments and health insurance data.
• Kahneman, Knetsch & Thaler (1991), “Anomalies: The Endowment Effect, Loss Aversion, and Status Quo Bias,” Journal of Economic Perspectives
• Madrian & Shea (2001), “The Power of Suggestion: Inertia in 401(k) Participation and Savings Behavior,” The Quarterly Journal of Economics — 37% and 86%.
• Johnson & Goldstein (2003), “Do Defaults Save Lives?,” Science — organ donation consent rates by country.
• Thaler & Sunstein (2008), Nudge: Improving Decisions About Health, Wealth, and Happiness, Yale University Press — choice architecture and default options.
• franceinfo (October 2013), “UIMM trial: Gautier-Sauvagnac confirms cash donations” — reports the defendant's statements on how old the practice was and his predecessor's role.
• France Bleu / ici (February 10, 2014), “Employers' slush fund: one year in prison for the former head of UIMM” — reports the Paris criminal court ruling: sentence, amount, and central knowing participation.
• Wikipedia, “UIMM slush fund case” — 2007-2015 timeline (Tracfin, EPIM, ruling, appeal of December 1, 2015); secondary source, to be cross-checked with court decisions.
• Cour des comptes (2024), “Tax support for Pinel rental investment,” thematic public report — traces successive extensions of the program and operators' dependence on these supports.
• Cour des comptes (2018), “Tax expenditures in favor of household rental investment” — concludes low effectiveness in the number of accessible rental units and calls for a gradual phase-out of these programs.

See also#