Pitching SRE to your Senior Executives
summary
82% of orgs see at least one unplanned outage in three years, averaging two outages of four hours and roughly $2M cost, so the proposal centers on cutting that downtime with SRE practices: move from monitoring to observability, introduce canary and blue‑green deployments, automate toil with chatbot auto-resolution 25% and self‑healing, adopt chaos engineering and immutable infra, measure SLOs (example: error budget 4%), and shift ops from cost center to value center — these changes are presented with a pilot balanced‑scorecard and demonstrated reductions in MTTR and deployment risk.
AI-written summary · about
chapters (10)
- 0:00Pitching SRE to executives
- 2:00Executives care about downtime
- 4:06Monitoring to observability
- 6:53SRE top job in 2022
- 9:18SRE tenets for business value
- 13:10Revamping ops with SRE
- 16:24SRE adoption case study
- 18:51SRE outcomes scorecard
- 21:39Measuring SRE success
- 23:44Communicating SRE value
related talks
07mIGNITE: Metrics, Margins, Mutiny – How to make your SREs (not) run away
16mSRE in Transition: From Startup to Established Business
45mClearing the Way for SRE in the Enterprise
18mWe need to talk about SRE burnout
45m“Disorganizing” Your SRE Organization
23mSite Reliability Evangelism: Practice Start-up within an Established...
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
41mAn Introduction to SRE at Google (with DevOps Focus)