Rethinking measurement for high-performing teams
summary
Combines SPACE and DORA signals with concrete actions: a spike in cycle time reveals PR-review heroes bottleneck and empowering the whole team reduces review latency; quarterly developer NPS uncovers burnout after an IC is pushed into management and a focused role change plus training lowers attrition; restructuring five teams into shared platform ownership creates fixed scope for preventative work and cuts rework. Focus is on metrics that answer a specific question and drive decisions, not optics.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:28Metrics versus strategy
- 4:01Misaligned metrics case studies
- 7:57Developer experience
- 10:49Leading with data
- 14:43Choosing metrics
- 21:06Key takeaways
- 22:33Summary
related talks
41mRethinking Measurement for High-Performing Teams
37mA systems view of developer productivity
44mSPACE: Measuring Developer Productivity
44mEnhancing the Performance of Engineering Teams
43mMeasuring Developer Productivity: The Good, the Bad and the Data
26mEngineering metrics, minus the creepiness
39mDev Team Metrics that Matter
49mProductivity Panel