Some thoughts on “5 Whys”
The “5” is a reminder to avoid shallow attribution When faced with a problem, there’s a general tendency for people to only consider the immediate contributing factors. The “5” in “5 Whys” is a reminder to go beyond shallow attribution and keep exploring underlying causes.
June 2: The Five Whys
Source: Mind Tools Published: October 2005 The Five Whys The 5 Whys technique is an effective tool for root-cause analysis in the Lean philosophy. It is utilized by individuals and teams to protect their processes from recurring mistakes. The methodology, developed by Sakichi Toyoda in 1930, was originally used in the Toyota Production System. Asking why five times helped the team at Toyota to identify the nature of the problem and find a clear solution.
Why is “why” important for Product Managers?
I probably sound like a broken record now but I strongly believe that it is very hard for Product Managers to understand the why behind everything they are building. There are some well-known terms like “5 Why questions”, “Deep Dive”, and “The Why Stack” that are tools for Product Managers…
The 5 Why’s Approach — Building a Culture of Learning
Is an initiative failing? We knew it! Was a mistake made? By who? If a mistake happens, we typically look for someone to blame. In turn, many of us will avoid risks or will play it safe to avoid being pointed out. Progress suffers from fear of taking action. Making…
Is it possible to always identify the actual root cause behind a security incident?
Identifying the actual root cause of a security incident is not always as straightforward as you think it is. If you have a security incident that is caused by malware, then often the user gets blamed because he/she clicked on a phishing link and/or visited a doggy website. But actually, a technical security control failed. Was the antimalware solution active, running and were the latest signatures and product updates applied? If not, then the question is why not? If they were applied, then more investigation is required to discover why the antimalware security control failed. This technique is also known as the 5-Why technique. Every time you identify a cause, you ask yourself the question ‘Is this the real root cause behind the security root?’. Important here is to answer the why question. But is this the only technique you can apply to identify a root cause?
How to save months of development?
You must have gotten excited just by reading this title? Well, it indeed excited me years ago when my manager introduced me to it and helped me take control of productions bugs as a Product Manager when and where it happened. Sometimes things don’t go according to plan. Tools break…