Zero Defects in Simple Terms
Zero defects does not claim that no defect will ever occur. It means the organisation does not plan for defects or treat them as acceptable. Each defect is a signal to find and remove its cause, not a number to stay under.
Key Principles
- Quality means meeting requirements, so requirements must be clear.
- Prevention, not inspection: build quality in with methods such as poka-yoke instead of sorting it out at the end.
- The standard is zero defects, not an acceptable quality level.
- Measure quality by its cost: the cost of poor quality makes problems visible in money terms.
Example
An assembly line used to accept a few missing clips per thousand as normal and relied on final inspection to catch them. Under a zero defects approach the team adds a sensor that stops the station if a clip is not detected, and treats every escape as a problem to analyse with root cause analysis. Missing clips at final inspection fall to almost none.
Common Criticisms and Mistakes
- Running it as a slogan campaign without changing processes or giving people the means to improve.
- Blaming workers for defects that come from the system.
- Confusing the goal with the measured result, so teams hide defects to protect their numbers.
Recording every rejected inspection and its corrective action, as OperaHive quality inspection software does, gives the data needed to work toward the goal.