Process Domain7 min read

Cause and Effect Diagrams for PMP Quality Questions

Master cause-and-effect (fishbone/Ishikawa) diagrams for the PMP exam. Learn how to build them, the 6 Ms framework, and when to use this quality tool.

cause and effect diagramIshikawa diagramfishbone diagramPMP examquality managementroot cause analysis

The Fishbone Diagram: Root Cause Analysis for PMP

The cause-and-effect diagram — also called an Ishikawa diagram or fishbone diagram — is one of the seven basic quality tools and a favorite topic of PMP exam writers. It is a visual tool for identifying potential causes of a problem or effect, organizing them into categories to facilitate root cause analysis. When a PMP question describes a team investigating why defects are occurring, the cause-and-effect diagram is often the correct answer.

Structure of the Diagram

The diagram resembles a fish skeleton:

  • Head (right side): The effect or problem being investigated — for example, "High defect rate in Module B."
  • Spine: A horizontal line extending from the head to the left.
  • Major bones: Diagonal lines branching off the spine, each representing a major cause category.
  • Minor bones: Smaller lines branching off the major bones, representing specific causes within each category.

The 6 Ms Framework

The most common categorization for manufacturing and general projects uses six categories, known as the 6 Ms:

  1. Manpower (People): Human factors — skill levels, training, fatigue, communication, staffing levels.
  2. Method (Process): How work is performed — procedures, workflows, standards, best practices.
  3. Machine (Equipment): Tools, technology, hardware, software — calibration, maintenance, capabilities.
  4. Material: Raw materials, components, data inputs — quality, availability, specifications.
  5. Measurement: How quality is assessed — metrics, inspection methods, measurement tools, data accuracy.
  6. Mother Nature (Environment): External conditions — weather, market conditions, regulatory changes, working environment.

For service industries or software projects, categories may be adapted: Policies, Procedures, People, Plant/Technology are common alternatives.

Building a Cause-and-Effect Diagram

  1. Define the effect: Write the problem or quality issue at the head of the fish. Be specific — "late deliveries" is better than "quality problems."
  2. Draw the spine and major bones: Add the major cause categories as branches.
  3. Brainstorm causes: For each category, the team identifies potential causes and writes them on minor bones. Use "5 Whys" iteratively — for each cause, ask "Why does this happen?" to dig deeper.
  4. Analyze the diagram: Look for causes that appear in multiple categories, causes that the team considers most likely, and causes that can be verified with data.
  5. Prioritize and investigate: Select the most probable root causes for data collection and testing.

When the PMP Exam Uses Cause-and-Effect Diagrams

Look for these scenario patterns:

  • "The team needs to identify possible causes of a quality problem." → Cause-and-effect diagram.
  • "The project manager wants to facilitate a brainstorming session about why defects are occurring." → Cause-and-effect diagram.
  • "A root cause analysis is needed." → Cause-and-effect diagram (or the 5 Whys technique).

Cause-and-Effect vs Other Quality Tools

Do not confuse the fishbone diagram with these related tools:

  • Pareto chart: Prioritizes problems by frequency. Use after identifying causes to determine which cause to address first.
  • Flowchart: Maps process steps. Use to understand how a process works, not to identify causes of problems.
  • Histogram: Shows data distribution. Use to understand the pattern of a measurement, not to trace causes.

The fishbone diagram is specifically for diagnostic purposes — finding out why something is happening.

Exam Tips

  • The cause-and-effect diagram is a tool of the Manage Quality and Control Quality processes.
  • It is used for root cause analysis, which is a technique in both quality management and risk identification.
  • The diagram organizes potential causes — it does not prove causation. Data collection and analysis are needed to confirm which cause is actually responsible.

Practice identifying when to use cause-and-effect diagrams versus other quality tools. Explore our quality management topics for targeted practice, or start your free trial today.

Practice what you just learned

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

Start Studying Free