Uncovering the Root Cause

Elizabeth Jamischak • Jun 08, 2022

Are you focused on the causes

or the symptoms?

The third phase in the DMAIC project lifecycle is ‘Analyze’. This is where we take the data we have collected during the ‘Measure’ phase and turn it into a cohesive story which will then inform how and where we will make improvements. More specifically, we discover the actual Root Cause of the problem we are trying to solve.

 

Over the past five years we have noticed that ‘data-analytics’ have increasingly become more popular as has ‘data story-telling’. This has been great for marketing the importance of collecting data within organizations however these courses and articles tend to take a broader approach to data (evaluate, clean, summarize) compared to how we analyze data within the DMAIC/Six Sigma framework.

 

Within Six Sigma, the Analyze activities which take place may include:

 

  • Graphical Analysis (ex. Box Plots, scatter, etc)
  • Normality Tests, Distribution ID & Data Transformation
  • Process Control Study (control charts)
  • Capability Study (Yield, TPY, RTY, DPMO, Z)
  • Failure Mode & Effects Analysis (Update RPN)
  • Hypothesis Testing, Y=f(x), (Parametric & Non-Parametric)
  • Test of Central Tendency (Mean, Median)
  • Test of Variance (Dispersion, Standard Deviation)
  • Test of Proportion (%)
  • Test of Frequency (count, occurrence, Chi-Square)
  • Regression Analysis (simple linear, multiple)
  • Analysis of Variance (ANOVA & ANOM)
  • Validate Findings and Conclusions
  • Phase review and approval

 

As previously mentioned, all of the above listed activities are completed with the objective of finding and validating the Root Cause(s) of the problem and ensuring that any improvement in the next phase is focused on causes rather than symptoms.

 

Therefore, the first step is to understand the difference between causality and correlation. Causality is the study of how things influence one other, how causes lead to effects (1). Correlation is a statistical measure or connection between two or more things – especially when one influences the other (2). It is important to keep in mind that “correlation does not imply causation” therefore taking sufficient time in your Root Cause Analysis (RCA) is imperative to avoid jumping to conclusions based on observations of correlation.

 

How do we differentiate between causation and correlation? Some key tools which will aid us in our RCA are:


  1.  5W2H
  2. This is an interrogative technique which asks the question ‘Why’ five times and ‘How’ two times to explore the cause of a problem and to expose weaknesses in a system or process. Each ‘Why’ generally forms the basis of the next ‘Why’ question to encourage the team to dig deeper into the problem. 
  3. Failure Mode and Effects Analysis (FMEA)
  4. This tool is to recognize and evaluate the potential failure of a product or process, the effects of each failure, and to identify actions that could eliminate or reduce the risk of failure as well as document the process.
  5. Fault Tree Analysis (FTA)
  6. This is a visualization tool which provides a convenient, symbolic representation of the combination of events that result in a specific outcome or top event. These events or gates are represented by symbols, similar to those in flow charts and follow a binary logic structure of ‘AND/OR’ branch points. In the FTA, the entire system as well as human interactions are analyzed.
  7. Fishbone Diagram
  8. This is a visualization tool for identifying and categorizing many potential causes of a problem. 
  9. Pareto Charts
  10. Commonly referred to as the ‘80/20 Rule’, it is a chart to help identify the vital few from the trivial many and it illustrates dominant ‘before and after’ results.
  11. Scatter Plot Diagram (aka Dispersion Diagram)
  12. This is a diagram which illustrates a summary of two sets of data/variables. The Y axis represents the dependent variable and the X axis represents the independent variable. This diagram shows the relationship between the two data sets/variables and aids in the interpretation of the correlation coefficient or regression model.

 

One observation we have had after reviewing hundreds of projects over the years is that the Root Cause is often smaller and simpler than originally anticipated at the beginning of the project. This has reinforced our conviction that it is very important to not rush through the Analyze phase, to take the time to use the tools listed above so that you are confident that you have identified the actual root cause. Once this has happened you are ready to take action and move to the next phase of your project which is ‘Improve’.

 

If you have any questions about the tools listed above or would like a refresher on how to use them, please contact us at info@ezsigmagroup.com.

 

 

1. https://www.newscientist.com/definition/causality/ 

2. https://www.jmp.com/en_ca/statistics-knowledge-portal/what-is-correlation.html 


By Elizabeth Jamischak 12 Apr, 2023
Reviewing your toolbox
By Elizabeth Jamischak 21 Dec, 2022
This year we have been posting about the DMAIC (Define, Measure, Analyze, Improve, Control) methodology which is the hallmark of Six Sigma theory and execution. Since this is the final blog for 2022 we decided to include both ‘Improve’ and ‘Control’ within this post. So far we have discussed the importance of defining the problem that we want to fix or area we want to improve and the value of spending time on developing a robust Project Charter, how to protect our project from scope creep by using tools such as a Data Collection Plan and how to uncover the actual Root Cause of the problem we are wanting to resolve or area we are planning to improve. In this post we will list common tools which will aid in collating all the information we have gathered thus far in our project and interpreting that information into potential solutions. However, our primary focus will be on how to actually implement change and then how to monitor / control those changes. To jump right in, some of the most common tools within the Improve phase to identify potential solutions include: Failure Mode and Effects Analysis Stakeholder Analysis Kaizen Event Poka-Yoke Cost-Benefit Analysis Matrix Diagram Once you have a list of possible solutions, selecting the best one AND implementing often brings with it stress and anxiety therefore putting a plan in place is essential for successful change. There are many templates and resources available online for developing an Implementation Plan. We recommend including the following elements: Strategy Process Action Each of these elements can be broken down by applying the 5W2H Method. For example, Strategy Who is managing the implementation of the change(s)? What is our ultimate goal with this project? When does the change(s) need to be completed? Where does this project tie into our mission & vision? Why have we selected ______ solution instead of _______ solution? How will the changes be monitored? How much will it cost to implement the changes? Process Who will be involved in implementing the changes? What is the process and timelines for implementing this change? When do we need to set our milestones to ensure success? Where does the majority of our focus need to be to successfully implement the changes? How will we communicate the change(s) to the staff / department / organization? How much effort is required from the team to implement this change(s)? Action Who is doing _______ [list specific role]? What do we need to accomplish this week / month / quarter to hit our next milestone? When do we need to test the process to verify our changes have been fully adopted? Where will we keep the documentation for implementing the change(s)? How will daily activities for ____ need to be adjusted due to these change(s)? How much time will __________ require to work on implementing the change(s)? By answering these questions, you and your team will have a clear picture of the time, human resources, financial resources and most importantly, the communication which will be required for a successful implementation of the improvements / solution you have selected for your project. The final element in a Six Sigma DMAIC project is ‘Control’. This is the phase that makes all the others worth the time and energy because in the Control phase we focus on maintaining the change(s) / improvement(s) that have been implemented. Oftentimes, the greatest challenge at this point is maintaining the cultural / psychological change that occurred therefore it is important to review your organizations infrastructure (is it technically possible to maintain the change?), the policies and procedures (do these support the change(s)?) and the culture of your organization (is everyone on board with the change(s) / improvement(s) and intentionally incorporating the change(s) / improvement(s) into their daily activities and conversations?) Some tools and activities which typically occur within the Control Phase include… Control Plan Statistical Process Control Control Charts (ex. Xbar, run chart, X-MR chart, p chart, np chart, c chart, u chart) Cost Benefit Analysis Formal Project Closure Celebration of success and team recognition As Six Sigma practitioners it is easy to remain focused on the technical aspects of a project such as collecting and analyzing the data. Therefore, in this series we wanted to highlight some key activities and soft skills which can have a dramatic impact on the success of your project. We trust you will continue to thrive and learn from each experience and that you will allocate additional time and energy to developing your plans at each stage of the DMAIC process and that you will focus on how your project will and is, impacting the culture of your organization. Thank you for joining us on this journey and we look forward to connecting in 2023!
By Elizabeth Jamischak 23 Mar, 2022
“You can’t improve what you don’t measure.” - Tony Robbins
By Elizabeth Jamischak 16 Feb, 2022
Do the necessary due diligence and get teams to the point where everyone is clear on the objective of the project with guardrails in place so that you are properly balancing a rapid agile environment without accidently running off the cliff. 
By Elizabeth Jamischak 22 Dec, 2021
"If you can't describe what you are doing as a process, you don't know what you're doing." -W. Edwards Deming
By Elizabeth Jamischak 17 Nov, 2021
20% of our time produces 80% of our results thus implying that we are typically highly productive for only 20% of our time.
Conflict taking place at work
By Website Editor 13 Oct, 2021
 "There will be times that simply listening to concerns will be the positive outcome you are looking to achieve, in other situations listening will be one of the steps which needs to be taken towards achieving a positive outcome." Post by Mike Ewing
By Elizabeth Jamischak 11 Aug, 2021
Why is there still a stigma around taking holidays? This blog post is an opinion piece written by Elizabeth Jamischak.
By Elizabeth Jamischak 14 Jun, 2021
How To Recognize Life Lessons
By Elizabeth Jamischak 05 May, 2021
Five Things to Consider When Switching to WFH Permanently
More Posts
Share by: