HKSM

A cause-and-effect diagram is a visual technique for organizing possible causes of a specific effect so teams can explore and test root causes. Also called a fishbone or Ishikawa diagram, it supports structured problem solving and quality improvement.

Key Points

• Visual tool that maps an effect (problem or outcome) to multiple potential causes organized in categories.
• Common in quality management and continuous improvement to support root cause analysis.
• Often used with brainstorming, 5 Whys, Pareto charts, check sheets, and data analysis.
• Suggests hypotheses about causes but does not prove causality without supporting evidence.
• Works best with a cross-functional team and a well-defined, measurable problem statement.
• Enables prioritization and planning of experiments or actions to validate likely root causes.

What the Diagram Shows

The diagram displays the effect (the outcome or problem) at the head of a horizontal spine, with major cause categories branching off like bones. Each major branch breaks down into sub-causes, showing a hierarchy of contributing factors.

• Typical categories include Methods, People, Equipment/Technology, Materials, Environment, and Measurement.
• Branches capture both process-related and context-related causes.
• Sub-branches show deeper levels of contributing factors uncovered by asking why repeatedly.

How to Construct

• Define the effect clearly, including scope and measurable criteria (what, where, when, how much).
• Draw a spine with the effect at the head (right side) and space for branches to the left.
• Select cause categories appropriate to the context; customize beyond standard labels if needed.
• Facilitate brainstorming to populate each category with possible causes, then add sub-causes by asking why.
• Use data and observations to annotate or mark likely causes (e.g., frequency, impact, evidence available).
• Consolidate duplicates, clarify vague wording, and ensure causes are actionable and specific.
• Agree on next steps to collect data, run tests, or implement trials to confirm or rule out causes.

Inputs Needed

• Clear problem statement and target or threshold that defines the effect.
• Process maps, SOPs, or workflow descriptions relevant to the effect.
• Observed data such as defect logs, cycle times, customer feedback, or check sheets.
• Subject matter expertise from people who do the work and stakeholders impacted.
• Historical insights such as lessons learned, audit findings, or prior corrective actions.
• Brainstorming outputs and preliminary analysis (e.g., Pareto of defect types).

Outputs Produced

• A completed fishbone diagram showing categorized potential causes and sub-causes.
• A vetted list of candidate root causes to validate with data or experiments.
• Prioritized causes based on impact, frequency, risk, or feasibility of action.
• Hypotheses to test, with proposed data collection or verification methods.
• Action items, owners, and timelines for investigation and improvement.

Interpretation Tips

• Look for clusters of causes in certain branches; density can signal systemic issues.
• Check for cross-branch links or common sub-causes that affect multiple categories.
• Validate suspected causes with data; correlation and controlled tests prevent false conclusions.
• Favor specific, observable causes over vague terms; rewrite ambiguous items for clarity.
• Combine with 5 Whys to drill down until causes are actionable and within influence.
• Use Pareto analysis or an impact-effort matrix to focus investigation on high-value causes.

Example

Effect: High rework rate on deliverables.

• Methods: Inconsistent review process; unclear acceptance criteria.
• People: Insufficient training for new team members; competing priorities reduce focus.
• Equipment/Technology: Tool configuration errors; slow environments causing timeouts.
• Materials: Outdated templates; incorrect reference data used by teams.
• Environment: Frequent interruptions; tight deadlines driving shortcuts.
• Measurement: Limited in-process checks; inconsistent defect tagging.

From this, the team selects top candidates to verify, such as clarifying acceptance criteria and standardizing reviews.

Pitfalls

• Jumping to solutions without validating suspected causes with evidence.
• Listing symptoms or outcomes instead of true causes that can be acted upon.
• Blaming individuals rather than examining process and system factors.
• Overloading the diagram with too many categories or vague items, reducing clarity.
• Excluding key stakeholders or frontline staff, leading to blind spots.
• Not updating the diagram after tests, causing outdated or incorrect conclusions to persist.

PMP Example Question

During Control Quality, a team wants to organize potential reasons for a recurring defect into categories and sub-causes branching from a defined problem. Which tool should they use?

1. Scatter diagram
2. Cause-and-effect diagram
3. Control chart
4. Histogram

Correct Answer: B — Cause-and-effect diagram

Explanation: A cause-and-effect (fishbone/Ishikawa) diagram categorizes potential causes of a defined effect for root cause analysis. The other tools visualize relationships, stability, or distributions, not hierarchical causes.