Your Systems Aren't Stuck - Your Teams Are
summary
Claims that outages and slow delivery stem from leadership patterns not tech, backed by DigitalOcean-era examples: a Perl monolith with one on-call expert, a DBaaS/MySQL team blocking a Compute team, hiring failures solved by splitting job specs, and repeated incidents from single-person knowledge. Presents four lightweight fixes: ownership maps, cognitive-load checks, a leadership shift from doer to coach, and weekly impact audits. Cites Forrester numbers: 54% more bugs per dev, 861% more code churn.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:25Leadership failure modes
- 6:34Hero culture risks
- 13:14Local vs global optimization
- 17:48Making decisions without clear ownership
- 20:36Tactical managers
- 26:55Psychological safety
- 29:21DevOps leadership loop
- 31:50Cognitive load check
- 34:39From solving to empowering
- 37:08Impact audit
- 40:24AI won't fix leadership
- 40:45Call to action
related talks
46mLeading Distributed Teams
13mTen Ways to Doom Your DevSecOps
54mFrozen DevOps, The Not so technical Last Mile
17mDevOps Leadership in practice. True stories
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
37mFrozen DevOps? Team Topologies Comes to the Rescue!
52mUnderstanding UnHealthy Syndromes of Software Delivery
43mSoftware Eats Culture For Breakfast