Is 8D an ISO standard?

No. 8D is a structured problem-solving method popularised by the automotive industry. Customer expectations for 8D format and depth vary — always follow the specific customer or company standard.

How long should an 8D take?

There is no fixed rule. A typical automotive customer expects containment (D1–D3) within 24–48 hours and a full report within 15–30 days. Complex root-cause work often runs longer, with interim reports issued at each phase.

Do I always need to do all eight disciplines?

For a formal customer 8D, yes — even if a step is short. For internal problems you can scale the report, but skipping containment (D2) or verification (D5) usually causes the problem to reopen.

8D vs 5 Why vs A3 — how do I choose?

5 Why is a tool used inside 8D and A3 for root-cause analysis. 8D is best for reactive defect/complaint investigations. A3 is better for improvement projects and system-level thinking. See the comparison pages linked below.

Getting started · Getting started

What is 8D problem solving?

8D — the Eight Disciplines — is a structured problem-solving method used by quality, manufacturing and supplier-quality teams to respond to defects and customer complaints. It forces a team to contain the problem quickly, prove the root cause with evidence, and put permanent corrective action in place before closing.

Key takeaways

8D has eight disciplines from D1 (define the problem) to D8 (recognise the team), plus a D0 preparation step in some variants.
Containment (D2) and verification (D5) are the phases most often skipped or done superficially.
Root cause proof (D4 preparation) requires evidence a peer can reproduce — not opinions.
8D reports are audited by customers and regulators, so evidence and approvals must be traceable.

Where 8D came from

8D was formalised by Ford Motor Company in the late 1980s as a team-based approach to solving recurring quality problems. It packaged existing tools — 5 Why, Ishikawa, Is/Is-Not, control plans — into a repeatable structure that a supplier or plant could follow.

Today, most automotive customers still ask for 8D reports for warranty and PPAP incidents, and the same structure is used by electronics, medical device, aerospace and general manufacturing organisations. 8D is a de-facto standard, not a certification.

What 8D actually solves

8D is designed for problems that have all three of the following properties:

The problem is real and observable — a defect, complaint, escape or nonconformance, not a theoretical risk.
The cause is not obvious and requires investigation — a checklist or a single Why is not enough.
The consequences justify a structured team response — customer impact, safety, cost, or a repeating pattern.

For simple problems (obvious cause, low impact), 8D is overkill. Use a lightweight NCR or 5 Why instead. For system-level improvement, use A3 or DMAIC. The comparison pages linked below make this concrete.

The eight disciplines at a glance

D1 — Establish a team with the right skills, roles and authority.
D2 — Contain the problem so no more defective product reaches the customer.
D3 — Describe the problem precisely (Is / Is-Not, quantities, timeline).
D4 — Identify and verify the root cause and the escape point.
D5 — Choose and verify permanent corrective actions.
D6 — Implement the corrective actions and confirm effectiveness in production.
D7 — Prevent recurrence by updating systems (control plan, PFMEA, work instructions).
D8 — Close, recognise the team and hand over lessons learned.

Common misconceptions

"8D is an ISO standard." It is not. 8D is a widely adopted method; customer expectations vary.
"8D means writing an 8D report." The report is a by-product; the investigation is the work.
"D2 containment is optional." If defective product is still shipping, D2 is the first priority.
"You can start D4 without a clean D3." Root-cause work is only as good as the problem statement.

Frequently asked questions

Is 8D an ISO standard?: No. 8D is a structured problem-solving method popularised by the automotive industry. Customer expectations for 8D format and depth vary — always follow the specific customer or company standard.
How long should an 8D take?: There is no fixed rule. A typical automotive customer expects containment (D1–D3) within 24–48 hours and a full report within 15–30 days. Complex root-cause work often runs longer, with interim reports issued at each phase.
Do I always need to do all eight disciplines?: For a formal customer 8D, yes — even if a step is short. For internal problems you can scale the report, but skipping containment (D2) or verification (D5) usually causes the problem to reopen.
8D vs 5 Why vs A3 — how do I choose?: 5 Why is a tool used inside 8D and A3 for root-cause analysis. 8D is best for reactive defect/complaint investigations. A3 is better for improvement projects and system-level thinking. See the comparison pages linked below.