Complete firstComplaint or defectnot in catalog
A concrete complaint, a recurring defect, or an urgent problem with measurable impact is present.
Without: Without a concrete complaint, 8D is played through as a formal ritual without learning value.
RunsheetOperations
8D Problem Solving
ComplexityHigh
Time1-6 Wochen
Participants4-10
FormatWorkshop + async
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstBlameless Postmortem
A culture and format of blame-free review are established so that D5 (root cause) is worked out honestly.
Without: Without a blameless norm, 8D slips into blame assignment and systemic causes remain hidden.
02
Preparation
What needs to be ready before start
Materials
8D report template, typically a document with eight sections D1-D8; whiteboard for team setup; data and logs for the defect; templates for Ishikawa and 5 Whys; customer contact information; trace data of affected deliveries.
People / roles
An experienced 8D lead; champion or sponsor; 4-7 people with domain knowledge (quality, production, engineering, logistics); customer or customer representative if external; a scribe.
Pre-read
Complaint ID, defect description, affected delivery quantity, customer, deadline; known predecessor cases; valid standards (for example AIAG, VDA); available retain samples and logs.
Time needed
D0-D3 in 24-48 h, complete in 4-12 weeks
Setup
Open the 8D report template, sections D1-D8 on a board or shared document. D1 (team) and D2 (problem description) as the first visible section. Fix daily goals and commitments. Open the communication channel to the customer.
03
Core question
The one question this method answers
Which systematically evidenced cause system produced the defect, which immediate and corrective measures prevent further damage, and how is recurrence prevented permanently?
04
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1D0+D1: Emergency action and team | Day 0-1 | D0: Immediate containment to limit damage (shipment hold, quarantine). D1: Name the team, lead, members with responsibilities, champion. Contact the customer. | D0 is not optional. Starting 8D without emergency action risks follow-up complaints. The D1 team must have decision authority, not just advisory power. |
2D2+D3: Problem and containment | Day 1-3 | D2: Describe the problem precisely (what, where, when, how much, how). D3: Containment actions (sorting out, 100% inspection, replacement delivery). Verify containment effect. | Containment is temporary. If containment is still running after 3 weeks, D5/D6 are missing. Set a threshold: containment max until D7 verification. |
3D4+D5: Root cause | Week 1-4 | D4: Collect cause hypotheses (Ishikawa, 5 Whys, brainstorming). D5: Test hypotheses with data and verify the root cause(s). Separate cause of defect from cause of non-detection. | Often only the cause of defect is searched. Equally important: why did the control system (inspection, test) not detect the defect. Two root-cause strands in parallel. |
4D6+D7: Corrective measures | Week 4-8 | D6: Permanent corrective measures for cause of defect and cause of non-detection. Verify effectiveness (pilot, test). D7: Prevent recurrence (standards, processes, tools). Remove containment. | D6 without proof of effect is not closure. D7 is often the hardest part: transfer lessons to other products or processes. Cross-functional review helps. |
5D8: Team recognition | 1 day | Team reflection: what went well, what did not. Recognition for performance. Store lessons learned in the central knowledge base. Close the 8D report with customer sign-off. | D8 is often skipped and harms the method over time. Recognition and a lessons-learned entry are discipline measures; otherwise willingness drops for the next complaint. |
05
Artifact
What comes out at the end
Form
8D report document with all eight sections D1-D8, data and test evidence for root cause and corrective measures, customer sign-off, lessons learned, and cross-references to affected standards or processes.
Versioning / ownership
One 8D per complaint with ID, date, team lead, and champion. Version state with date. For re-openings (repeat, new insights), create a new iteration with a reference to the previous one; keep the original 8D report.
Tool alternatives
- Standard 8D template in Word or PDF
- Confluence page in the quality space
- Dedicated QMS tool, for example Plex, SAP QM, MasterControl
- Markdown in the repo under quality/8d-<complaint-id>/
8d-problem-solving-working-template.md
Compact working template for 8D Problem Solving with context, input, output artifacts, and next step.
8D Problem Solving Working Template
Goal
Eight-step problem-solving method for containment, root cause analysis, and permanent correction.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- 8D Report:
- Containment Plan:
- Root Cause Evidence:
- Corrective Action Plan:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
06
Example output
Concrete filled scenario, fictional example
8d-problem-solving-beispiel.md
Concrete filled scenario, fictional example
8D — Complaint 2026-R-0341, hardware bundle 'Pro Kit', customer Mueller GmbH
Lead: @ben. Champion: Quality Director. Opened: 02.05.2026.
D1 Team
Quality, Production, Engineering, Logistics, Customer Service, customer representative (Mueller QA).
D2 Problem description
42 of 120 delivered bundles contain USB cable type C instead of type A. Impact: the customer cannot integrate them into existing peripherals, production stops for 4 h, damage EUR 18,500.
D3 Containment
02.05.: remaining stock locked (320 units), 100% inspection. Replacement delivery of 78 correct bundles by express on 03.05.
D4 Cause hypotheses
Fishbone: wrong component in bill of materials, pick error in warehouse, changed supplier version without update. 5 Whys on top hypotheses.
D5 Verified root causes
- Cause of Defect: Supplier changed the USB variant without labeling it, and the engineering change note was not carried over.
- Cause of Non-Detection: Goods receipt checks only quantity, not variant; no sample test for USB type exists.
D6 Corrective measures
- Supplier EC process: written confirmation per variant, effective 15.05. (owner @anna).
- Goods receipt: add USB type test to the sample routine, effective 12.05. (owner @marlene).
- Verification: pilot 6 deliveries without defects between 12. and 30.05.
D7 Recurrence prevention
Updated FMEA for all USB variants; supplier evaluation revised (labeling requirement); quality plan adapted for comparable bundles ('Office Kit', 'Mobile Kit').
D8 Recognition
Team retro on 28.05.: quick response acknowledged; lessons captured in the central KB section 'Supplier EC'. Customer sign-off 30.05.
07
Pitfalls
Recognize symptoms and steer against them
Trap
Containment lasts too long
Symptom
100% inspection runs for 8 weeks without a D6 solution, costs rise, and the team gets used to it.
What to do
Set a threshold: containment max until D7 verification. If delayed, the champion escalates; containment is not the solution.
Trap
Only cause of defect, not non-detection
Symptom
D5 lists only the direct cause and omits the question of why the control failed.
What to do
Run two root-cause strands in parallel: why the defect emerged and why it was not detected. Both strands need measures in D6.
Trap
Blame instead of system cause
Symptom
Root cause is 'employee overlooked the variant', and no systemic level is reached.
What to do
If the root cause is personalized, ask further: which safety net was missing. If the control was absent, that gap is the root cause, not the person.
Trap
D7 forgotten or superficial
Symptom
D6 fixes the current case, D7 is just a phrase ('training expanded'), and no system transfer happens.
What to do
D7 requires a cross-functional review: which other products, processes, or suppliers have a similar risk. Check at least 2-3 additional areas.
Trap
D8 omitted
Symptom
Complaint closed, no lessons-learned entry, no team reflection. The next complaint starts from zero again.
What to do
D8 is part of the report, not an appendix. Make the 1-2 week follow-up after D7 closure mandatory. Store lessons in the central KB, not only in the 8D report.
Trap
Wrong method frame
Symptom
8D is applied to a minor complaint and the overhead eats the benefit.
What to do
8D is for significant complaints with systemic risk. Use A3 or a simple postmortem for minor cases. Define a threshold, for example damage amount or repeat risk.
08
Stop criteria
Done signals checkable in under a minute
The defect is not reproducible or specifiable, so containment and analyze have no anchor.
The customer demands an immediate solution without willingness to collaborate, and data and retain samples are unavailable.
Team members are not freed up for at least 20% capacity, so 8D drags on for 12 weeks without effect.
The blameless culture is missing and the root-cause analysis slips into blame.
The complaint is a minor case without systemic risk, so 8D is oversized.
Champion or sponsor is missing, so phase discipline and D7 transfer fail.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.