Status Quo Bias has been a subject of interest in behavioral economics and psychology since the late 20th century. It was initially applied in the context of consumer behavior and investment decisions.

Early studies in these areas revealed that people were more likely to keep their money in the same bank accounts, continue with the same insurance policies, or hold onto the same stocks, even when there were financially better options available.

The bias was attributed to various factors, including the fear of making a wrong decision, the emotional comfort of sticking with the familiar, and the cognitive effort required to evaluate new options.

In team settings, the bias can manifest in resistance to new technologies or methodologies, leading to inefficiencies and missed opportunities.

Status Quo Bias can manifest itself in different ways across the software development lifecycle. UX designers may hesitate to experiment with new design paradigms, sticking to tried-and-true interactions even when data suggests a need for change. Product managers may shy away from taking calculated risks, opting instead to maintain existing features. Engineers may avoid migrating to newer, more efficient technologies due to the comfort and familiarity of legacy systems. On a broader scale, software teams may resist adopting more agile or efficient methodologies, clinging to traditional approaches despite their limitations.