Lean Product Development Through SLOs
summary
Argues that making SLOs the product backbone turns vague requests into measurable outcomes: revisits core use cases to define SLIs/SLOs, builds a lightweight pipeline that translates technical changes into business events, and wires a Grafana-style dashboard broadcasting SLOs so teams see error budgets. Uses concrete targets (example: one business day 80% over a rolling 30‑day window), shows the number tradeoffs (adding nines is 10× harder), and reports it reduces assumptions, focuses work, and actually frees capacity for new features.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:14Lean SLO takeaways
- 3:02Landing zones for SLOs
- 4:45Lean theory and waste
- 8:36SLIs, SLOs, SLAs defined
- 11:06Negotiating SLOs with consumers
- 13:13SLOs as SMART goals
- 16:45Balancing nines and capacity
- 18:11SLOs guide engineering
- 19:38Avoiding Schrodinger’s SLA
- 21:01SLOs in team workflows
- 22:45Error budgets and expectations
- 24:52Renegotiating SLOs
- 25:54SLOs as team language
- 26:36Key takeaways and closing
related talks
06ma pint sized introduction to SLO
31m9 Things You Should Do When Starting to Use SLOs
57mSLI and SLO for the Business: Monitoring Quality Across 200+ Products
30mMetrics for good, not evil
28mEngineering Data Reliably Using SLO Theory
01h 06mPepperoni, Puppets, and Priorities: Demystifying SLAs, SLOs, and SLIs
22mLook Ma, No Metrics: A Quest Towards Extracting SLOs
05mSLOs: You’re missing the point!