Autonomous teams require great managers
summary
Claim: true autonomy only works when managers set frames coach skills and run the system. Evidence: three required elements — team manager system — and a case where multiple microservices in C# Java Kotlin Go create microservice language sprawl, blocking cross‑team help. Fixes applied: a golden path for service tech, weekly cross‑org prioritization, tighter alignment (the painful dead Smiley phase). Leadership needs move from expert/achiever to catalyst; autonomy without that infrastructure proves damaging rather than liberating.
AI-written summary · about
chapters (12)
- 0:00Introduction and speakers
- 2:44Defining autonomous teams
- 5:33Core elements for success
- 7:56Common challenges
- 11:01Balancing autonomy and alignment
- 15:13Leadership styles
- 18:44Leadership as a skill
- 21:38Accountability and transparency
- 25:07Warning signs for teams
- 28:36Evaluating the investment
- 30:29Call to action
- 33:56Conclusion and Q&A
related talks
53mAutonomous teams require great managers
41mAutonomous teams require great technical leaders
47mUnlock your autonomy. Improve your software design
21mAutonomous Teams
43mAutonomy, is that what we really want?
18mJourney towards autonomous teams | A coach's toolkit
34mAutonomous Teams in Technology Organisations
47mAutonomy – From Buzzword to Business Value