What is an 8D report?

8D (Eight Disciplines) is a problem-solving methodology used in automotive, medical, and manufacturing industries. It guides teams through D0 to D8 steps from problem identification to root cause analysis and corrective actions, preventing recurrence. 8D.wiki provides a free AI-powered 8D report generator tool.

How does 5-Why root cause analysis work?

5-Why analysis is the core tool of D4 in 8D methodology. Start from the visible symptom and ask 'Why?' repeatedly, drilling down until you find the systemic root cause. Five iterations is typical, but the goal is finding the system-level cause, not a specific number. 8D.wiki's AI engine automates this process.

Is there a free 8D report generator?

Yes, 8D.wiki offers a completely free AI-powered 8D report generator online. Generate professional IATF 16949 compliant 8D reports with 5-Why analysis, PDF and Word export — no registration required.

IATF 16949 is the international quality management standard for the automotive industry. Built on ISO 9001, it adds stringent automotive-specific requirements. 8D reports are the recommended corrective action tool under IATF 16949 Clause 10.2.

What is the difference between 8D and A3 reports?

8D reports focus on cross-functional team collaboration with a strict D0-D8 process, ideal for customer complaints and major quality events. A3 reports are simpler and better suited for internal improvements. 8D is required by IATF 16949, while A3 is common in Toyota's lean management system.

What is the 8D methodology?

The 8D Methodology is a systematic, team-oriented approach for identifying, correcting, and eliminating recurring problems. Made popular by Ford Motor Company, it follows 8 disciplines: D0 Preparation, D1 Team, D2 Problem Description, D3 Containment, D4 Root Cause, D5 Verification, D6 Implementation, D7 Prevention, D8 Recognition.

What is Poka-Yoke in 8D?

Poka-Yoke (mistake-proofing) is a technique used in D6 of the 8D process. It makes defects physically impossible through mechanical fixtures, sensors, or process controls — rather than relying on operator vigilance. It is the gold standard for permanent corrective actions.

What is FMEA and how does it relate to 8D?

FMEA (Failure Mode and Effects Analysis) is a risk assessment tool. In 8D, D7 requires updating the FMEA with new Occurrence and Detection ratings based on D4 findings. This transforms the FMEA from a static document into a living knowledge base. Both are core IATF 16949 requirements.

Fishbone Diagram (Ishikawa) — Root Cause Analysis Tutorial

What Is a Fishbone Diagram?

A fishbone diagram (Ishikawa diagram or cause-and-effect diagram) is a visual root cause analysis tool that maps potential causes of a problem into categories. Named after its shape — the "head" represents the problem, and the "bones" branch out into cause categories. It was developed by Kaoru Ishikawa in the 1960s at Kawasaki shipyards and became a foundational tool of the Toyota Production System.

How Fishbone Fits Into 8D (D4)

In 8D D4 (Root Cause Analysis), the fishbone diagram is typically used FIRST — before 5-Why analysis. The team brainstorms ALL possible causes across categories, then uses 5-Why to drill into the most likely ones.

The 6M Categories

The classic 6M framework for manufacturing:

1. **Man (People)** — Training, fatigue, communication, experience

2. **Machine (Equipment)** — Wear, calibration, maintenance, tooling

3. **Method (Process)** — SOP clarity, work instructions, sequence

4. **Material (Raw Materials)** — Supplier variation, storage, handling

5. **Measurement (Inspection)** — Gauge accuracy, measurement method, sampling

6. **Mother Nature (Environment)** — Temperature, humidity, dust, vibration

Some industries add: **Management** (policies, resources) and **Maintenance** (preventive schedules).

How to Create a Fishbone Diagram

**Step 1:** Write the problem statement at the "head" (right side).

**Step 2:** Draw a horizontal spine line from left to the head.

**Step 3:** Draw 6 main branches (one per M category) angled off the spine.

**Step 4:** Brainstorm specific causes for each category as sub-branches.

**Step 5:** Ask "Why?" for each cause to drill deeper (creates tertiary branches).

**Step 6:** Circle the 3-5 most likely causes based on data and team consensus.

**Step 7:** Use 5-Why on the circled causes to find the true root cause.

Real Example: High Scrap Rate on CNC Line

**Problem (Head):** 12% scrap rate on CNC Line 3 — bearing housing OD oversize

**Man:** Operator A on night shift has 3x scrap rate of Operator B → Training gap?

**Machine:** Spindle bearing vibration 0.08mm at 8000 RPM → Worn bearings?

**Method:** Setup procedure skips warm-up cycle on night shift → Procedure gap?

**Material:** Raw casting from Supplier X has 0.3mm more stock than Supplier Y → Variation?

**Measurement:** CMM probe tip worn — last calibration 8 months ago → False readings?

**Environment:** Night shift ambient temp 5°C lower than day shift → Thermal contraction?

**Root Cause Found (via 5-Why on Machine):** Spindle bearings past replacement interval → 5-Why: Why not replaced? → PM schedule didn't account for 24/7 operation → MRC: PM schedule designed for single-shift operation.

Fishbone vs 5-Why

Use fishbone FIRST to cast a wide net across all categories. Then use 5-Why to drill deep into the 2-3 most likely cause branches. They work together — fishbone provides breadth, 5-Why provides depth.

Key Takeaways

1. Fishbone maps ALL possible causes before narrowing down

2. The 6Ms ensure you don't miss entire categories of causes

3. Always verify with data — don't circle causes based on opinion

4. Combine with 5-Why for the most likely cause branches

5. Update your fishbone as new evidence emerges during investigation