Psychologically safe reliability management
summary
Case study of driving an observability platform across a multi‑product org during General Election Preparation shows the technical work landed but adoption stalls because of top‑down and bottom‑up buy‑in failures, org structure mismatches, and unclear processes around accountability. A blameless post‑mortem surfaces that SLOs and error‑budget policies and dedicated on‑call shifts helped clarify expectations, while missing feedback loops and culture gaps prevent scale. The concrete claim: the platform is built and useful, but organizational fixes — not more tech — determine whether it succeeds.
AI-written summary · about
chapters (10)
- 0:00Psychological safety basics
- 2:25Trauma-informed leadership
- 5:32Chronic issues and safety
- 11:04Feedback loops for prevention
- 14:37Accountability and service level objectives
- 15:40On-call pain points
- 18:06Proactive monitoring
- 19:51Reactive failure approaches
- 23:01Leadership accountability
- 27:15Final thoughts
related talks
32mPsychologically Safe Reliability Management
15mWhy psychological safety is the key to sustainable product development
22mA Dual Approach to Accountability Engineering
24mOperationalizing Observability: The Invisible Parts
35mIs My Thing Reliable? Adventures in Driving Consistency of...
22mLeading software teams with context (visibility)
36mPsychological Safety for Your Platform Engineering
34mExploring Disconnects between Reliability Practitioners and Management