5 Whys

Sakichi Toyoda, founder of Toyota Industries, came up with the "5 Whys" technique. It's a great problem-solving tool, particularly for engineering leadersat growing startups who need to tackle challenges at their root.

What's the Story Behind the "5 Whys"?

Engineering Managers (and engineers)need strategies that can pinpoint and solve the real cause of problems. The "5 Whys" technique, created in the 1930s, is perfect for this. Toyota started using it widely in the 1970s, helping them make decisions based on the reality of a situation rather than guesses.

Why is the "5 Whys" Useful for Startup Engineering Managers?

Startups often come across problems that keep popping up, no matter how many times they're addressed. While quick fixes might seem to solve these issues, they don't tackle what's causing the problem in the first place. The "5 Whys" technique cuts through the surface and gets to the root cause. This is especially important for startups, where resources are tight and need to be used wisely.

When Should You Use the "5 Whys"?

The "5 Whys" is a great tool for solving problems and improving quality, but it works best for simple or moderately complex problems. If you're dealing with a complex or critical issue, broader methods like the Cause and Effect Analysis or Failure Mode and Effects Analysis might be more suitable.

A Step-by-Step Guide to Using the "5 Whys"

  1. Gather your team: Make sure to include people who know the problem and the process well. Choose a facilitator to keep the discussion focused on finding effective solutions.
  2. Define the problem: Work with your team to create a clear, brief problem statement that everyone agrees on. It should capture the main challenge.
  3. Start asking "why?": Ask your first "why?" to understand the reason behind the problem.
  4. Keep asking "why?": After you get each answer, ask "why?" four more times. The questioning should be quick and you should wait until the end to make any conclusions.
  5. Know when to stop: If asking "why?" isn't giving you any more useful answers, it's time to stop. By now, you should have found a solution or change that can address the root cause.
  6. Address the root cause(s): Once you've identified the root cause, discuss and agree on solutions that will stop the problem from happening again.
  7. Monitor the results: Watch how well your solutions are working to eliminate or reduce the problem. You might need to adjust them or even start over. If that's the case, it's a good idea to go through the "5 Whys" process again to make sure you've identified the right root cause.

Another Helpful Tool: Appreciation

Apart from the "5 Whys" technique, another question-based approach called "appreciation" can help startup leaders uncover hidden aspects of a situation. Originally used in the military, "appreciation" helps you understand any fact, problem, or situation in depth.

While the "5 Whys" aims to find the root of a problem, "appreciation" tries to get as much information as possible from a simple fact or statement. Both methods offer valuable insights to help make effective decisions in a startup's complex and changing environment.