Guide

The 8D Problem-Solving Methodology

A comprehensive reference for quality engineers responding to supplier corrective action requests (SCARs) using the Eight Disciplines framework.

What Is 8D?

The Eight Disciplines (8D) methodology is a structured, team-based approach to identifying, correcting, and preventing recurring problems. Originally developed by Ford Motor Company in the 1980s, it has become the de facto standard for supplier corrective action responses across automotive (IATF 16949), aerospace (AS9100), medical device (ISO 13485), and general manufacturing industries.

The methodology walks teams through eight sequential disciplines, from forming the right team (D1) to celebrating closure (D8). Each discipline builds on the previous one, creating a traceable chain from problem identification through root cause analysis to verified corrective action.

An 8D report is not just documentation — it is evidence that your organization has a systematic process for resolving quality issues and preventing them from recurring. This is what auditors and customers evaluate.

D0 — Prepare and Plan

Before formally starting the 8D process, assess whether the problem warrants a full 8D investigation. Not every complaint requires eight disciplines — minor issues may be resolved with a simple corrective action. D0 is the triage step.

Key questions:

  • Is this a recurring problem or a one-time event?
  • What is the severity? Safety, regulatory, or customer impact?
  • Is the problem clearly defined, or does it need scoping?
  • What data is available? Inspection records, reject quantities, dates?
  • Does the customer require a formal 8D response?

D1 — Establish the Team

Identify a cross-functional team with the process knowledge, authority, and time to solve the problem. The team should include people who understand the product, process, and customer requirements. Assign a team leader and a champion (management sponsor).

Best practices:

  • Include at least one person from production, quality, and engineering
  • Name specific individuals with roles — not department names
  • Keep the team to 4–8 people to maintain focus
  • The team leader should have authority to implement changes

Common rejection trigger: listing “Quality Department” instead of named individuals with roles.

D2 — Describe the Problem

Define the problem in specific, measurable terms using the 5W2H framework: What, Where, When, Who, Why, How, How many. A well-defined problem is half solved. Avoid vague descriptions like “parts were bad” — instead specify the exact defect, affected part numbers, quantities, detection location, and time frame.

Include:

  • Part number(s) and revision level
  • Defect type and specification violated
  • Quantity affected vs. quantity shipped
  • Detection location (incoming, in-process, field)
  • Date range of affected production
  • Customer name and SCAR/complaint reference number

D3 — Implement Interim Containment Actions

Containment protects the customer from further exposure to the problem while the root cause investigation is underway. These are temporary actions — not permanent fixes. The goal is to stop the bleeding immediately.

Typical containment actions:

  • 100% inspection / sorting of suspect inventory
  • Quarantine of affected lots at supplier, in-transit, and customer locations
  • Replacement shipment of conforming parts
  • Rework or screening of WIP
  • Temporary process hold or additional process controls
  • Customer notification with containment scope and timeline

Common rejection trigger: no evidence of containment scope (which lots, which locations) or missing timeline.

D4 — Root Cause Analysis

Identify and verify the root cause(s) of the problem. This is the most critical discipline — corrective actions that don't address the true root cause will fail. Use structured analysis methods and verify the root cause with data.

Common methods:

  • 5-Why Analysis: Ask “why” iteratively until the systemic cause is found. Each “why” should be supported by evidence, not speculation.
  • Fishbone (Ishikawa) Diagram: Categorize potential causes by Man, Machine, Method, Material, Measurement, Environment (6M).
  • Fault Tree Analysis: Top-down logic diagram of failure modes with AND/OR gates.
  • Is/Is-Not Analysis: Compare where the problem occurs vs. where it does not to isolate variables.

Common rejection triggers: “operator error” as root cause without explaining why the system allowed it; no verification that the identified cause actually produces the observed defect.

D5 — Choose and Verify Permanent Corrective Actions

Select corrective actions that address each identified root cause. Each action must have an owner, a due date, and a clear link to the root cause it addresses. Verify that the proposed actions will actually resolve the problem without introducing new risks.

Strong corrective actions:

  • Error-proofing (poka-yoke) — physically prevent the error
  • Process changes with updated work instructions
  • Tooling or fixture modifications
  • Inspection criteria updates with measurement method changes
  • Supplier development or material changes

Common rejection triggers: “retrain operator” as the sole action; no owner or due date; actions that don't map to identified root causes.

D6 — Implement and Validate Permanent Corrective Actions

Implement the chosen corrective actions and validate their effectiveness with data. Define measurable success criteria before implementation so you can objectively determine whether the actions worked.

Validation evidence:

  • Before/after capability data (Cpk, defect rates)
  • Inspection results from post-implementation production runs
  • Test reports confirming the defect no longer occurs
  • Process audit results confirming new procedures are followed
  • Customer feedback on post-correction shipments

D7 — Prevent Recurrence

Extend the lessons learned to prevent the same or similar problems from occurring elsewhere in the organization. This is where the 8D process moves from reactive to proactive. Update systemic controls: FMEA, control plans, work instructions, training materials, and incoming inspection criteria.

Systemic updates:

  • PFMEA updated with new failure mode, severity, detection, and RPN
  • Control Plan updated with new inspection points or frequencies
  • Work instructions revised and operators trained on changes
  • Lessons learned shared across similar product lines or processes
  • Design rules or standards updated if applicable

D8 — Congratulate the Team and Close

Formally close the 8D after verifying all actions are complete and effective. Recognize the team's effort. Archive the report for future reference and audit purposes. Confirm containment actions have been withdrawn (replaced by permanent fixes).

Closure checklist:

  • All corrective actions completed and verified effective
  • Interim containment actions removed
  • Systemic documents (FMEA, Control Plan) updated
  • Customer notified and SCAR formally closed
  • Report archived with full audit trail

Build 8D reports in minutes, not hours

8D Pack automates field extraction, guides you through D1–D8 with structured forms, and exports customer-ready response packs.

Start Free Trial

14 days free / no credit card