let’s dive into the Cause and Effect Diagram, also known as the Ishikawa Diagram or Fishbone Diagram. It’s a powerful tool for root cause analysis, quality management, and continuous improvement — and it does appear in the PMBOK® Guide as a model for problem-solving.
🐟 What is a Fishbone Diagram (Cause and Effect Diagram)?
A Fishbone Diagram visually maps out the possible causes of a problem, helping teams identify, analyze, and solve the root causes rather than symptoms.
It’s called a “fishbone” because the diagram looks like a fish skeleton:
- The head is the problem (effect)
- The bones are categories of potential causes
🧠 Use in PMP Context
- Tools & Techniques in:
- Root Cause Analysis
- Manage Quality (process 8.2)
- Control Quality (process 8.3)
- Commonly used in problem-solving sessions, retrospectives, and corrective action planning
📘 Typical Categories in a Fishbone Diagram (6M for manufacturing)
| Category | Description |
|---|---|
| Man (People) | Human factors (skill, fatigue, training) |
| Machine | Tools, technology, software, hardware |
| Method | Procedures, workflows, practices |
| Material | Input quality, raw data, software versions |
| Measurement | Metrics, accuracy, KPIs |
| Mother Nature (Environment) | External influences, weather, culture, working conditions |
In software projects, “Machine” could be infrastructure and “Material” could be data or code.
🧩 How to Build One (Steps)
- Define the Problem (Effect):
→ Write this at the “head” of the fish. - Draw the Spine and Bones:
→ Create main categories as “bones” - Brainstorm Causes:
→ Under each category, list possible causes - Drill Down:
→ Keep asking “why?” to find root causes - Analyze and Prioritize:
→ Highlight the most likely or impactful causes
🎯 PMP Example Scenario
Problem: High defect rate in delivered software
Fishbone categories might reveal:
- Inadequate testing (Method)
- Under-trained staff (Man)
- Unstable test environment (Machine)
- Poor user stories (Material)
- Lack of defined quality metrics (Measurement)
📊 Sample Diagram Layout
lessCopyEdit |→ Cause A1
Category A →|→ Cause A2
|
Problem --------> |
|→ Cause B1
Category B →|→ Cause B2
|
🧠 PMP-Style Practice Question
Your project has experienced repeated delays in deployment. You want to identify the root causes involving people, processes, and tools. Which tool should you use?
A) Scatter diagram
B) Pareto chart
C) Fishbone diagram
D) Control chart
✅ Correct Answer: C
Explanation: The Fishbone Diagram is used to categorize and analyze root causes.
✅ Summary
| Term | Also Known As |
|---|---|
| Fishbone Diagram | Cause-and-Effect Diagram, Ishikawa Diagram |
| Used For | Root Cause Analysis |
| Related PMBOK Areas | Manage Quality, Control Quality |
| PMP Exam Type | Tool selection, scenario-based analysis |

Leave a Reply