What it is
Status quo bias is the preference for the current state of affairs, expressed as resistance to change that is disproportionate to the actual costs of changing. It is related to loss aversion but distinct from it: status quo bias operates even when the potential gain from changing clearly exceeds the transition cost. The current arrangement is treated as the reference point, and any deviation from it is experienced as a loss rather than an opportunity.
Where it shows up
In SaaS replacement decisions, status quo bias is one of the most consistent sources of delay. Teams know a platform is under-delivering - poor integration, limited configurability, high per-seat cost at scale - but the friction of change feels larger than the ongoing cost of staying. The comparison is rarely made explicit: the full cost of the status quo, including the opportunity cost of foregone capability, is seldom written down and weighed against the transition cost with the same rigour.
What Rubicon Probity does
When Rubicon Probity processes a decision record at the Decide stage where the analysis explicitly or implicitly treats the current arrangement as the default and alternatives as requiring extraordinary justification, it raises a NOTE flag and requests that the cost of inaction be documented with the same level of detail as the cost of change. Both directions must be held to the same evidential standard.
Detection questions
- Have you calculated the full ongoing cost of the status quo - including capability gaps, integration overhead, and opportunity cost - at the same level of detail as the transition cost?
- Is the current arrangement performing to its original specification, or are you staying because switching feels difficult rather than because the current state is delivering?
- If you were choosing from a clean slate today, with no switching cost, would you select the current arrangement?