A Root Cause Analysis is a problem-solving method used to identify the root causes of faults or problems. A factor is considered a root cause if removal thereof from the problem-fault-sequence prevents the final undesirable event from recurring. Short-term actions are not profitable for the organization; thus, RCA help to eliminate the issues permanently.
Root cause analysis is a collection of tools and processes we can use to determine the most important causes for an issue we are trying to resolve. This is an important function as one of the top 5 reasons for project failures is poor root causation / no root cause identified. If we can identify the root cause of an issue, we have a good chance of solving it.
“Take away the cause, and the effect ceases.” – Miguel De Cervantes in Don Quixote.
Why Root Cause Analysis?
In a process, unpredicted problems may occur at any time, which leads to machine downtime, rework, rejections, or customer dissatisfaction. Fixing a process quickly becomes a convenient solution. However, it does not prevent the problem’s re-emergence. Hence, teams to focus on finding the root cause using appropriate tools to develop a more effective strategy to overcome it.
When should conduct Root Cause Analysis?
The RCA process involves data collection, analysis, root cause identification, initiating corrective actions, and implementation. You should perform a root cause analysis to determine what happened, why the issue happened, and what action to implement to reduce or eliminate it. RCA is used to identify issues in the process, analyze customer complaints, reasons for high rework, machine downtime, etc. Moreover, It helps to identify target opportunities for systemwide improvement.
Basics of Root Cause Analysis
Before diving in with the aforementioned tools, it’s good to start with Causal Theory. In other words, Why does a certain problem exists?
To do this, we start with a basic equation; Y = f(x) ;
- Y is the output of a process.
- Xs are the process elements that influence Y.
Another way to state this is Y is the crime; Xs are the suspects that explain the crime of Y.
Data door & Process door
Some of my instructors refer to the data door and the process door. Both are good for root causation, but certain tools are better in certain circumstances.
- Effectiveness project – use data door.
- Efficiency project – use process door.
Root Cause Analysis: Open-Narrow-Close
To validate the root causes identified in the Open-Narrow-Close efforts, the team should employ three tools/techniques:
- Basic data collection: In the DMAIC methodology, a data collection plan is created during the Measure phase. It is a useful tool to focus your data collection efforts on.
- Scatter Analysis/Regression: Linear regression is a statistical technique to estimate the mathematical relationship between dependent and independent variables. In other words, predict the change in the dependent variable according to the change in the independent variable.
- Design of Experiments: The objective of Design of Experiments (DOE) is to Establish optimal process performance by finding the right settings for key process input variables. Furthermore, the Design of Experiments is a way to intelligently form frameworks to decide which course of action you might take. This is helpful when you are trying to sort out what factors impact a process.
You want to gather as many ideas as possible in the open phase. To do that, first, you use the Brainstorming method. It is a method for generating a large number of creative ideas in a short period of time. You can boil or funnel these ideas to a smaller list of priority items later in the project.
The team then pairs the ideas with a Fishbone or Cause and Effect Diagram. It is one of the seven basic quality tools identifying many possible causes for an effect or problem. Effective brainstorming can take advantage of a Fishbone diagram to achieve stellar results. It sorts ideas into useful categories.
Multivoting is a way for a group to narrow a list of choices down to a manageable few. While multivoting is NOT a decision-making tool, it is a great way to achieve consensus on an option that the group most favors.
Once the agreed actions are implemented, the team closes the process by validating using a hypothesis and convicting them or setting them free. During the IMPROVE phase, the team will work on the validated Xs.
Types of Root Cause Analysis Tools
You perform a Root Cause Analysis (RCA) using various statistical tools. However, no fixed rule exists for applying certain tools. Hence, subject matter experts like the Quality team or the six sigma champion determine the appropriate tool based on the scenario.
- Brainstorming: Brainstorming is a method for generating a large number of creative ideas in a short period of time. Brainstorming is full of energy, moves rapidly, and is synergistic, creating a large list of ideas that may eventually be converted into a smaller list of priority items later in the project.
- Fishbone Diagram: A Cause and Effect Diagram (aka Ishikawa, Fishbone) is a pictorial diagram showing possible causes (process inputs) for a given effect (process outputs). In other words, it is a visual representation to determine the cause(s) of a specific problem.
- 5 Whys: The 5 Whys is a basic root cause analysis technique; to solve a problem, we need to identify the root cause and then eliminate it. The 5 Whys method is simply asking the question “Why” enough times–until all the problem symptoms have been narrowed down to the root cause (not just till 5 whys).
- Pareto and data analysis: The Pareto Chart is a graphical tool to map and grade business process problems from the most recurrent to the least frequent. In other words, this helps to identify the most frequently occurring problems or separate the vital few from the trivial many.
- FMEA: Failure Mode Effects Analysis (FMEA) is a tool that helps us anticipate what might go wrong with a product or process. We can also use it to identify the possible causes and probabilities of failures.
Steps to perform a Root Cause Analysis
- Form a small team (consisting of members from the process area, subject matter experts, and the Quality team) to perform a root cause analysis.
- Define the problem and describe it in clear and comprehensive language.
- Collect the data and create a timeline to visualize the sequence of events that occurred.
- Differentiate causal factors or symptoms and the root cause of the problem.
- Use appropriate tools such as 5Why or Fishbone to systematically identify the root cause of the problem.
- Prioritize the root cause that needs to be addressed first, which greatly impacts the process.
- Implement appropriate corrective action(s) to prevent the recurrence of the same issue in the future.
- Monitor the progress and communicate with relevant stakeholders
Root Cause Example in DMAIC Project
Example 1: A female operator from XYZ organization fell in the assembly area and was injured during the second shift. Perform the root cause analysis to avoid the recurrence of the issue.
Example 2: XYZ organization reported most of the service complaints are due to inaccurate seal diameter (out of specification).
- Root cause analysis helps to define the problem and identify the root cause(s) of the problem.
- Help to identify improvement opportunities in the organization.
- Provides confidence to the customers that organizations are valuing the feedback and analyzing systematically to identify root causes
- Root cause analysis helps to implement mistake-proofing solutions
- It helps to implement preventive actions across the organization.
Root Cause Analysis Videos
Good video, awful sound. I muted it and just clicked through at a good pace. It gets the point across.
Other Helpful Notes
Also, see Linear Regression for Y = f(x)