Problem Solving & Quality · Act

8D Method

Eight disciplines from team to recognition — including containment, verified root cause, permanent fix and prevention — in the format customers expect.

Time4 h+
FormatTeam
StageAct

8D Method: what it is and why it works

8D, Eight Disciplines, is a team problem-solving method and report format widely used to answer customer complaints, especially in the automotive and aerospace supply chains. The disciplines are: D1 form the team; D2 describe the problem with facts; D3 put interim containment in place; D4 identify and verify the root cause, both for why the defect occurred and why it escaped detection; D5 choose and verify permanent corrective actions; D6 implement them and confirm the results; D7 prevent recurrence across systems and similar products; D8 recognize the team and close. Many organizations add D0 to decide whether an 8D is warranted and to plan emergency actions.

8D works because it separates protecting the customer from solving the problem and forces both. Containment in D3 buys time without pretending to be a fix. The two root causes in D4, occurrence and escape, lead to actions on both the process and the detection system. D7 pushes the learning into FMEAs, control plans and similar products, where yokoten spreads it further. Customers value the format because it is traceable and familiar. Compared with DMAIC, 8D is faster and response-driven; tools such as immediate containment, Is/Is-Not and structured whys plug into its disciplines.

What you need

A customer complaint or internal problem with its first facts and samples
A small cross-functional team with a leader and a management sponsor
Access to production records, inspection data and the affected parts
The customer's specific requirements for 8D reporting and deadlines

What you get

Verified containment protecting the customer
Verified root causes of occurrence and of escape
Implemented and validated permanent corrective actions
Updated FMEA, control plan and standards, and a completed 8D report

When to use it

When a customer complaint needs a structured, traceable answer with deadlines.

How to do it, step by step

D1 form a small cross-functional team with a leader; D2 describe the problem with facts (5W2H, Is / Is-Not).
D3 put interim containment in place and verify that it protects the customer.
D4 find and verify the root cause of occurrence and the escape point where detection failed.
D5 choose and verify permanent corrective actions; D6 implement them, remove containment and confirm the results.
D7 prevent recurrence — update FMEA, control plan, standards and similar products; D8 recognize the team and close.

Worked example: Burrs on stamped brackets

Illustrative scenario — figures are realistic but not from a real company.

A tier-2 automotive supplier stamps steel mounting brackets. A tier-1 customer found burrs on the inside edge of a hole that cut a wiring harness sleeve during assembly, and reported 38 suspect parts from one shipment. The customer requested containment within 24 hours and a complete 8D within its standard deadline.

D1–D2: a team from production, tooling, quality and logistics described the problem with Is/Is-Not: one part number, one die, one hole, parts produced since the previous Tuesday; other holes and dies were not affected.
D3: all stock at the plant, in transit and at the customer was sorted using a go/no-go edge check; certified parts were marked with a green dot. The customer confirmed no further escapes.
D4: the occurrence cause was a chipped punch, due to a missed regrind interval after a production volume increase. The escape cause was that the end-of-line visual check could not see the inside edge of the hole.
D5–D6: punch regrind was switched from a calendar interval to a hit counter on the press, and a feeler check of the hole edge was added at first-piece and every 500 parts. Results were verified over four weeks before containment was lifted.

Result. D7 updated the PFMEA and control plan, and the hit-counter regrind trigger was applied to 14 other dies with similar punches. D8 recognized the team at the plant meeting. No further burr complaints were received in the next six months, and the customer closed the 8D on first submission.

Open it in the FieldKit Problem Solving app → Get the Problem Solving template pack — join the waitlist

Common pitfalls and how to avoid them

Treating containment as the corrective action and closing the 8D.Keep containment until permanent actions are verified in D6, then remove it deliberately and confirm results hold.
Looking only for why the defect occurred and ignoring why it was not detected.Analyze and act on both occurrence and escape root causes in D4 and D5.
Writing "operator error" or "retraining" as the root cause and fix.Ask why the process allowed the error; target system causes, using the hierarchy of controls to choose actions.
Skipping D7, so the same failure appears on similar products.Update FMEAs, control plans, standards and similar parts, and track horizontal deployment.

Frequently asked questions

What are the 8 disciplines of 8D?

D1 build the team, D2 describe the problem, D3 implement interim containment, D4 identify and verify root causes, D5 choose and verify permanent corrective actions, D6 implement and validate them, D7 prevent recurrence, and D8 recognize the team and close. Many organizations add D0, planning and deciding whether an 8D is needed, with emergency response actions.

What is the difference between 8D and 5 whys?

5 whys is a single questioning technique for tracing a cause-and-effect chain. 8D is a complete problem-solving process that includes team formation, problem description, containment, root cause analysis, corrective actions, prevention and closure. The whys technique is often used inside D4 of an 8D, alongside tools such as Is/Is-Not, fishbone diagrams and data analysis.

How long does an 8D take to complete?

It depends on the problem and the customer's requirements. Containment is typically expected within a day or two, and customers often set a deadline for the root cause and the full report. Confirming the effectiveness of permanent actions in D6 can take several weeks of production data. Always check the customer-specific requirements, which usually define the expected timing.

Origin

8D (Eight Disciplines) — Ford Motor Company, Team Oriented Problem Solving manual, 1987; D0 added later.

Used in these playbooks

Customer complaint closure 4 weeks

Four weeks to answer a complaint the way customers expect: a structured 8D, a clean problem statement, causes of occurrence and escape, an error-proof fix and deployment to sister lines.

Related methods

More in “Act”

Plan, pilot and run the fix — with owners, dates and a structured roadmap.