A Fresh Look at Operational Debt
summary
Defines operational debt = work to fix process gaps that present risk and links it to measurable impact on time‑to‑restore, using runbooks and API contracts as concrete examples (hundreds of runbooks vs tens of contracts). Introduces a toil pile that quantifies recurring interest paid by on‑call teams, sizes remediation as t‑shirt projects, and plots them on a quadrant (cost to fix vs toil reduced) to prioritize work, create a risk‑rated backlog, and surface unknown unknowns.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:40Technical debt is insufficient
- 1:09I'm thinking about
- 2:34Examples
- 3:01Operational debt characteristics
- 3:56Runbooks
- 5:11Prior definitions 8
- 5:42Debt summary
- 6:44The toil pile
- 8:28Your SREs have unique resource constraints
- 9:23Fowler's quadrants for operational debt
- 10:51Practical applications ... backlogs
- 12:01Practical applications ... toil reduction
- 12:34Practical applications ... unknown unknowns
- 14:11Practical applications ... unknown ur
related talks
28mManaging Technical Debt at Scale
05mBalancing Technical Debt and Modernisation in DevOps
27mUnveiling the Business Value of Technical Debt
34mThe Technical Debt Trap
25mDemystifying Technical Debt
39mThe cash value of technical debt - How to scare your boss into doing the right thing
35mTechnical Debt. A guide for developers and IT managers
31mOperations Reform: Tom Sawyer-ing Your Way to Operational Excellence