Lesson 2: Cause-and-Effect Diagrams and 5-Why Analysis: Choosing the Right Tool for the Right Problem

It’s Monday morning at a stamping plant, and the line has stopped for the third time this week. The team leader points to a worn-out sensor. Maintenance replaces it. By Wednesday, the line stops again — same symptom, different sensor. Sound familiar? This recurring frustration is not a maintenance problem. It is a root cause problem. The team is treating symptoms because they reached for the nearest tool rather than the right tool. In Kobetsu Kaizen, choosing between a Cause-and-Effect Diagram and a 5-Why Analysis is not a matter of preference — it is a strategic decision that determines whether your problem-solving effort produces lasting results or temporary patches.

Understanding the Two Tools: What They Are and How They Work

Before you can choose the right tool, you need to understand what each one is designed to do. Both the Cause-and-Effect Diagram (also known as the Fishbone or Ishikawa Diagram) and the 5-Why Analysis are root cause identification tools — they belong to Step 4 and Step 5 of the structured KAIZEN Board process: identifying the cause of a problem and analyzing it in depth. However, they approach causality from fundamentally different angles.

The Cause-and-Effect Diagram (Fishbone / Ishikawa)

The Fishbone Diagram is a visual, team-based tool that maps all potential causes of a problem across multiple categories. The “head” of the fish represents the problem (the effect), while the “bones” represent categories of causes — typically Man, Machine, Method, Material, Measurement, and Environment (the 6M framework). Teams brainstorm causes within each category, creating a comprehensive visual picture of the problem landscape.

This tool excels when:

• The problem is complex and multifactorial
• The root cause is unknown and multiple hypotheses need to be explored simultaneously
• Cross-functional input is needed — operators, maintenance, quality, engineering all contribute
• You want to prevent tunnel vision and ensure no cause category is overlooked
• The problem is recurring and previous single-cause fixes have failed

The output of a Fishbone session is not the final answer — it is a structured map of hypotheses. These hypotheses must then be validated with data, often using tools like Pareto Diagrams or tally charts, before countermeasures are defined.

The 5-Why Analysis

The 5-Why Analysis is a linear, depth-first technique that drives from a symptom down to a root cause through a chain of sequential “why” questions. You ask “Why did this happen?” and use the answer as the input for the next “Why.” Repeating this process five times (though sometimes fewer or more iterations are needed) typically reaches the systemic or physical root cause that, when addressed, prevents recurrence.

The KAIZEN Coach Practice Guide emphasizes a critical discipline: investigate and examine the end-level items — particularly the 4th and 5th why — in detail, with physical verification at the gemba. This is not a desk exercise. Each answer must be confirmed by evidence, not assumption.

This tool excels when:

• The problem has a single, clear failure chain (e.g., a machine breakdown, a minor stoppage, a quality defect with a known pattern)
• The root cause path is relatively straightforward and linear
• Speed is important and the team has good process knowledge
• You are analyzing sudden failures — the guide recommends creating a failure cause analysis sheet every time a sudden failure occurs

Choosing the Right Tool for the Right Problem

The Kobetsu Kaizen methodology is explicit: tool selection is a deliberate step, not a default habit. The KB source material identifies this directly — “Choice the right tool” is a named step in the Kobetsu KAIZEN Board process. The tools matrix from the KB confirms that both the Fishbone Diagram and the N5W (5-Why) Analysis are assigned to problem cause identification. But they are not interchangeable.

Use this decision logic in practice:

1. Define the problem clearly first (Step 2 of the KAIZEN Board: Concern / Problem Representation). If you cannot write a single clear problem statement, neither tool will work well.
2. Assess complexity: Is there one obvious failure chain, or are there multiple possible contributing factors across different functions and systems?
3. If complexity is high → use Fishbone first, then validate top causes with data, then apply 5-Why to the confirmed cause chain.
4. If the failure chain is clear → go directly to 5-Why, verify each step at the gemba, and document findings in a cause analysis sheet.
5. Never skip data verification. Both tools generate hypotheses. The 5W1H and Pareto Diagram support cause confirmation before countermeasures are defined.

A common mistake in manufacturing environments is applying 5-Why to a complex, multi-cause problem. The result is a plausible-sounding cause chain that reflects the opinion of the most senior person in the room — not the physical reality of the process. Similarly, creating a Fishbone Diagram for a simple, linear failure wastes team time and dilutes focus.

Practical Case Study: Apex Precision Components

Apex Precision Components, a mid-sized CNC machining facility, was experiencing a recurring dimensional defect on a critical shaft bearing surface. The defect appeared intermittently — roughly 4 times per week — and had resisted two previous corrective actions: a tool change protocol update and a coolant pressure adjustment.

The Kobetsu Kaizen team, led by the production team leader, began Step 4 of the KAIZEN Board. Given the intermittent nature and the failure of previous single-cause fixes, they correctly identified this as a complex, multifactorial problem. They chose the Fishbone Diagram as the entry tool.

During the structured brainstorming session, causes were mapped across all 6M categories. Under Machine, the team noted spindle runout variation and fixture wear. Under Method, they identified inconsistency in operator setup verification. Under Material, incoming bar stock hardness variation was flagged.

Using a tally chart over two weeks, the team collected data and ran a Pareto analysis. The result was clear: 68% of defects correlated with fixture wear. With the dominant cause now confirmed by data, the team applied a 5-Why Analysis specifically to the fixture wear issue:

1. Why is the bearing surface out of tolerance? → Fixture is not holding the part in the correct position.
2. Why is the fixture not holding correctly? → The locating pins are worn beyond specification.
3. Why are the locating pins worn? → They have exceeded their replacement interval without inspection.
4. Why were they not inspected? → There is no scheduled inspection point in the PM checklist.
5. Why is there no inspection point? → The fixture was added after the original PM plan was created and was never formally integrated.

The root cause was a system gap in preventive maintenance planning, not a tooling problem. The countermeasure: update the PM checklist, add fixture inspection to the standard, and create a visual management card at the machine. The defect rate dropped to zero within the following month.

Key Takeaways

• Both tools serve Step 4–5 of the KAIZEN Board (cause identification and analysis), but they are not interchangeable — tool selection must match problem complexity and structure.