Enabling teams for happier and more productive engineers
summary
Adopts the Team Topologies pattern and an inverse Conway maneuver to reduce developer cognitive load, dedicating 3% of engineering capacity to a transversal enabling team called Hubble. Focuses on CI/CD runbooks, incident resolution and documentation, builds a sandbox web app and synthetic monitoring using Splunk to pilot changes. Results: 30% more monthly deployments, ~33% fewer problematic deployments, and team engagement rising from 84% to 94%. Emphasis is on coaching not doing the work, then scaling successful pilots into team backlogs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:00About Tim
- 8:33The results
- 10:30Team architectures
- 15:37Two approaches to enabling teams
- 17:48Five steps to enable teams
- 21:00What to enable
- 22:13Who to hire
- 24:48Enabling
- 29:30Building trust
- 34:58Staying flexible
related talks
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
46mBuilding memorable software engineering teams
32mPanel discussion: The journey to building effective engineering teams
32mSynergy: Building Strong Engineering Teams
18mAgile leadership and technical mastery, a harmonious alliance
30mThe Sociotechnical Path to High-Performing Teams
39mTransforming ivory tower architecture to enabling teams
44mTeams That Propel People Forward