The term “confirmation bias” was coined in the 1960s, by English psychologist Peter Wason. His experiments showed that individuals are inclined to seek information that confirms their existing beliefs, which is something that is a fundamental aspect of human cognition.

This bias has evolutionary roots, potentially as a mechanism to quickly process information and make fast decisions based on past experiences and beliefs.

The rise of behavioral economics in the late 20th and early 21st centuries, spearheaded by researchers like Daniel Kahneman and Amos Tversky, brought a renewed focus on confirmation bias. Their work illustrated how confirmation bias is not just a passive process of accepting confirming evidence but actively seeking it, even in the face of contradictory information.

The internet and social media has further amplified the significance of confirmation bias. The ability to access incredible amounts of information and connect with like-minded individuals has created echo chambers, where confirmation bias can significantly influence public opinion and the spread of misinformation.

On software teams, confirmation bias can significantly impact how products are developed and perceived. For example, a product manager might favor market data that supports their vision while ignoring data that might suggest a different direction is appropriate. UX designers might prefer user feedback that supports their original design choices, overlooking critical feedback that suggests significant changes. Engineers could overlook potential flaws in their systems, focusing instead on evidence that validates their work.