Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

June 22, 2017 | Barb Carr

Six Sigma: Better Root Cause Analysis and Corrective Actions

I remember first learning about root cause analysis during Six Sigma training. The main methods we used were 5 Whys and Fishbone diagrams, but somehow we had a hard time arriving at good corrective actions. It took time and testing to get there, and still the fixes were not always robust.

Since then, I have learned a lot more about RCA. Unguided deductive reasoning tools like 5 Whys or Fishbones rely heavily on the knowledge and experience of the investigator. Since nobody can be an expert in every contributing field, this leads to investigator bias. Or, as the old adage goes: “If a hammer is your only tool, all your problems will start looking like nails”.

Other issues with deductive reasoning are investigations identifying only single causes (when in reality there are several), or ignorance of generic root causes that have broader quality impacts. Results will also be inconsistent; if several teams analyze the same issue, results can be wildly divergent. Which one is correct? All of them? None?

This is where the TapRooT® methodology has benefits over other tools. It is an expert system that guides investigators to look at a range of potential causal factors, like human engineering, management systems and procedures. There are no iterations of hypotheses to prove or disprove so investigator bias is not a problem.

The process is repeatable, identifies all specific and generic causes and guides the formulation of strong corrective actions. It is centered on humans, systems and processes, and the decisions they make every day.

The supporting TapRooT® Software is designed to enable investigators to keep efforts focused and organized:

  1. define the problem in a SnapCharT®
  2. identify Causal Factors and Root Causes with the Root Cause Tree®, and
  3. formulate sustainable corrective actions using the Corrective Action Helper® module

The TapRooT® process avoids blame, is easy to learn and quickly improves root cause analysis outcomes.

In Six Sigma parlance, the SnapCharT® is used for problem definition (Define), the Root Cause Tree® and trending for root cause identification (Measure and Analyze), and the corrective action process to define effective fixes (Improve).

#TapRooT_RCA

Categories
Root Cause Analysis
-->
Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *