The Team as a High-Load System
summary
Maps common software-development practices to team management by treating a team as a high-load system. Uses developer tools and approaches — such as monitoring, metrics, incident-style postmortems, and decomposition of responsibilities — to solve organizational problems without relying on formal management training.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:04Overloaded team lead
- 5:07Exception man role
- 9:10450 blocker bugs
- 10:58Spaghetti processes
- 11:41Bug or feature decision
- 17:11Backlog improvements
- 20:53Team dashboards
- 24:26Fighting blockers
- 25:28Single-point expertise risks
- 27:38Software-team analogy
- 28:46Q&A
related talks
15mBuilding high performing teams
48mHow to scale not only IT systems but also IT teams
59mDesign mistakes in high-load projects
49mBuilding a High-Performance Team is Everyone's Job
44mFundamentals & Practices for getting a High-Performance Team
11mLeading software teams with systems thinking
30mThe Sociotechnical Path to High-Performing Teams
44mHighly Available, Distributed & Resilient Software... Team