The four components of high performing teams
summary
Names four concrete levers: mastery, autonomy, purpose and safety, and shows how measurement and process changes move delivery. Uses cycle time from tooling to track progress, drops cycle from 14→1.5 days at one org and 30→5 days at another, abolishes individual story assignment and subtasks, introduces pairing, a skills matrix, Kaizen experiments and putting teams on call. Bugs fall from >100 to <10 and mean time to resolution and on‑call load both drop, proving the fixes work.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:24Debugging teams
- 5:13Purpose
- 6:20Cycle time
- 7:32Safety
- 9:21Mastery pt 1
- 12:22Levelling
- 13:08Skills matrix
- 14:08Change toolkit
- 14:21Give engineers power to control change
- 18:16Reward hard feedback
- 21:52Quality
- 24:46Autonomy pt 2
- 27:14You get what you measure....
- 28:26Questions?
related talks
44mEnhancing the Performance of Engineering Teams
15mBuilding high performing teams
28mBuilding High Performance Engineering Teams
27mLeading a Team with Values
39mThe Key To High-Performing Teams Based On Trust
33m7 habits of a high performing team
44mFundamentals & Practices for getting a High-Performance Team
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems