Architect(ure) as Enabler of Organization’s Flow of Change
summary
Argues organizations must evolve their architecture topology across nested scopes (teams, products, product groups, portfolios) rather than treat architecture as accidental; describes concrete moves used at bol.com over five years: create a tech‑leads network, place architects as enabling architects who coach teams instead of gatekeep, and adopt an advice process (anyone may decide after seeking affected parties and experts). Reports the tech‑leads pattern reduces decision bottlenecks and the advice process speeds decentralized decisions when trust and transparency exist.
AI-written summary · about
chapters (11)
- 0:00Introduction to flow
- 1:03Challenges in modern orgs
- 4:34Architecture as an enabler
- 7:14Architecture topologies
- 11:41Purposeful autonomy
- 17:05Holistic architecture models
- 20:28Evolutionary architecture
- 25:11Enabling teams
- 30:21Facilitating collective decisions
- 33:40Advice process
- 37:47Building a learning culture
related talks
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
45mTowards Architecture Organization Topologies
46mArchitecture Transformation Challenges
45mArchitecture: The Stuff That's Hard to Change
01h 02mThinking Like an Architect
46mTHE too MANY FACES OF ARCHITECTURE
46mTowards Sustainable Learning, Designing and Decision-making
44mWhen your boss decides to have an architecture team…