Root-Cause Analysis Tools, and How to Use Them - Kepner Tregoe Consulting & Training

Break/fix is a way of manufacturing life, but how you respond to it is the key difference between merely muddling through and operating a well-oiled process. Whatever process you call it, Corrective Action or CAP or CAPA, the time it takes to find the root cause of any problem is growing. As a result, your production is slowing and your quality is suspect. The quality of your products relies on how quickly you get to the root cause of your production problems. There are many tools available today that can lead us to root cause and then the corrective action, but which one is right for you? In this video Michael Curran-Hays offers a basic understanding of each tool as well as a model for when to them and on what issue.
Areas that are discussed:
• Common Root Cause Analysis tools in an 8D framework
• Human performance module designed to diagnose “Operator Errors”
• “Think Beyond the Fix”… Where else could this happen?
• Issue escalation model for using the right tool, at the right time, with the right people

[@ChanduTadanki]

05:12 RCA Tools list
27:08 KT Is/Is Not example
30:41 RCA Methods - Simple to Complex (5 Whys, Fishbone/Ishikawa, KT PA, 8D)
31:41 KT 8D Model
31:48 KT 8D Template example
47:53 Simple Flowchart for finding cause (5 Whys, KT Is/Is Not, Fishbone/Ishikawa)
49:17 Complex Flowchart for finding cause
50:50 Example: Problem Escalation: Action Tool

[@josevaldesv]

I was quite surprised to see pretty much a summary of General Motors's Drill Deep & Wide and Red X.

[@claude-edouardloiseau3404]

Awesome!

[@eduardomuniz5314]

How was the test for understanding of this fragmented presentation of KT process? e.g IS/IS NOT?......

[@joeking6972]

Oh so this essentially a form of first principles thinking

[@rachaelwilliams4576]

Not for beginners in this area.

[@MyMorara]

what was the main idea behind this drastic increase?

[@trajan9822]

Not for beginners. Most of the graphs are really blurred. Topic are too brief.

[@joseluizth]

Incomplete explanation