Know Thy Enemy: How to Prioritize and Communicate Risks
summary
Customer Reliability Engineering adapts SLOs and error budgets into a quantifiable prioritization process by computing expected cost = likelihood × impact, where likelihood uses estimated time between failures and impact uses estimated time to resolution and percent users affected. A shared spreadsheet stacks risks and shows minutes per year (99.99% SLO ≈ 50–53 minutes budget) so anything over a 25% threshold (~13 minutes) is flagged for work. The lightweight tool proves useful with customers to shift debates from gut feeling to numbers.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:00Definition of Risk
- 6:26Personal Perspective
- 8:54Its Not All Bad
- 10:17Ignore It
- 13:19Intuition
- 17:50Risk Matrix
- 22:42Expected Cost
- 25:16Expected Cost for Air
- 26:37Estimated Time to Resolution
- 27:44Annual Budget Impact
- 31:04Stack Rank of Risks
- 34:02Summary
- 35:36Never Events
related talks
29mAre We There Yet? Metrics-Driven Prioritization for Your Reliability Roadmap
47mCultivating Production Excellence
30mReliable Observability at Scale: Error Budgets for 1,000+
25mPitching SRE to your Senior Executives
34mReliability and Engineering Requirements
43mThe SRE I Aspire to Be
05mSLOs: You’re missing the point!
33mThe Value of Reliability