Principles for managing product quality
summary
Claims systems thinking gives the highest leverage for lasting quality, and backs it with concrete examples: a small tool for predicting system behavior built on loopy used to map feedback loops, a Facebook homepage case where fixes like docs tooling and t‑shirts reduce regressions, and retro tactics like five whys that reveal cultural root causes. Examples include a bounded query fix, the growth‑and‑underinvestment pattern, and “fixes that fail,” and outcomes show measurable, lasting improvement rather than vague theory.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:22Understand systems
- 2:32Use systems
- 2:46Systems thinking
- 3:58Four types of thinking
- 4:49Event oriented thinking
- 8:00Systems oriented thinking
- 8:47Growth and under investment
- 10:25Quality
- 13:45Systems Patterns
- 14:26Shifting the Burden
- 15:26Conclusion
related talks
28mInstilling the built-in quality mindset into a dev team
46mQuality Engineering for DevOps Teams
20mEnsuring Quality in DevOps Culture
41mQuality Transformation
54mValue Streams, Quality Engineering And You
26mTen Product Mindset Rules for DevOps Teams
27mWe're All in This Together
05mHow does Quality fit in CALMS?
