When something goes wrong in an organisation, it can be tempting to focus on what happened, mop up the mess and move on. An employee sent an email to the wrong person. A sensitive document was shared accidentally. A process wasn't followed correctly. Human Error can be a tempting category to slot them under. But simply calling it human error doesn't necessarily explain why it happened.
That's where the 5 Whys model can help.
In a recent episode of The Rest is Data, Scott Sammons explores the 5Y model and how repeatedly asking "why?" can help organisations move beyond the immediate cause of an incident and uncover the root cause.
What is the ‘5 Whys’ model?
While the concept has been around for generations, the modern technique was originally developed by Sakichi Toyoda and was used within the Toyota Motor Corporation during the evolution of its manufacturing methodologies.
The 5 Whys is a straightforward root cause analysis technique. The idea is simple: when something goes wrong, ask why it happened – then ask why again. The process continues until you get beyond the obvious explanation and start uncovering the underlying factors that contributed to the problem.
For example, imagine an employee accidentally sends sensitive information to the wrong recipient.
Why did the data go to the wrong person?
Because the employee selected the wrong email address.
Why did they select the wrong address?
Because several similar contacts appeared in their address book.
Why wasn't the mistake spotted before the email was sent?
Because there was no additional checking process.
Why wasn't there a checking process?
Because the organisation's procedures didn't require one.
Suddenly, what initially looked like ‘straightforward’ human error becomes something much broader: a process failure.
Don't stop at "human error"
One of the key points Scott discusses is how easily organisations can write incidents off as human error. People make mistakes. But mistakes rarely happen in isolation.
Workload, training, communication, technology, processes, resources and organisational culture can all contribute to an incident. As Scott explains, "These things just don't happen. There will be a reason."
The purpose of the 5 Whys isn't to find someone to blame. It's to understand what happened well enough to prevent the same problem happening again.
Using the 5 Whys for data breaches
The approach can be particularly useful when investigating data breaches and information security incidents.
Instead of simply recording that an employee made an error, organisations can use the 5Y model to explore whether the underlying issue was related to:
Inadequate training
Heavy workloads or insufficient resources
Poor communication
Unclear processes
Technology or system limitations
A lack of appropriate checks
Gaps in policies or procedures
This creates a much more useful picture of what actually happened – and where improvements could be made.
Why asking "why?" matters
The 5 Whys model is a reminder that the first explanation isn't always the complete explanation. A data breach report might tell you what happened, but effective root cause analysis should also help you understand why it happened.
By asking better questions, organisations can identify opportunities to improve processes, strengthen training and reduce the likelihood of similar incidents occurring in the future. And perhaps most importantly, the process shifts the conversation away from blame and towards learning.
Want to hear Scott explain the 5Y model?
Scott goes into much more detail about the 5 Whys, root cause analysis and data breaches in the latest episode of The Rest is Data.
Listen to the podcast here

