This week on the show we’re talking to Maaike Brinkhof about cognitive biases! There are so many biases, but we talk about a few here, and share some resources for learning more.
Why are we biased?
- Too much information → We filter it
- Not enough meaning → We fill in the gaps
- The need to act fast → We want to feel in control
- What should we remember? → We pick out what stands out
Is it a bad thing or a blessing in disguise?
As with all things it can be both. Biases are evolutionary as brains can’t process everything, but they can be a crutch, a mental shortcut which can cause issues.
If you view biases as a bad thing, then you’re missing the point. You can choose to view it as something you can learn more about and getting to know more about yourself – such as learning to recognise when you might be biased and trying to adjust your behaviour.
Biases in testing – its not just about your own biases
Often when we are testing, we are looking for problems caused by biases from people around us, such as the biases of developers or project managers. Often people will write their own biases into products without realising it.
We also have to be aware of our own biases guiding us, hiding or obscuring information. We might like to think we are objective in our thinking, but we are not perfect either.
Understanding biases can also help you explain and justify your testing, questions, problems or information that you’re providing to people.
Lets talk about some biases!
Confirmation bias (the biggest bias of all, and can be broken down into several ‘smaller’ biases, for example the ones below):
How do you deal with biases?
- Work alone less and pair or mob more
- Focus and de-focus
- Self-awareness of your own concentration levels and behaviours
- Awareness of biases
- Referring to and using heuristics
- Stepping back and examining your thinking, concentration, and working patterns to avoid relying on biases to take shortcuts.
Books and courses we’ve mentioned