We can’t all be Shaq: why it’s time for the SRE hero to pass the ball and how to make it happen
summary
Argues that relying on a handful of rescue engineers creates burnout and masks missing systems, offers three concrete steps: codify incident runbooks by thinking out loud in the incident channel, swap hero for incident commander to coach and rotate responders, and audit tooling—adopt SLOs observability and an incident management tool plus regular retrospectives. Gives practical examples of what to write down, how to hand off responsibility, and mentions FireHydrant as context for incident management.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 1:25Personal journey to incident insights
- 3:31Problem with SRE hero culture
- 6:42Hero culture bottlenecks
- 9:49Why hero model doesn’t scale
- 10:52Breaking heroism cycle
- 12:18Formalizing incident response
- 13:23Empowering others to lead
- 14:04Improving on-call and observability
- 15:28From reactive to strategic incidents
- 16:10Closing
related talks
15mSustainable Incident Management for happy SRE teams
30mHow Did Things Go Right? Learning More from Incidents
28mRevolutionizing Incident Response
30mHow to have an operational incident a crash course
35mIf I Can Do It on an Ambulance, You Can Do It in an Office: Scalable Incident
37mManaging incidents in microservices
28mHow to Do SRE When You Have No SRE
43mLearning from Firefighters to Improve Systems Reliability