Cognitive biases in software development. Part 4. Bias mitigation strategies

4th part, other posts — first part, second part, third part.

Chip and Dale to the rescue!

However it may be very beneficial to know what cognitive bias is running your logical reasoning (either at the time of reasoning by observing your reasoning or after having reasoned by observing the outcome of your reasoning). If you can recognize the bias you can consider the cost and payoff of having that bias run your thinking. If proceeding with the bias is beneficial in a particular context you can let the bias inform you and act on it (it can be a form of heuristics) or discard the bias and select another bias or more rational thinking.

The danger is in being blind to what cognitive bias is currently coloring your world view. When not recognized the Bias itself becomes a ‘thinking driver’ where the world view and conclusions of situations in a given context are limited by the bias. So, before any big decision, make sure you’re not falling prey to these cognitive biases by stepping back and asking:

• Why do you believe a certain way? (Search for more information & data , Play Devil’s Advocate, Reflect on your own views & values)
• What are the counterarguments to your opinion? Are they valid?
• Who is influencing your beliefs?
• Are you following the group because it’s what you actually believe?
• What will you lose if you make this decision? What will you gain?

And keep being suspicious :)