Skip to main content

Using 5 Whys and Fishbone (Ishikawa) Diagram - Root Cause Analysis (RCA) in Lean Six Sigma

 

Root Cause Analysis (RCA) in Lean Six Sigma

Using 5 Whys and Fishbone (Ishikawa) Diagram

Image

Image

Image

Image


What is Root Cause Analysis (RCA)?

Root Cause Analysis is a structured problem-solving approach used in Lean Six Sigma to identify the real cause of a problem—not just its symptoms.

Goal: Fix the problem once and permanently, not repeatedly.

RCA is mainly used in the Analyze phase of DMAIC.


Why RCA is Critical in Lean Six Sigma

  • Prevents recurring defects

  • Avoids “quick fixes”

  • Reduces waste and rework

  • Enables sustainable improvement

  • Supports data-driven decisions


Two Most Powerful RCA Tools

Lean Six Sigma commonly uses:

  1. 5 Whys

  2. Fishbone (Cause-and-Effect) Diagram

They are often used together.


1️⃣ 5 Whys Technique

What is 5 Whys?

The 5 Whys is a simple questioning technique where you repeatedly ask “Why?” until the root cause is revealed.

📌 Usually 5 times—but it can be 3 or 7, depending on the problem.


5 Whys – Example

Problem Statement

Customer received wrong invoice

Why?Answer
1️⃣ Why was the invoice wrong?Incorrect data was entered
2️⃣ Why was incorrect data entered?Operator selected wrong customer
3️⃣ Why did operator select wrong customer?Customer names look similar
4️⃣ Why do names look similar?System does not show unique ID clearly
5️⃣ Why doesn’t system show unique ID?Design requirement was missed

✅ Root Cause

👉 System design does not enforce unique customer identification


When to Use 5 Whys

✔ Simple problems
✔ One main cause suspected
✔ Small teams
✔ Fast analysis

Limitations

❌ Can be subjective
❌ Depends on facilitator skill
❌ Weak for complex problems


2️⃣ Fishbone Diagram (Ishikawa)

What is a Fishbone Diagram?

The Fishbone Diagram visually maps all possible causes of a problem under logical categories.

It answers:

What are all the possible reasons this problem could occur?


Image

Image

Image


Common Fishbone Categories (6M)

Manufacturing (6M)

  • Man – People, skills, training

  • Machine – Equipment, tools

  • Method – Process, SOP

  • Material – Raw materials

  • Measurement – Data, metrics

  • Mother Nature – Environment

Service / IT (often adapted)

  • People

  • Process

  • System

  • Policy

  • Data

  • Environment


Fishbone – Example

Problem

High order delivery delay

Possible causes identified:

  • People: New staff, inadequate training

  • Process: No standard delivery workflow

  • System: ERP downtime

  • Measurement: No delivery SLA tracking

  • Environment: Traffic, weather

👉 After brainstorming, data analysis confirms:

  • 70% delays due to missing standard process

✅ Root Cause

👉 Lack of standardized delivery process


How 5 Whys and Fishbone Work Together (Best Practice)

StepTool
Brainstorm all possible causesFishbone
Narrow down key causesData analysis
Drill into true cause5 Whys
Validate causeEvidence
Fix permanentlyImprove phase

📌 Fishbone = Wide view
📌 5 Whys = Deep dive


Common Mistakes to Avoid ❌

  • Jumping to solutions too early

  • Stopping at symptoms

  • Blaming people instead of process

  • Not validating causes with data

  • Treating assumptions as facts


Lean Six Sigma Golden Rule ⭐

If you remove the root cause, the problem will not return.
If the problem returns, the root cause was not removed.


Short Summary

Root Cause Analysis in Lean Six Sigma is used in the Analyze phase to identify the true cause of defects.
Fishbone diagrams identify all possible causes, while 5 Whys drills down to the actual root cause for permanent improvement.




Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .