Repeat Incidents – Why Do You Have Them? [Stop Them Now!]
Why Do You Have Repeat Incidents?
This post will discuss why you have repeat incidents and what you can do to stop having repeat incidents.
The main reasons for repeat incidents are:
- Poor Root Cause Analysis
- Poor Corrective Actions
- Don’t Implement Corrective Actions
- Poor Generic Cause Analysis
- Bad Corporate Memory
We will discuss each of these reasons for repeat incidents below and what you can do to stop repeat incidents.
Repeat Incidents Reason #1: Poor Root Cause Analysis
You already knew this reason for repeat incidents. If you don’t find the incidents real root causes, how can you develop effective corrective actions?
But everyone knows how to find root causes … right?
NO! Our experience has shown that most people don’t know how to perform a root cause analysis.
Why? First, most people asked to perform a root cause analysis have never been trained to find root causes. In fact, they may not even know what a root cause is.
For example, if you asked many untrained people if human error is a root cause, many would say, “Yes.”
But we know better. We wrote the #1 Googled article on why human error IS NOT a root cause. See this link:
Also, some people who are trained in root cause analysis are trained to use poor, ineffective techniques. Techniques that don’t help the investigator go beyond their current knowledge. Techniques that contribute to confirmation bias. Techniques that focus on a single root cause.
What kind of techniques have these kinds of problems?
- Why Trees
That’s just a sample. Read about why one of the techniques, 5-Whys, leaves many users dissatisfied at this link:
Therefore, if you think you have inadequate root cause analysis, you need to do something. We will cover the potential improvements that you may need after we discuss the remaining four problems.
Repeat Incidents Reason #2: Poor Corrective Actions
We already pointed out that poor root cause analysis can lead to poor corrective actions. However, that is NOT the only reason that your corrective actions may NOT lead to improved performance.
We observed that even when people found the root cause analysis of problems, they often suggested ineffective corrective actions that didn’t fix the root cause.
Why would they recommend ineffective corrective actions? Because that’s all they ever saw. Their experience was that every root cause was fixed by one of these solutions…
FIRST, if it was a human error related root cause, you would recommend:
- Training. If they had already been trained then you would recommend MORE training.
- Discipline. This usually started with counsel the operator to be more careful. If that wasn’t enough, you would use the progressive discipline system. And if it was a contractor? You could just fire them.
- Procedure. If you didn’t have a procedure, you could write one. If you had a procedure, you could make it longer.
Those are the top three favorite corrective actions. Those corrective actions are what they always saw previously. Those are the corrective actions that management always approves. So, those are the corrective actions they always use.
And what if it was an equipment failure related root cause? That’s easy! Just replace the part.
You can see these ineffective corrective actions are why incidents repeat. Repeat incidents can’t be solved by the same level of thinking that created the problem to start with! (A paraphrase of Einstien’s quote.)
Again, we will discuss how to solve poor corrective actions later.
Repeat Incidents Reason #3: Don’t Implement Corrective Actions
We already discussed poor corrective actions but this problem is probably even worse.
What happens if your folks perform a good root cause analysis, develop effective corrective actions, but they don’t ever get implemented?
Why would this happen?
- There isn’t any tracking of corrective action completion.
- There is an overwhelming corrective action backlog.
- Adequate resources aren’t authorized when the corrective action is approved.
Whatever the reason, if you don’t implement your corrective actions, performance probably won’t improve.
However, some people THINK they are implementing their corrective actions but they really aren’t.
At one facility, they noticed they were having repeat incidents. They thought they were recommending good corrective actions. What was wrong?
- They weren’t really recommending effective corrective actions.
- They weren’t implementing many of the corrective actions they were recommending.
The first problem was being caused by a combination of poor root cause analysis and poor corrective actions.
The second problem was being caused by a failure to track corrective actions to completion.
- They approved the corrective actions,
- They assigned them to someone to complete, but
- They never checked to see if the corrective actions were actually completed.
- Also, they never checked to see if the corrective actions were effective.
They THOUGHT that the people were working on the corrective actions but the people assigned the corrective actions to implement had other, higher priorities.
Is this happening at your company? If you track your corrective actions you will know the answer.
Repeat Incidents Reason #4: Poor Generic Cause Analysis
Many people don’t even know what a Generic Cause is. A 2015 post (LINK HERE) explains the concept of a Generic Cause. Generic Causes are related to Extent of Cause and Extent of Condition (explained HERE). Here is the definition of a Generic Cause…
The systemic cause that allows a root cause to exist.
Fixing the Generic Cause eliminates
whole classes of specific root causes.
If you find and fix Generic Causes, you will eliminate whole classes of root causes and see much more rapid performance improvement.
Failure to find and fix Generic Causes will leave problems unsolved and you will continue to have similar (but not exactly the same) incidents.
Repeat Incidents Reason #5: Bad Corporate Memory
Corporations often forget what they have learned. They have an incident, learn lessons, but, over time, forget those lessons learned.
In some cases, corrective actions are “undone.”
Why does this happen? Several reasons but often it is because the people that learned the lessons move along. The experience they take with them leaves. When your corrective actions dependent on human actions and human memory and aren’t embedded in concrete or the corporate culture, they can easily be forgotten or not passed on to the next generation.
Thus, things you thought were fixed become unfixed.
Fixing Your Problems with Repeat Incidents
How can you stop repeat incidents? We’ve got some suggestions in the following sections. They include:
- Improving Your Root Cause Analysis
- Improving Your Corrective Actions
- Ensuring Corrective Actions Are Implemented
- Effective Analysis of Generic Causes
- Improving Your Corporate Memory
Read on to learn more…
Fix #1: Improving Your Root Cause Analysis
If you are a TapRooT® User, you already know what to do.
If you aren’t a TapRooT® User, you might want to see the comparison of a 5-Why root cause analysis to a TapRooT® Root Cause Analysis:
You can clearly see what kind of problems are left unsolved when you use an inferior root cause analysis system.
Why does the TapRooT® System help people find the real root causes of incidents? Because it is a guided root cause analysis. Find out more about guided root cause analysis here:
Therefore, if you don’t use TapRooT® Root Cause Analysis, we recommend attending one of our upcoming courses. See the dates and locations of our public courses at this link:
If you would like to have a TapRooT® Course at your site, CONTACT US.
Fix #2: Improving Your Corrective Actions
When we realized the problems people were having developing corrective actions, we developed a new root cause analysis corrective action development tool called the Corrective Action Helper® Guide. We also built this guide into the patented TapRooT® Software.
The Corrective Action Helper® Guide provides four suggestions to help an investigator develop more effective corrective actions.
First, the guide has the investigator CHECK that they are addressing a real root cause.
Second, the guide suggests strategies to address the root cause.
Third, the guide asks if a Generic Cause has been identified and suggests ways to address the Generic Causes.
Fourth, the guide provides references to learn more about the root cause and the suggested corrective action.
For example, here is the section of the Corrective Action Helper® Guide for addressing problems with bad labels (used here by permission):
And here are the suggestions for correcting the Generic Causes of bad labels and references to learn more about good labels (used here by permission):
Perhaps now you can see how the Corrective Action Helper® Guide can help your investigators recommend more effective corrective actions? If you can, you should probably have them attend one of these courses
- 2-Day Root Cause Analysis Training
- 2-Day Equifactor® Equipment Troubleshooting and TapRooT® Root Cause Analysis Training
- 5-Day TapRooT® Advanced Root Cause Analysis Team Leader Training
In addition to the Corrective Action Helper® Guide, we teach investigators about the hierarchy of controls and how it can be used to develop more effective corrective actions based on the risk profile of the incident. This helps them recommend stronger Safeguards that are more effective at preventing future incidents.
That is quite a bit of help making sure your corrective actions are effective.
Fix #3: Ensuring Corrective Actions Are Implemented
How can you make sure that your corrective actions are implemented?
First, when management approves a corrective action, they should make sure that the appropriate resources are assigned/approved to ensure prompt implementation.
Second, your company should have a way to track the corrective actions to completion.
Third, management should have performance measures of how well corrective actions are being implemented. These should include a measure of the corrective action backlog and a measure of the performance of corrective action implementation compared to the originally approved completion dates.
Fix #4: Effective Analysis of Generic Causes
This is an easy problem to fix. TapRooT® Root Cause Analysis has built-in tools for Generic Cause Analysis. Therefore, if you implement TapRooT® RCA, you will be implementing an effective analysis of Generic Causes.
Fix #5: Improving Your Corporate Memory
The best way to improve your corporate memory if to not depend on memory. Instead, corrective actions should be permanent solutions.
For example, if you train people to not make a mistake, the training effectiveness will be lost over time. Eventually, time passes and one or two generations of new operators later, no one will remember the lessons learned.
This is demonstrated in the onion story. (I heard it a long time ago but, once again, found it HERE.)
The chemist-turned-Holocaust-memoir-writer Primo Levi has a story about a time he was working at a chemical plant that made varnish. He was surprised to find that in addition to the chemicals he expected, the varnish formula also called for a raw onion. At first, he could find no reason as to why a raw onion had to be added; there wasn’t anything in onions that was needed in varnish, and even if there were, a single onion would be too little for a large industrial vat.
After doing a little research, Levi found out that his predecessors used to toss an onion into the varnish as a simple and inexpensive way of testing its temperature. If the mixture was hot enough, the onion would fry. With modern equipment, the need for the onion had vanished, but for reasons they no longer knew, it had become part of the recipe.
In this case, the action (throwing in an onion) outlived the reason for the action (to measure the temperature of the varnish).
Your corrective actions should be more permanent by implementing engineering fixes (rather than just implementing training). The Corrective Action Helper® Guide will help with this.
However, you may want to implement audits of important corrective actions that were implemented to stop major accidents to make sure they aren’t accidentally removed.
For example, at a nuclear plant, several steps were added to a procedure as a lesson learned from an incident. Later, the steps were removed to simplify the procedure. The reasons that the steps were added had been forgotten. Only an audit by an old engineer that remembered the steps and wondered why they were gone, lead to the discovery of the missing corrective action (the steps).
Do you have a list of important corrective actions that need to be audited to make sure the lessons aren’t lost?
Are You Ready to STOP Having Repeat Incidents?
If so, here is your three-step plan:
- Implement TapRooT® Root Cause Analysis at your company. We can help you do this by developing a Roadmap for Successful Implementation. Contact us to set up an Executive Briefing to get the process started.
- Get TapRooT® Root Cause Analysis Training scheduled for your investigators.
- Plan to attend the 2021 Global TapRooT® Summit to network/benchmark your root cause analysis and yo hear about the latest root cause analysis improvements and CAPA program best practices.
We’ve seen this plan work many times before … Now let’s see it work at your company.