Clearing the Way for SRE in the Enterprise
summary
Enterprises fail at SRE because org scar tissue — silos, queues, excessive toil, low trust — prevent the three SRE essentials: service level objectives with consequences, guaranteed engineering time to improve, and self‑regulated workload. Practical fixes: map value streams, reduce handoffs, run an operations‑as‑a‑service platform (example: Rundeck) to expose pull‑based privileged actions, shift decisions left, and set toil limits. Example: a client had ~25,000 approvals in six months with <1% rejected, showing approvals add cost not control.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:02Damon Edwards
- 4:55Principles of SRE are what set SRE apart
- 5:28SLO and Error Budgets: Tools for Shared Responsibility
- 8:21Forces That Undermine SRE Principles
- 9:48Silos cause disconnects and mismatches
- 11:05Silos create labor pools of functional specialists
- 13:26Request queues are an expensive way to manage work
- 15:21What do queues do to value streams?
- 15:53Tickets queues become "snowflake makers"
- 16:58Ticket Queues Undermine SRE Principles
- 17:37Toil is the enemy of SRE
- 19:50Excessive toil prevents fixing the system
- 21:29Where are decisions made? Who can take action?
- 23:39Low trust + approvals = illusion of control
- 26:38Lean on Lean to find what to fix
- 30:52SREs are expensive, stay out of their way!
- 32:24Operations as a Service: Turn handoffs into self-service
- 34:01Operations as a Service: Popular Uses for SRE
- 39:28But won't Security or Compliance stop you?
- 42:46Reduce Toil
- 43:10Start a book club
- 43:33Recap
related talks
25mSRE Guiding Principles & Transformational Framework
49mWhat SRE Could Be: Systems Reliability Engineering
35mCare and Feeding of SRE
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
19mCrafting an SRE Roadmap for Enterprise Success
22mChallenges in delivering value using SRE, DevSecOps and Value...
18mDeploying Humans at the Edge of SRE
24mBeing Reasonable about SRE