The Good, the Bad and the Very Ugly in Structuring IT Organizations
summary
Argues that organizational change follows two poles — fill‑the‑gap designs vs problem‑driven evolution — and that each restructure seeds future issues so iterative cycles matter. Uses Kanban/Lean ideas, Team Topologies as a lens, and organizational archaeology to read snapshots. Gives concrete failures: copying Spotify’s model breaks within 1.27 nanoseconds, centralizing regional IT took 3–4 years to work then lost learned knowledge, 170 country IT fragments and temporary DevOps teams morph into permanent bottlenecks.
AI-written summary · about
chapters (28)
- 0:00Introduction and welcome
- 1:07Personal journey and insights
- 2:01Two cultures of organizational change
- 4:28Organizational archaeology explained
- 6:58Scope beyond software lifecycle
- 8:02Organizational evolution cycle
- 9:05Why structure matters
- 10:13Conway's hypothesis revisited
- 12:47Team Topologies overview
- 15:13Complex adaptive systems defined
- 16:37Nonlinear behavior in systems
- 19:09Feedback loops in organizations
- 20:58System archetypes and patterns
- 23:28Reinforcing loops in IT releases
- 26:15Learning from Spotify's model
- 28:45Historical evolution of structures
- 32:19Modern approaches to agility
- 33:23Startup scaling challenges
- 34:50Agile transformation pitfalls
- 36:36Resistance to change management
- 37:00Database team restructuring
- 38:48Vendor collaboration issues
- 39:35Global IT resource centralization
- 42:52Knowledge loss in restructuring
- 43:57System selection and knowledge transfer
- 45:50Complex systems require experimentation
- 47:15Incremental change and learning
- 47:57Focus on people and collaboration
related talks
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
39mDesigning an Organization, Lessons from scaling technical orgs
44mInsights on How Team Topologies Drive Organizational Success
54mThe value of Org Topologies in the era of DIY-frameworks
28mOrganizing for Outcomes
51mOrganisation Refactoring and Culture Hacking : Lessons from Software
23mIts transformation! But, is it though?
43mThe Sociotechnical Organisation Design Playbook