Lean Enterprise Institute Logo
  • Contact Us
  • Newsletter Signup
  • Cart (0)
  • Account
  • Search
Lean Enterprise Institute Logo
  • Explore Lean
        • What is Lean?
        • The Lean Transformation Framework
        • A Brief History of Lean
        • Lexicon Terms
        • Topics to explore
          • Operations
          • Lean Product & Process Development
          • Administration & Support
          • Problem-Solving
          • Coaching
          • Executive Leadership
          • Line Management
  • The Lean Post
        • Subscribe to see exclusive content
          • Subscribe
        • Featured posts
          Twi cards on a cork board

          Understanding the True Value of the TWI...

          office sign that says - Kaizen Promotion Office

          Ask Art: Why Do I Need a...

          • See all Posts
  • Events & Training
        • Leadership Coaching and Custom Training
        • What is a Co-Learning Partnership (CLP)?
        • Forms and Templates
        • Featured learning
          • Improvement Kata/Coaching Kata Remotely

            April 10, 2023 | Online Live Course

          • Developing Structured Problem-Solving and Leadership Skills using A3 Thinking: Managing to Learn Remotely

            April 17, 2023 | Online Live Course

          • Hoshin Kanri Remotely: Aligning and Executing on Your Organizational Objectives

            April 21, 2023 | Online Live Course

          • Designing the Future Remotely: A Lean Product Development Immersive Learning Experience

            April 24, 2023 | Online Live Course

          • See all Events
  • Store
        • Shopping Cart
        • Featured books
          Managing to Learn: Using the A3 management process

          Managing to Learn: Using the A3 management process

          Learning to See

          Learning to See

          • See all Books
  • About Us
        • Our people
          • Senior Advisors and Staff
          • Faculty
          • Board of Directors
        • Contact Us
        • Lean Global Network
        • Press Releases
        • In the News
        • Careers
        • About us

The Lean Post / Articles / People Don’t Fail, Processes Do

People Don’t Fail, Processes Do

Problem Solving

People Don’t Fail, Processes Do

By Terry Smith

September 29, 2015

Terry Smith, a lean web developer, shares two examples of real-life companies who used the "5 Whys" to drill down to the root of a thorny problem.

FacebookTweetLinkedInEmailPrintComment

Lean isn’t only a mindset. It gives you and your organization tons of tools and techniques you can apply immediately to improve your business processes. One of my favorites is the 5 Whys. It’s the best demonstration I think of how in fact, people don’t fail, processes do.

In short, 5 Whys is a quick root-cause analysis. Sakichi Toyoda invented this approach in the Toyota Motor Corporation to analyze the defects in processes.

Here’s one way to use it. As soon as an issue happens, you gather a 5 Why-meeting with everyone who participated in the situation and the host asks five times, “Why did it happen?” The host takes down all the answers while the whole team brainstorms an issue. It lets to evaluate the problem from all angles and restore the full chain of events.

Case #1: Freemake

Freemake is a multimedia startup. Their apps stream YouTube videos. But in February 2015, YouTube went down and Freemake displayed an error instead of streaming. So, they went through a 5 Why session:

1. Q: Why did Freemake software show an error?
A: Because YouTube content wasn’t available.

2. Q: Why wasn’t YouTube streaming available?
A: Because YouTube went down and we had nothing to display.

3. Q: Why did Freemake show nothing?
A: Because we were not aware of the YouTube disaster and we showed a default message.

4. Q: Why didn’t we know of YouTube’s outage?
A: Because we don’t have an alarm notification system.

5. Q: Why didn’t we have an alarm notification about streaming?
A: Because we don’t have quality assurance testing for emergency situations.

The team answers are neutral and clear. They don’t show any wishful thinking like “Because we had to think twice.” There is no hatred or blame. Take a look at the fifth answer and you clearly see a process failure. The Freemake quality assurance process failed and caused a poor experience for their customers. One solution? Develop a real-time tracking system and more user-friendly alerts about possible streaming problems. Victoria Kushner, Senior Marketing Manager from Freemake, says: “It was easy to blame our developer’s team, but our company reputation suffered and we realized the importance of a systematic fix”.

Case #2: Buffer

Now let’s look at Buffer, a social media management service company. In 2014 the service had a brief system-wide outage. Here’s how they ran the 5 Whys according to their own words:

1. Q: Why did we go down?
A: Because the database became locked.

2. Q: Why did it become locked?
A: Because there were too many database writes.

3. Q: Why were we doing too many database writes?
A: Because this wasn’t foreseen and it wasn’t tested.

4. Q: Why wasn’t the change tested?
A: Because we don’t have a development process set up for when we should test changes.

5. Q: Why don’t we have a development process for when to do a load test?
A: We’ve never done too much load testing and are hitting new levels of scale.

Next, team members worked out countermeasures. Team members subsequently took responsibility for implementing those countermeasures and new tasks. Notice, each answer was related to a process issue. There were no answers like: “Developer X didn’t do Task Y.” The team didn’t let branching happen and instead kept the focus on figuring out the root cause. And the last answer pointed to a high level issue, i.e. the absence of critical testing of large scale systems, which caused a chain of failures that affected the company’s clients and business.

What’s common across both cases? In both cases, team members worked out effective solutions to fix broken or nonexistent processes. Simple and transparent question-and-answer meetings replaced complicated “investigations.” Applying this technique, of course, has its limits. You have to watch out for all-too-common answers like “We didn’t have enough time/resources” or “We should have thought twice.” And sometimes team members will jump from one level of answers to another. But the practice of going through the 5 Whys will still get you closer to the real root of the problem. It means that you start improving your business faster and avoid witch-hunting.

FacebookTweetLinkedInEmailPrintComment

Written by:

Terry Smith

About Terry Smith

Terry Smith is a freelance web developer. He dreams to improve freelance practices with lean management tools. Terry is into technology and education.

Leave a Comment Cancel reply

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

Related

WLEI Podcast with author Paulo Savaget of The Four Workarounds

Problem Solving

Strategies for Tackling Complex Problems: a Conversation with Paolo Savaget

Podcast by Tom Ehrenfeld

man at wall putting puzzle together

Problem Solving

Learning to Solve Problems By… Wait for It… Solving Problems

Article by Josh Howell

Animation on Starting a Lean Journey

Problem Solving

Getting Started with Lean Thinking and Practice

Video by James (Jim) Womack, PhD

Related books

The Power of Process – A Story of Innovative Lean Process Development

The Power of Process – A Story of Innovative Lean Process Development

by Eric Ethington and Matt Zayko

Welcome Problems, Find Success – Creating Toyota Cultures Around the World

Welcome Problems, Find Success – Creating Toyota Cultures Around the World

by Nate Furuta

Related events

April 10, 2023 | Online Live Course

Improvement Kata/Coaching Kata Remotely

Learn more

April 17, 2023 | Online Live Course

Developing Structured Problem-Solving and Leadership Skills using A3 Thinking: Managing to Learn Remotely

Learn more

Explore topics

Problem Solving graphic icon Problem Solving
Administration & Support graphic icon Administration & Support

Subscribe to get the very best of lean thinking delivered right to your inbox

Subscribe
  • Privacy Policy
  • Sitemap
  • LinkedIn
  • Twitter
  • YouTube
  • Instagram
  • Facebook

©Copyright 2000-2023 Lean Enterprise Institute, Inc. All rights reserved.
Lean Enterprise Institute, the leaper image, and stick figure are registered trademarks of Lean Enterprise Institute, Inc.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Learn More. ACCEPT
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT
Share this ArticleLike this article? Email it to a friend!

Email sent!