Last updated on April 11, 2024
Confirmation bias – the tendency to discredit non-confirmative evidence, or to seek out (actively or subconsciously) primarily confirming evidence – is part of all of us. We all suffer from it, every day. As technologist, we could do better. We should always re-evaluate all the facts and not fall into the traps of our dogma/orthodoxy – what we see or want to see.
Rather than reviewing all the facts, we too often hold onto our beliefs. Ask a front-end developer which library/framework should be used for a given project, it’s rarely followed by a question on what the requirements are. Rather, if they are a ReactJS developer, they will automatically respond with ReactJS. An Angular developer is no different. We end up choosing a solution first then justify its fit. Just ask why ReactJS is better solution, they will point to facts like, “it’s the most downloaded library”
By that logic, I should just go buy a Ford F-Series truck. If I’m an eco-friendly individual that never needs the truck to carry loads, maybe I don’t need a truck. Maybe an electric vehicle is a better fit. Yet, because it is the most sold vehicle in America, do you think it’s the right fit. Failure to take into considerations of the facts of the requirements and/or the make-up of the engineering team, we do a disservice to our clients/customers.
How to Avoid Confirmation Bias?
Discuss your thoughts with others. Don’t jump to conclusions. Gather as much facts. Surround yourself with a diverse group of people, and don’t be afraid to listen. The simplest way to avoid confirmation bias is to look at your own beliefs. Search out ways in which your default solution may be wrong, rather than the ways in which it is right. Always be learning. Seek out competitive solutions and learn from it.
