Towards Architecture Organization Topologies for Sustainable Fast Flow of Change
summary
Presents a concrete model called Architecture Organization Topologies and shows how one retailer moves from centralised “Ivory Tower” architects to enabling teams and cross-team product groups, formalising roles like product tech lead. Describes breaking a monolith into microservices (600+ services), scaling from ~30 to 100+ teams, then 150+, and investing in platform capabilities. Claims decentralised decision making and coaching architects speed delivery, reduce coordination pain, and make multi-team changes feasible rather than requiring ten teams to touch one front-end field.
AI-written summary · about
chapters (15)
- 0:00Introduction to agility
- 2:24Learning from Amsterdam
- 5:13Definition of learning
- 6:42Embracing environmental change
- 9:25The Cynefin framework
- 12:08Complexity and Conway's Law
- 15:17Shifting to new models
- 19:03Architecture topologies
- 21:47Case study: Ball.com
- 23:53Scaling with DevOps
- 26:10Challenges in scaling
- 28:45Restructuring for flow
- 32:00Evolving architecture roles
- 34:29Conclusion
- 35:47Q&A session
related talks
45mTowards Architecture Organization Topologies
43mArchitect(ure) as Enabler of Organization’s Flow of Change
46mTowards Sustainable Learning, Designing and Decision-making
16mEveryone architect!
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
40mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
54mThe value of Org Topologies in the era of DIY-frameworks