Just Enough Reliability

on YouTube ↗28m

" summary

Argues for prioritising a small set of critical user journeys mapped to concrete endpoints, replacing noisy sitewide alerts (example: 3% errors for 5m) with alerts only on those flows. Implements a weekly ops ratchet: descope alerts, fix CUJ-related issues within a week with boring fixes (retries, pay down errors), record deferred work in a risk register spreadsheet, then add more CUJs as all chosen flows turn green to decide whether to hire or invest in bigger tech.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:08Startups and minimal reliability
3. 3:36Overcomplicating technology
4. 5:44Engineers and complexity
5. 7:49Reliability engineer challenges
6. 10:19Critical User Journeys
7. 13:27CUJs and business value
8. 15:55Alerts for critical flows
9. 18:22Ratchet method for reliability
10. 22:57Scaling reliability efforts
11. 24:00Q&A

" related talks

• 47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a SuccessfulBlake Bisset, Jonah Horowitz · LISA17
• 28mAlerts don't suck, YOUR alerts suckLeon Adato · SREday London 2024
• 39mActionable ObservabilityLesley Cordero · NDC London 2024
• 31mBetter Monitoring for Humans: The CASE MethodCory Watson · DevOpsDays Raleigh 2019
• 52mPersistent SRE Antipatterns: Pitfalls On the...Blake Bisset, Jonah Horowitz · SREcon17 Europe/Middle East/Africa
• 19mSensory Friendly Monitoring: Keeping the Noise DownQuintessence Anx · DevOpsDays Detroit 2019
• 28mFixing On-Call When Nobody Thinks It's (Too) BrokenTony Lykke · SREcon19 Americas
• 27mSensory Friendly Monitoring: Keeping the Noise DownQuintessence Anx · DevOpsDays Boston 2018