A Dual Approach to Accountability Engineering
summary
Presents a concrete decision model called accountability engineering that bifurcates projects into direct (high control, visible wins) and diffuse (long‑game culture change) accountability, arguing SRE must own engineering deliverables and build incentives for partner teams. Describes tools actually built and used: a global incident response tool that auto‑populates postmortems and tracks AIs, a service catalog in Backstage with routing and ownership metadata, a SLO publishing pipeline (PromQL copy/paste into page views), templated Google Doc operational reviews, PagerDuty health checks, Grafana JPEGs and scorecards. Development spans about three years and cultural shifts take three–five years; the service catalog and SLO tooling report strong adoption.
AI-written summary · about
chapters (9)
- 0:00Accountability engineering intro
- 3:39Traditional SRE problems
- 5:47Accountability engineering principles
- 9:21Accountability engineering heuristic
- 12:30Bifurcating projects for accountability
- 15:16Feedback loop and recognition
- 16:41Diffuse accountability culture
- 18:05Reddit tools and systems
- 21:16Summary
related talks
19mCrafting an SRE Roadmap for Enterprise Success
23mSite Reliability Evangelism: Practice Start-up within an Established...
24mIgniting Sociotechnical Systems with Reliability Advocacy
25mSRE Guiding Principles & Transformational Framework
29mThe Curious SRE: Cultivating a Mindset for System Resilience
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
31mConfessions of an SRE Manager
45m“Disorganizing” Your SRE Organization