Thinking in testing: Are we missing the questions we should be asking

Running a root cause analysis only addresses half of the problem. Instead of asking, why did we miss this. Ask, why didn’t we think of this? 

 

Fixing a process or writing a missing automated test only fixes half the problem. When a bug slips into production. the standard response is to run a root cause analysis. We look at the logs, find gaps in our testing, maybe add a new safeguard to the pipeline. We feel good because we fixed the immediate issue. But all we really did was patch a hole in our process. 

We rarely stop to ask the harder question. Instead of just asking ‘Why did we miss this?’ or ‘Where is the gap in our process?’ We should also be asking. ‘Why didn't we think about this?’ or ‘Where is the gap in our thinking?'  

Fixing a process feels easier as it is something we are much more familiar with. Changing how we think is a much harder endeavour. We invest our time building our skills and knowledge. But we too rarely train our brains to think more deeply, more widely, or from multiple perspectives. 

If we only focus on that missing test. We just prevent that exact bug from happening again. If we focus on the gap in our thinking, we have the possibility of finding categories of problems before they ever make it into the product. Process, tests, and automation are essential. But they are only as good as the thought patterns behind them. 

If you want to improve quality, stop looking only at where your process failed. Start looking at how your thinking can evolve.