Unknown
UnknownZero-Defect Principle
Quality should be built into the process, not inspected in after the fact.
Popularity
Usefulness
Aliases
Unknown
Domains
Unknown
Definition
- The
Core Idea
- Quality should be built into the process, not inspected in after the fact.
- Defects are signals that requirements, controls, or execution need to improve.
- The goal is prevention and conformance to requirements, not acceptance of an "allowable" error rate.
How It Works
- Define requirements clearly.
- Design processes, training, and controls to prevent errors before they happen.
- Measure defects and remove their causes instead of normalizing them.
Usage Example
- A factory reduces rework by mistake-proofing a packaging step so that parts can only be assembled in the correct orientation.
Famous Example
- Example: Philip Crosby's zero-defects philosophy in quality management.
- Why it fits this rule: It treats defects as preventable failures of process and discipline, not as an unavoidable cost of doing business.
- Verification status:
Use Cases / Situations Where It Applies
- Quality-critical manufacturing and operations.
- Safety-sensitive work where defects have outsized consequences.
- Service processes where preventable errors damage trust.
When Not to Use or Common Misuse
- Do not confuse zero defects with punishing individuals for every mistake; the point is prevention, process design, and clear requirements.
- Do not pretend that literal perfection is free or effortless.
- Do not use the slogan without investing in training, feedback, and error-proofing.
Rule Invention / Origin
- Invented by: Philip B. Crosby popularized the concept.
- Year of invention: 1960s.
- Country / context of origin: United States quality management.
Evidence / Research Basis
- Supported by quality-management practice focused on prevention, conformance to requirements, and continuous process improvement.