Optimizing for a fast flow of value with adaptive, socio-technical systems
summary
Claims that combining Wardley Mapping + Domain-Driven Design + Team Topologies produces an executable "architecture for flow" and shows how to cut blockers to change. Demonstrates mapping an online-school monolith into bounded contexts, spinning a platform team, replatforming infrastructure to cloud, then forming stream-aligned teams; outcome: reduced handovers, lower cognitive load and faster delivery. Recommends team size 5–9 people, uses event storming and refactoring patterns, and reports audience recognition of Wardley mapping at about 75%.
AI-written summary · about
chapters (11)
- 0:00Introduction to adaptive systems
- 2:11Building the right thing right
- 7:50Wardley Mapping basics
- 15:21Optimizing flow of change
- 23:38Closing efficiency gaps
- 24:00Team Topologies overview
- 31:48Internal platform design
- 36:46Learning organizations
- 40:41Practical transition steps
- 45:40Summary and future changes
- 47:50Q&A session
related talks
40mAdaptive Socio-Technical Systems with Architecture for Flow
46mAdaptive Socio-Technical Systems with Architecture for Flow
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
43mAdaptive Socio-Technical Systems with Architecture for Flow
45mAdaptive Socio-Technical Systems
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
43mAdaptive Socio-Technical Systems with Architecture for Flow
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies