Improving Investigations & Root Cause Analysis
Success Story: Improving Investigations and Root Cause Analysis
Submitted by Tom Bestwick,
Supervisor, Health and Safety at Enmax Corporation
This success story was written in the past and is being updated to our most recent blog article format and reposted here. The example shows how TapRooT® Root Cause Analysis can help improve incident investigations and root cause analysis. These lessons apply today just as much as they did when this was first written.
As the Supervisor of Health and Safety at Enmax Corporation (a municipal electric utility), I reviewed all incident reports. My observations were that the quality of the reports varied greatly depending on the training, experience, and diligence of the investigator. There was little consistency in format and content from one report to the next. And the investigators tended to identify immediate causes (actions that went wrong) rather than root causes (the causes for the actions that went wrong).
Perhaps these problems were related to the investigation system we were using. It was time-consuming and not very user friendly. It didn’t provide us with a tool to clearly explain what happened and why it happened, nor did it effectively track the status of corrective actions.
To me the challenge was obvious. If we wanted to learn more from the dear-bought experience derived from accidents and incidents, then we needed to improve our investigations and root cause analysis.
Fortunately, I had just been introduced to a system for incident investigation and root cause analysis called te TapRooT® Root Cause Analysis System. The action to take seemed clear. I needed to hold training for the people performing investigations so that they could use the TapRooT® Root Cause Analysis System to improve our investigation performance.
The feedback from the participants in the training was that they left the course feeling confident that they had the skills they needed to use TapRooT® Root Cause Analysis to find the root causes of our incidents. They now had a new vocabulary of root cause analysis, a clear goal for their investigations, and the tools they needed to reach that goal.
However, the real test would be when they applied the techniques. What would I get? The answer was clear and obvious. I immediately noticed an improvement in the quality and thoroughness of investigations and reports. This improvement and consistency meant that all the investigations were well above the minimum that I expected.
The software also helped improve the consistency of the reports and our analysis and the database helps us maintain our incident records. The Corrective Actions Reports are essential in completing the investigation loop by tracking the status of corrective actions and providing documentation that improvements have been implemented.