8D Problem Solving: 8 Proven Steps to Fix Recurring Defects

8D problem solving is a structured, team-based method that finds the root cause of a recurring defect, contains it, corrects it, and prevents its return through eight defined disciplines running from D1 to D8, giving aerospace and manufacturing suppliers a disciplined way to close customer complaints and satisfy AS9100 auditors. It replaces guesswork with evidence.

In the quality systems we build for aerospace and manufacturing clients, a rejected 8D report is usually the moment a supplier relationship starts to slip. The method itself is not difficult. What trips teams up is jumping to a fix before the root cause is proven, then watching the same defect come back three months later. This guide walks through 8D problem solving the way we coach clients to run each discipline on the floor.

What is the 8D problem solving method?

8D problem solving, short for the Eight Disciplines, is a corrective action framework popularized by Ford in the 1980s and now standard across automotive, defense, and aerospace supply chains. When a customer raises a complaint or an internal audit flags a repeat nonconformance, 8D problem solving gives a cross-functional team one shared format to investigate and respond. Each discipline has a specific job, and you do not move forward until the prior step holds up to evidence.

The 8 disciplines: D1 through D8

Here is what each of the eight disciplines actually asks your team to do:

1. D1: Build the team. Assemble a small cross-functional group that owns the process, the product, and the data. Name a champion and a team leader.
2. D2: Describe the problem. Define the defect in measurable terms: what, where, when, how many. Use is / is-not analysis so you are not chasing a vague symptom.
3. D3: Contain it. Put interim containment in place so no defective product reaches the customer while you investigate. Sort suspect stock, add a temporary inspection, quarantine lots.
4. D4: Find the root cause. Use the 5 Whys and a fishbone (Ishikawa) diagram to separate the true cause from contributing factors. Verify each candidate cause against real data.
5. D5: Choose permanent corrective actions. Select fixes that address the verified root cause, not the symptom, and confirm they will not create a new failure mode.
6. D6: Implement and validate. Put the corrective action into production and prove it works with measurement over time, not a single good part.
7. D7: Prevent recurrence. Update the control plan, work instructions, PFMEA, and lessons learned so the same cause cannot resurface elsewhere.
8. D8: Recognize the team. Close the report, document results, and acknowledge the people who did the work.

What does 8D stand for?

8D stands for Eight Disciplines. Some organizations add a D0 planning step at the front, which makes it a nine-step process on paper, but the core method your customers expect to see is still the eight disciplines above. On aerospace programs, the 8D format often maps directly to the corrective action request (CAR) your prime contractor issues under AS9100.

What are the 5 Whys in 8D?

The 5 Whys is a root cause technique used inside D4. You start with the defect and ask “why” repeatedly, each answer feeding the next question, until you reach a cause you can act on rather than another symptom. Five is a rule of thumb, not a law; sometimes three whys are enough and sometimes you need seven. The discipline is refusing to stop at the first convenient answer. We pair the 5 Whys with a fishbone diagram so the team considers method, machine, material, measurement, people, and environment before settling on a cause.

8D vs a quick fix: what actually changes

Common mistakes in 8D problem solving

Most rejected reports fail for the same handful of reasons. Skipping containment in D3 and letting suspect product ship. Confusing a contributing factor for the root cause in D4. Writing corrective actions that describe the symptom (“operator will be more careful”) instead of a system change. And closing the 8D at D6 without ever updating the PFMEA or control plan in D7, which guarantees the defect comes back on the next program.

The OQS 8D readiness checklist

Before you submit an 8D problem solving report to a customer, run it against these five practitioner checks we use with clients:

• Data, not opinion. Every claimed root cause has a measurement, a sample size, or a trial behind it.
• Containment is dated and closed. D3 shows when interim action started and when permanent action replaced it.
• Read-across done. You checked whether the same cause affects sister parts, other lines, or other customers.
• Documents actually changed. The PFMEA, control plan, and work instruction revisions are attached, not promised.
• Effectiveness has a date. D6 states the review date and the metric that will confirm the fix held.

Running 8Ds well is also an audit skill. A strong internal audit program surfaces repeat findings early, and connecting each corrective action back to your PFMEA is what stops the same failure mode from reappearing. For the underlying discipline of quality methods, the AIAG maintains the core reference material many aerospace and automotive customers expect suppliers to follow.

8D problem solving FAQ

Is 8D only for automotive? No. 8D started in automotive but is now used across aerospace, defense, medical devices, and general manufacturing anywhere a customer requires a formal corrective action.

How long should an 8D take? Containment (D3) should happen within days. A full 8D with verified root cause and validated corrective action typically runs a few weeks, depending on how long effectiveness monitoring takes.

Do I need software to run 8D? No. Many teams run 8D on a standard form or spreadsheet. The rigor comes from the discipline of the process, not the tool.

How does 8D fit with AS9100? AS9100 requires a documented corrective action process, and the 8D format satisfies it cleanly. If you need help building that system, talk to our team about corrective action and audit readiness.