Root Cause Analysis

Posted on February 5, 2017 by Michael J. Shull

Getting to the root cause of a problem is the first step taken to understand how to fix the problem. After all, if you do not know what is causing the problem, how are you going to fix it?

Ask Why 30 Times

Certified Reliability Engineer Mark Galley takes this methodology one step further. Expanding on the Five Why principle, Galley suggests that asking 20 or 30 why questions can lead to a better understanding of the root problem. In fact, this twist on the Five Why principle can uncover a series of root causes, allowing the team to focus on the most valuable problem.

Process Mapping in Excel

Presenting at the 2016 Mile High Lean Summit, Galley used the Titanic Cause Map analysis from the Think Reliability resource center. Perhaps one of the key takeaways was that Galley did all of his process mapping in Excel. As Galley states, what software does nearly every business manager in the world have on their computer?

Discover more from Improvement Habit

Subscribe to get the latest posts sent to your email.

About Michael J. Shull

Michael Shull inspires people to turn strategy into measurable results by connecting vision to the work that truly matters. He believes that the best ideas come from those closest to the work and focuses on creating conditions where teams are not afraid to try new things, learn quickly, and grow. He also encourages people to challenge the status quo and rethink policies and procedures that were designed for conditions that no longer exist. His perspective on improvement was shaped early in his career in restaurants, broadened in construction, and evolved across government and nonprofit sectors, including healthcare, transportation, and tourism. Today, he leads the Continuous Improvement Program at Denver International Airport and founded The Organizational Improvement Habit in 2009 to share ideas that spark learning, inspire reflection, and drive action.