Architecture and Organization
summary
Examples from Avvo, Spotify, Adobe and Microsoft show organizational shape driving software and vice versa, with concrete outcomes: a monolith causing weeks-long feature delivery, Spotify reorganizing into feature teams and ending up with 800 developers, 800 services to cut dependencies, and experiments that pair architecture and reporting lines to raise throughput. Tactics include queuing work, treating internal teams like vendors, shifting ownership to a platform team when multiple teams share code, and deliberately using the reverse Conway maneuver to align org chart and desired architecture.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:10Conway's Law origins
- 5:22Homomorphic force explanation
- 13:03Mel Conway's nuanced view
- 15:50Is Conway's Law a real law?
- 16:52Conway Jujitsu concept
- 17:13Adobe Revel case study
- 22:08Spotify's organizational shift
- 26:41Avo's transformation
- 28:47Practical Conway's Law tips
- 31:14Reverse Conway maneuver
- 32:39Harvard Business School study
- 33:42Summary and takeaways
- 34:04Q&A session
related talks
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
35mOrganization: A Tool for Software Architects
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
47mArchitecture and Corporate Operating Structure: a Cloud Puzzle
43mArchitect(ure) as Enabler of Organization’s Flow of Change
16mEveryone architect!
46mScaling Agile in your Organization with the Spotify Model
44mWhen your boss decides to have an architecture team…