You are using an ad blocker...
ToolsHero is a free knowledge platform on management methods, models and more.
Our core business model is advertisement which helps us to create this free platform for you!
Please help us by disabling your ad blocker and add our website to your whitelist.
This article explains the Root Cause Analysis (RCA) in a practical way. After reading you will understand the basics of this powerful problem solving method.
What is a Root Cause Analysis (RCA)?
Root Cause Analysis (RCA) is a method of problem solving that aims at identifying the root causes of problems or incidents.
Root Cause Analysis is based on the principle that problems can best be solved by correcting their root causes as opposed to other methods that focus on addressing the symptoms of problems.
Through corrective actions, the underlying causes are addressed so that recurrence of the problem can be minimized.
It is utopian to think that a single corrective action will completely prevent recurrence of the problem. This is why root cause analysis is often considered to be an iterative process.
Root Cause Analysis is used as a tool for continuous improvement.
If a Root Cause Analysis is used for the first time, it is a reactive way of identifying and solving problems.
This means that an analysis is performed after a problem or incident has occurred. By gaining experience with root cause analysis, its use changes from reactive to proactive, so that problems can be anticipated in time.
Root Cause Analysis is not a strictly defined methodology. There are many different tools, processes and philosophies that have been developed based on Root Cause Analysis.
However, there are five approaches that can be identified in practice:
- Safety-based root cause analysis – Its origin can be mainly be found in accident analyses, safety and healthcare.
- Production-based root cause analysis – Its origin can be mainly be found in the area of quality control and industrial manufacturing.
- Process-based root cause analysis – This is the follow-up from production and business processes.
- Failure-based root cause analysis – Its origin can be found in Engineering and maintenance.
- Systems-based root cause analysis – its origin can be found in the amalgamation of the approaches mentioned above and this is combined with ideas from change management, risk management and systems analysis.
Despite the fact that there seem to be no clear definition of the differences in the objectives among the various approaches, there are some common principles that can be considered to be universal.
It is also possible to define a general process for performing an Root Cause Analysis.
The basic process
The basic process consists of a number of basic steps. These corrective measures will lead to the true cause of the problem.
- Define the problem or the factual description of the incident. Use both qualitative and quantitative information (nature, size, locations and timing) of the results in question.
- Collect data and evidence and classify them along a time line of incidents until the eventual problem or incident is found. Each special deviation in the form of behaviour, condition, action and passivity must be recorded in the time line.
- Always ask ‘why’ to identify the effects and record the causes associated with each step in the sequence toward the defined problem or incident.
- Classify the causes within the causal factors that relate to a crucial moment in the sequence including the underlying causes.
- If there are multiple causes, which is often the case, document these, preferably in order of sequence for a future selection. Identify all other harmful factors.
- Think of corrective actions or improvement measures that will ensure prevention of recurrence with a sufficient degree of certainty. Explore whether corrective actions or improvement measures can be simulated in advance so that the possible effects become noticeable, also with respect to the other underlying causes.
- Think of effective solutions that can prevent recurrence of the causes and to which all involved colleagues can agree. These solutions must comply with the intended goals and objectives and must not cause any new and unforeseen problems.
- Implement the solutions (corrective actions) that have been made by consensus.
- Monitor the effectiveness of the solutions (corrective actions) closely and adjust if necessary.
- Other methods for problem-solving and problem prevention may be useful.
- Identify and address any other causes that may be harmful factors in the process.
Please note: steps three, four and five are the most critical part of the corrective measures because these have proved to be successful in practice.
Root cause analysis tools
Other well-known Root cause analysis techniques and tools are listed below:
This root cause analysis technique is often used in the industrial sector.
It was developed to identify energy flows and focus on possible blocks for those flows in order to determine how and why the obstacles cannot prevent the energy flows from causing damage.
Current Reality Tree
This complex but powerful method developed by Eliahu M. Goldratt is based on representing causal factors in a tree structure.
This method uses rules of logic. The method starts with a short list of the undesirable factors we see around us that will subsequently lead to one or more underlying causes.
This research methodology is often used for problems or accidents and demonstrates how the problem has presented itself from different perspectives.
5 times why
In the Japanese analysis method 5 whys the question ‘why’ is asked five times. The 5 whys technique was originally developed by Sakichi Toyoda, and was used to trace the root cause of the problems within the manufacturing process of Toyota Motors.
This root cause analysis method is also known as the fishbone diagram.
The Ishikawa diagram is a much preferred method of project managers to perform a Root Cause Analysis.
Kepner Tregoe method
The Kepner Tregoe Method is a Root Cause Analysis method based on facts in which the possible causes are systematically excluded in order to find the real cause.
This method also disconnects the problem is from the decision.
RPR Problem Diagnosis
This is an ITIL aligned method designed to determine the root cause of IT problems.
It’s Your Turn
What do you think? What is your Root Cause Analysis experience? Do you recognize the practical explanation or do you have additions? What are in your opinion success factors for conducting a Root Cause Analysis?
Share your experience and knowledge in the comments box below.
- Andersen, B. & Fagerhaug, T. (2006). Root cause analysis: simplified tools and techniques. ASQ Quality Press.
- Barsalou, M. A. (2014). Root Cause Analysis: A Step-By-Step Guide to Using the Right Tool at the Right Time. Productivity Press.
- Dankovic, D. D. (2001). Root Cause Analysis. Technometrics, 43(3), 370-371.
- George, M. L., Maxey, J., Rowlands, D. & Price, M. (2004). The Lean Six Sigma Pocket Toolbook: A Quick Reference Guide to 100 Tools for Improving Quality and Speed. McGraw-Hill Education.
How to cite this article:
Van Vliet, V. (2010). Root Cause Analysis (RCA). Retrieved [insert date] from ToolsHero: https://www.toolshero.com/problem-solving/root-cause-analysis-rca/
Add a link to this page on your website:
<a href=”https://www.toolshero.com/problem-solving/root-cause-analysis-rca/”>ToolsHero.com: Root Cause Analysis (RCA)</a>
Did you find this article interesting?
Your rating is more than welcome or share this article via Social media!