The 'Success' in SRE Is Silent
summary
Claim: ROI for reliability is not found in headline metrics but in concrete changes to people and process. Quantitative measures like MTTR is misleading and “nines” fail for distributed customer-facing systems; an experiment with observability and observability (high-cardinality tracing) produces Kirkpatrick levels: reaction→learning→behavior→business result as a practical ROI ladder. Example: a year-long SRE placement on a large “apple” service handling millions of requests per second boosts throughput temporarily, introduces a supplier change that kills 10 trees, and ultimately fails to justify the program.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:17My SRE Experience
- 4:51Expertise
- 7:17Giant Cephalopod
- 10:00Security vs Availability
- 13:03SRE vs Reliability
- 13:46Im in the hot seat
- 14:07Its not just you
- 14:35Regulation
- 15:18Certification and Licensing
- 20:20Quantitative Methods
- 21:37Availability
- 24:53Qualitative Methods
- 28:20Invasive Pest
- 28:41Fired
- 29:04Conclusion
related talks
43mThe SRE I Aspire to Be
58mEnterprise Roadmap for SRE
41mSRE in Enterprise
43mWhere SRE Can Go Wrong
35mThe Best SREs Seem to Be the Ones without an SRE Title—And What We Can Do
29mThe Curious SRE: Cultivating a Mindset for System Resilience
49mWhat SRE Could Be: Systems Reliability Engineering
22mSRE for Enterprises