D8 — What Happens After an 8D Is 'Done'? D8 Closure and Lessons Learned

Part of the 8D methodology (D0–D8).

Discipline 8 (D8) is the formal closure. It is about acknowledging the effort of the team and archiving the knowledge for the future.

Should You Reward the Team Who Caused the Problem? Solving complex quality problems is stressful. Formal recognition, whether a small award, a team lunch, or a mention in the company meeting, reinforces the value of quality and encourages employees to engage in future problem-solving efforts.

What Goes Into a Lessons-Learned Database? The 8D report is a technical asset. It should be stored in a searchable database so that future engineers facing similar problems can learn from this case.

How Do You Close an 8D That Reopens? The 8D is not closed until the Champion and the Quality Director have reviewed and signed the document. This ensures that no steps were skipped and that the organization is satisfied with the outcome.

What Should a Lessons-Learned Database Look Like?

Each entry: D2 problem, D4 root cause, D5-D6 actions, D7 prevention, key metrics. Tag with failure mode, product family, process, material, customer. A future engineer should find related cases within seconds.

Real-World D8: The Cost of Not Closing Properly

A supplier had recurring gasket leaks across three programs. After the third occurrence, horizontal audit was mandated for every closure. This eliminated the issue. Three investigations cost $120,000. The audit added 4 hours per closure but saved $80,000 per year.

Closure Criteria Checklist

Verify: D3 containment removed only after D6 validation, D4 root cause confirmed, D5 verified with adequate sample size, D6 monitored, D7 FMEA updated, D8 horizontal deployment verified. Each needs documented evidence.