Radical Quality — From Toyota to Tech
summary
Presents Toyota’s Dantotsu quality program adapted for software, showing it reduced defects ~85–88% in three years by using an 8-step root‑cause routine finished within 24 hours, an ABCD defect classification tied to CI/QA/production boundaries, and regular QC problem‑resolution sessions. Describes practical practices—visual standards, dojo training, templates and concrete countermeasures—and reports pilot results (bug backlog reductions of 5x to 16x) with metrics normalized to days billed or change‑failure rate.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:45Tech bugs problem
- 3:55Toyota zero-defect strategy
- 12:01Radical defect resolution
- 17:37Key concepts from San anora
- 24:35Hocus case study
- 30:20Oloron case study
- 34:37Fintech client experience
- 37:27Simplified defect analysis
- 41:18Conclusion
- 43:33Q&A
related talks
40mReal Quality Assurance from an Agile and Lean Viewpoint
30mA framework for ambitious companies
44mExceeding Expectations, Inspiring Quality
43mImproving Software Quality with Retrospectives
27mTrue North and Technical Debt
52mToyota Kata - Retrospective on Steroids
45mDeming's Management Philosophy for Testers Teams
21mRadical Therapy for Software Teams