By EMA Health and Safety Advisor Rebekah Stephens
When something goes wrong at work, “human error” can feel like a straightforward explanation. Someone made the wrong decision, missed a step or failed to follow the procedure.
But describing an incident as human error tells us very little about why it happened. More importantly, it gives a business limited protection against the same thing happening again.
A useful incident review goes further. It examines the conditions surrounding the person’s actions, including the systems they were working within, the information available to them and the pressures they faced at the time.
That shift in focus can turn an incident from an isolated failure into an opportunity to improve how work is designed and managed.
The problem with stopping at human error
People make mistakes. But simply identifying that a mistake occurred does not explain what contributed to it.
Labelling an incident as human error can oversimplify what happened and bring the investigation to an early close. The organisation may respond by reminding employees to take more care, repeating training or updating a procedure. These actions may be appropriate, but they will have limited effect if the conditions that influenced the original decision remain unchanged.
Most people do not arrive at work intending to act unsafely. They make decisions based on what they see, understand and believe is expected of them at the time.
Those decisions can be shaped by production pressures, fatigue, interruptions, equipment design, unclear instructions, competing priorities or long-established ways of working. A procedure might look clear on paper but be difficult to follow in the actual work environment. A safety control might be available but impractical to use under certain operating conditions.
If an investigation concentrates only on the final action taken by an individual, these contributing factors can remain hidden.
Ask what made the decision make sense
Rather than beginning with “Who made the mistake?”, consider asking:
What made that action seem reasonable in that moment?
This question does not remove personal responsibility or excuse unsafe behaviour. It gives the organisation a better chance of understanding why the decision occurred.
It may reveal a gap between the documented procedure and how the job is normally completed. Employees might be expected to meet a deadline that is difficult to achieve while following every required step. Instructions may be open to interpretation, or an employee may have learned an informal workaround from someone more experienced.
These details matter because they show how work happens in practice.
They can also help distinguish between an isolated error and a wider issue that could affect other people performing the same task.
Look at the conditions surrounding the incident
A good review considers the incident within the wider system of work. Three areas provide a useful starting point.
Work conditions: Consider what was happening around the person at the time. Was there pressure to complete the job quickly? Were there interruptions, distractions, noise or poor visibility? Had the person been working for an extended period? Did weather, temperature or the physical layout of the workplace affect the task?
These factors may not appear significant when considered separately. Together, they can change how information is interpreted and how decisions are made.
Systems and processes: Examine whether the organisation’s systems supported the safe completion of the work. Were procedures clear, current and practical? Did they reflect the task as it was actually performed? Were suitable controls available, and could employees use them without creating another difficulty?
It is also worth looking at whether equipment, tools or workspaces made an error more likely. Where possible, critical controls should not depend entirely on someone remembering the right step at the right time.
People and communication: Review the information, training and support available. Did the employee understand what was expected? Was there appropriate supervision? Were responsibilities clear? Had employees previously raised concerns or identified problems with the task?
An incident may expose information that was already known somewhere within the business but had not reached the person or team able to act on it.
Make the response match the cause
Once the contributing factors are understood, the response should address them directly.
This might involve redesigning or strengthening a control, changing the sequence of a task, improving supervision or making a procedure easier to use. It could also mean reviewing workloads, training, equipment, staffing levels or the way competing priorities are communicated.
The most effective action will depend on what the investigation finds. Repeating training may help if the issue was a genuine knowledge gap. It will not resolve a poorly designed process, conflicting expectations or a control that cannot be used reliably.
Businesses should also consider how the learning can be shared. If similar work takes place across other teams, sites or shifts, the same conditions may exist elsewhere.
The test is simple: what has changed in the system as a result of what was learned?
If the only change is that an individual has been told to be more careful, the underlying risk may still be present.
Create the conditions for honest reporting
How an organisation responds to an incident also influences what employees report in the future.
If people expect blame or punishment, they may be less willing to raise near misses, mistakes or concerns. That limits the information available to the business and removes opportunities to act before someone is harmed.
A learning-focused response does not mean ignoring accountability. Deliberate misconduct still needs to be addressed appropriately. But most incident reviews will produce better information when employees can speak openly about what happened, including the pressures, misunderstandings and practical difficulties involved.
Leaders set the tone by showing that the purpose of the review is to understand and improve, not to identify the quickest person to blame.
From investigation to improvement
Every incident and near miss provides a view into how work is really being done. The value comes from looking beyond the final action and understanding the conditions that shaped it.
That requires careful questions, honest conversations and a willingness to examine whether systems operate as intended.
After your last incident review, what changed in the way work was designed, managed or supported?
If the answer is “nothing”, the investigation may have explained who was involved without addressing why the incident happened.