Transforming ivory tower architecture to enabling teams
summary
Centralized architecture teams convert into enabling team roles by coaching stream-aligned squads, using Team Topologies as the framework, pairing and mob-programming to transfer skills, and running pilots for about half a year before full enablement. Goal is to shift macro rules to mandatory guards while moving most micro-architecture decisions into teams and to dissolve the enabler in ~3–4 years. Watch for concrete blockers: salary-band and works‑council rules, HR role changes, and measure effectiveness with team retrospectives and anonymous satisfaction polls rather than top-down metrics.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:37Working modes for Architects
- 3:57Agile crossfunctional teams
- 6:21Cognitive load for teams
- 8:36Team topologies
- 12:10Team bottleneck
- 16:27The role of the enabler
- 20:27Removing the enabling team
- 21:10Stakeholders
- 23:18Senior Management
- 27:00Showstoppers
- 28:33Giving instructions
- 29:56Heckler
- 30:36Be sensible
- 31:05Questions
related talks
40mEnabling teams for happier and more productive engineers
46mTechnical Leadership and Empowered Teams
29mCultivating architecture
43mArchitect(ure) as Enabler of Organization’s Flow of Change
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
47mFrameworks for Shaping High-Performing Teams
46mTowards Sustainable Learning, Designing and Decision-making
27mSoftware Architects and Autonomous Teams