Mean Time to WTF: Why Developer Experience Frameworks Belong in Your Incident...
summary
Argues that applying SPACE and DORA to SRE work reveals measurable operational friction and that a new metric, Mean Time to WTF, (time from alert to “I understand what’s happening”) surfaces brittleness before MTTR rises. Cites Night Capital’s $460M loss in 45 minutes and studies: $1.52T technical debt, 40% of dev budgets on avoidable rework, 68% productivity → ~$300B GDP loss. Recommends practical steps: add a friction log/retro field, time MTWF on incidents, run on‑call surveys, and publish visibility reports (error rates by team) to drive fixes.
AI-written summary · about
chapters (9)
- 0:00Developer experience intro
- 3:50Friction as reliability risk
- 7:43AI and system friction
- 14:50Measuring DX with SPACE/DORA
- 22:41Mean Time to WTF
- 26:54Business case for less friction
- 33:38Data-driven org change
- 37:14Six actionable steps to improve developer experience today
- 39:22Q&A
related talks
17mMake Work Not Suck Improving the Developer Experience
20mEvangelizing the SRE mindset
39mDev Team Metrics that Matter
44mEnhancing the Performance of Engineering Teams
27mTales from the VOID: The Scary Truth about Incident Metrics
24mThe Metrics Question: Evolving Past MTTX
44mDeveloper Joy – How great teams get s%*t done
27mWhat Makes a Great Developer Experience?