Free Trial

← Back to blog

Quality managementReading time 12 min

How to write an 8D that does not come back rejected

8D is not a form. It is a test of whether you really found the cause. Filling in the boxes is easy; passing review is not.

8D

01The eight steps

StepNameDeliverable
D1Form the teamCross-functional list with responsibilities and an owner
D2Describe the problem5W2H, the symptom, quantity, lot numbers, occurrence rate
D3Interim containmentDisposition and completion time for shipped, in-stock, WIP and in-transit material
D4Root causeOccurrence cause plus escape cause, each verified
D5Permanent corrective actionThe chosen action and verification of its effectiveness
D6Implement and confirmImplementation date, lot number, tracking data
D7Prevent recurrenceStandardisation: SOP, FMEA, control plan, gauges
D8Close and recogniseHorizontal deployment to similar processes and part numbers
D3 has to be complete within 24 to 48 hours; everything from D4 onward usually gets 15 to 30 days.

02D4: two causes, not one

A sound 8D answers two questions and cannot skip either:

  • Occurrence. Why was the defect produced?
  • Escape. Why, having been produced, was it not caught?

An 8D with only the occurrence cause will be sent back. Even with the process fixed, the hole in the detection system remains, and the next different problem will escape the same way.

Ask why until you reach something you can control

LevelExampleAssessment
SymptomDimension out by 0.05 mmNot yet a cause
Direct causeTool wear past the limitGetting closer
System causeTool changes judged by experience, with no defined limitNow at a level you can change
Management causeThe work standard sets no tool change criterionRoot cause
Stopping at “the operator was careless” is the most common failure. People will always be careless; the system has to absorb it.

03D5: the action has to be verifiable

The quality of a permanent action depends on which level of the error-proofing hierarchy it sits at.

LevelApproachEffectiveness
1. EliminateChange the design so the problem cannot occurHighest
2. Mistake-proofGet it wrong and it will not assemble, or the machine will not runHigh
3. DetectAutomatic detection that stops the lineMedium
4. ControlSPC monitoring of the trendMedium-low
5. ProcedureSOP, training, extra patrol inspectionLowest
A corrective action that stops at level 5 will usually not be accepted.

04Five things a reviewer will look for

  1. Are quantity and scope clear in D2? Affected lots, date range, quantity already shipped.
  2. Does D3 cover everything in transit? The customer, the warehouse, WIP and the supplier all need a disposition.
  3. Does D4 give both causes? Occurrence and escape.
  4. Is D5 high enough in the hierarchy? Stopping at training gets it rejected.
  5. Did D7 go back and change the documents? FMEA, control plan, SOP and gauge list must all be updated, with revision and date.

The last of these is the most often missed. If the FMEA is not updated once the 8D is closed, the same failure mode will come round again on the next project.