PMP Concepts8 min read

Fishbone Diagram: Root Cause Analysis for the PMP Exam

Master the fishbone (Ishikawa) diagram for PMP root cause analysis. Learn the 6M categories, construction steps, and exam application strategies.

fishbone diagramIshikawa diagramroot cause analysisPMP exam prepquality management

Tracing Problems to Their Source

The fishbone diagram — also known as the Ishikawa diagram or cause-and-effect diagram — is one of the most visually distinctive and frequently tested quality tools on the PMP exam. Its purpose is simple and powerful: systematically identify potential root causes of a problem by organizing contributing factors into categories.

Named after quality pioneer Kaoru Ishikawa, this tool transforms vague complaints like "the deliverable is always late" into structured investigations that reveal actionable root causes.

Anatomy of the Fishbone Diagram

The diagram gets its name from its shape:

  • The head (right side) states the problem or effect being investigated
  • The spine is a horizontal line extending left from the head
  • Major bones branch off the spine at angles, each representing a cause category
  • Minor bones branch off the major bones, representing specific contributing factors within each category

The result resembles a fish skeleton — hence the name.

The 6M Categories

The most common framework for cause categories is the "6Ms," originally developed for manufacturing but widely applied:

  1. Manpower (People) — Skills, training, experience, staffing levels, motivation
  2. Methods (Process) — Procedures, workflows, standards, documentation
  3. Machines (Equipment) — Tools, technology, hardware, software
  4. Materials — Inputs, data, raw materials, requirements documents
  5. Measurements — Metrics, KPIs, testing criteria, acceptance standards
  6. Mother Nature (Environment) — Working conditions, organizational culture, external factors

For non-manufacturing projects, you can adapt these categories. A software project might use: People, Process, Technology, Requirements, Testing, and Environment. The framework is flexible — the important thing is that categories prompt comprehensive thinking about potential causes.

Building a Fishbone Diagram Step by Step

  1. Define the problem clearly — Write a specific problem statement and place it at the head. "Too many defects" is vague; "Module X has a 15% defect rate, three times the project average" is actionable.
  2. Identify major categories — Draw the major bones using the 6Ms or a customized set of categories relevant to the project.
  3. Brainstorm causes within each category — Ask the team: "What factors within this category could contribute to the problem?" Add each factor as a minor bone.
  4. Drill deeper with "Five Whys" — For each potential cause, ask "why?" up to five times to uncover deeper root causes. Add sub-branches as needed.
  5. Analyze and prioritize — Identify the most likely root causes based on data and team expertise. Mark them for further investigation.

Fishbone Diagrams on the PMP Exam

Expect these question types:

Tool Selection

"The team needs to identify root causes of a recurring quality problem. Which tool should they use?" The fishbone diagram is the answer when root cause investigation is the goal.

Process Context

The fishbone diagram is primarily associated with the Manage Quality and Control Quality processes. It can also appear in risk identification when the team analyzes the causes of potential risk events.

Distinction from Other Tools

Know the difference between finding root causes (fishbone) and prioritizing which causes to address (Pareto). A common exam pattern presents both as answer choices — choose based on what the scenario asks the team to do.

Combining with Other Techniques

The fishbone diagram is most powerful when combined with other tools:

  • Use brainstorming to populate the branches
  • Use Five Whys to drill from symptoms to root causes
  • Use Pareto analysis to prioritize which root causes to address first
  • Use scatter diagrams to verify that a suspected cause actually correlates with the effect

Common Exam Pitfalls

  • Do not confuse the fishbone diagram with a decision tree — they look nothing alike and serve different purposes
  • Remember that the fishbone diagram identifies potential causes but does not prove causation — further analysis is needed
  • The diagram is a team exercise — building it alone defeats its purpose of capturing diverse perspectives

Practice identifying when fishbone diagrams are the right tool versus when other quality tools are more appropriate. PMPprep's scenario questions train this situational judgment effectively.

Practice what you just learned

Test your knowledge with flashcards, mini exams, and full-length practice tests on PMPprep.

Start Studying Free