Adaptive Socio-Technical Systems with Architecture for Flow
summary
Claims a practical method: combine Wardley Mapping, Domain-Driven Design and Team Topologies to turn a monolithic online-school into modular bounded contexts, migrate on-prem infra to cloud, and reduce handovers by forming platform teams and stream-aligned teams. Shows concrete patterns used — anti-corruption layer and Open Host Service — and an incremental team-first transition: platform team replatforms, stream teams refactor, enabling teams coach. Reports outcomes as lower cognitive load, fewer delivery bottlenecks and closed efficiency gaps; slides and a book are available for details.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:43What do these companies have in common?
- 2:32Evolving a legacy system
- 4:37Wardley Map of the current state
- 5:14External forces impacting the landscape
- 7:33Assessing responsiveness to change
- 11:29Optimizing flow of change
- 12:28Architecture for flow
- 24:524 team types of team topologies
- 27:413 interaction modes
- 31:41How to transition?
- 32:09Evolution of team topologies
- 35:57Value chain
- 40:32Why should be change?
- 43:00Start small
- 44:09Takeaways
- 45:23Outro
related talks
43mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
45mAdaptive Socio-Technical Systems
40mAdaptive Socio-Technical Systems with Architecture for Flow
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies