The Sociotechnical Path to High-Performing Teams
summary
Argues that the gap between elite and average teams comes from sociotechnical feedback loops, not raw engineering skill, and recommends tracking DORA metrics plus a fifth metric: alerts outside work hours. Prescribes CI/CD as continuous deployment with a pipeline that deploys to kibble -> dogfood -> production with hour gates, instrumentation and observability-driven development, on-call rotation of ~6–7 people with on-call weeks free of product work and about two-to-three wakeups per year as a reasonable target.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:50Teams
- 11:00How to build high-performing teams?
- 14:40Insidious loop
- 15:30Virtuous loop
- 21:51ODD
- 25:19A dirty little secret
- 29:16Outro
related talks
44mEnhancing the Performance of Engineering Teams
25mCapabilities for Building High-performing Technology Teams
22mLeading software teams with context (visibility)
31mThe Secrets of High Performance- What the Data Says
52mSecrets of High Performing Teams: Science Edition
37mFrozen DevOps? Team Topologies Comes to the Rescue!
33m7 habits of a high performing team
39mThe Secrets of High Performing Technology Organizations