Best Practices for Availability
summary
Company asks 100+ distributed SaaS teams to meet SLAs without extra budget; response is a co-created Best Practices for Availability document and two instruments: a maturity model and a failure mode analysis based on Six Sigma across 13 problem domains. Piloting six high-performing teams (each at 99.99+% uptime) produces a heat‑map visualizing probability and outage‑minute impact, a central SLA dashboard, mandatory service enrollment, and ongoing resubmissions — a measurable program that identifies riskiest domains and drives engineering and management investment.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:25How to get teams to work with you
- 6:22Key points
- 9:48Teams
- 11:55Culture
- 15:55Service Management
- 18:45Predictive Exercise
- 21:25Course Instrument
- 23:55Future Work
related talks
49mWhat It Really Means for Your System to Be Available
38mImplementing SRE practices: SLI/SLO deep dive
46mMeeting Impossible SLAs: How we made our uptime 99.999%
30mImproving Reliability w/ Error Budgets & SRE
30mMetrics for good, not evil
25mBuilding a highly scalable system to assure Business Resilience
29mAutomating Continuous Compliance for Scalable SaaS Delivery
45m⚡A Resilient Application in a Partially Degraded World ⚡
