Adaptive Socio-Technical Systems with Architecture for Flow
summary
Argues that combining Wardley Mapping, Domain-Driven Design and Team Topologies lets teams turn a monolithic “big ball of mud” into modular bounded contexts with stream-aligned and platform teams, anti-corruption layers and open host service APIs; proposes a cloud rep‑platforming path: platform team replaces infra with cloud services, stream teams refactor into smaller modules, reduce handovers, lower team cognitive load and remove delivery bottlenecks. Example is an online‑school case assembled from projects and is not yet fully realized; warns inertia costs (Nokia >90% share loss).
AI-written summary · about
chapters (13)
- 0:00The importance of adaptability
- 1:26Mapping business landscapes
- 4:40Climatic patterns of change
- 7:03Identifying system constraints
- 10:43Architecting for flow
- 13:27Domain driven design
- 17:36Context maps for integration
- 24:07Team topologies for success
- 26:20Team interaction models
- 29:00Mindsets and evolution
- 30:57Transitioning to cloud
- 34:16Overcoming organizational inertia
- 37:24Q&A and closing thoughts
related talks
46mAdaptive Socio-Technical Systems with Architecture for Flow
40mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
45mAdaptive Socio-Technical Systems
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies