Building Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
summary
Architecture mirrors org charts so reorganizing people reshapes systems, and trying the inverse Conway maneuver in a large enterprise usually fails. Use domain-driven design and eventstorming to map bounded contexts (example: train/platform/shop/passenger vs customer) and create a unified language. Practical moves include giving teams cross-functional ownership (biz/dev/sec/ops), provisioning Terraform repos and platform tooling per domain, and avoiding heavy top-down frameworks like SAFe; the claim: these steps increase communication bandwidth and deployment autonomy.
AI-written summary · about
chapters (7)
- 0:00Welcome to Conway's law
- 3:13Conway's law impact
- 6:46Inverse Conway maneuver
- 9:37Domain driven design
- 13:56Bounded contexts alignment
- 15:42Principles for resilient teams
- 18:10Q&A
related talks
50mConway's Law: When Best Practices Are Not Enough
35mOrganization: A Tool for Software Architects
41mArchitecture and Organization
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
45mTowards Architecture Organization Topologies
54mThe value of Org Topologies in the era of DIY-frameworks
47mArchitecture and Corporate Operating Structure: a Cloud Puzzle