Adaptive Socio-Technical Systems
summary
Combines Wardley Mapping, Domain-Driven Design and Team Topologies into an “Architecture for Flow” that maps an online‑school value chain, classifies components by evolution stage, splits the monolithic product into bounded contexts (core/support/generic), then forms stream‑aligned and platform teams to run an incremental cloud migration and refactoring. Claims include avoiding the inertia that sank firms (cites >200,000 jobs and ~$220B losses), reducing change coupling and team cognitive load, and achieving faster, safer flow of change through clear ownership and composable services.
AI-written summary · about
chapters (18)
- 0:00Adaptive socio-technical systems
- 1:24Why companies fail to adapt
- 3:12Designing for constant change
- 4:35Wardley Maps for business
- 9:13Understanding external forces
- 12:01Assessing change responsiveness
- 15:36Wardley Maps, DDD, Team Topologies
- 16:41Identifying subdomains
- 20:12Decomposing with bounded contexts
- 22:41Aligning teams and structures
- 28:02Cloud migration efficiency
- 29:31Dynamic re-teaming architecture
- 33:47Expanding internal services
- 36:58Overcoming inertia to change
- 39:05Starting small with adaptation
- 41:32Summary
- 42:13Q&A: Bounded contexts
- 43:17Q&A: Legacy systems
related talks
43mAdaptive Socio-Technical Systems with Architecture for Flow
46mAdaptive Socio-Technical Systems with Architecture for Flow
40mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
15mSAG Expert Interview #07: Socio-Technical Systems for Fast Flow of Change