How platform teams create resilient organisations
summary
Runs an observability platform team of five people supporting about 500 users across digital and tech. Uses incidents as high-value learning events, joins responses and post-incident reviews, and applies the STELLA framing to decode system behaviour. Builds transparency with a biweekly community of practice plus public health Slack channels where cross-team answers emerge. Prioritises interrupts as customer discovery, exploits temporary slack to deliver improvements, tracks logins as a “can fail by” metric and warns against over-relying on MTTR/DORA.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:42Ed’s journey into resilience engineering
- 2:59Platform team definitions
- 5:39How expertise builds resilience
- 6:47What expertises does platform team need
- 8:30Learning from incidents
- 11:56Building relationships
- 12:47Using interrupts to grow your platform team
- 15:10Building Observability community of practice
- 19:16Exploiting slack for progress as a group
- 21:55Key takeaways
- 22:38Success metrics
- 26:00Wrap up
related talks
41mPlatform teams: Applying Lean practices to reduce their Operational workload
31mPlatform Health: A team model of platform evolution
33mBeyond Monitoring: The Rise of Observability Platform
47mPlatform Team Structures and Concerns
15mImportance of Observability in Platform Engineering
31mEscaping operations hell
22mRaise a Production System:Making on-call human-scale w/ Observability & Trust
33mEffective observability in microservice architectures