Adaptive Socio-Technical Systems with Architecture for Flow
summary
Combines Wardley Mapping, Domain-Driven Design and Team Topologies into an “Architecture for Flow” canvas that starts from current team structure, maps user needs to a Wardley value chain (example: online school), classifies subdomains as core/supporting/generic, defines bounded contexts to modularize a monolith, then assigns stream-aligned, platform and enabling teams so platform self‑service cuts handovers and wait time. Claims measurable gains: faster end‑to‑end change flow, focused investment on core differentiators, and an incremental transition using the reverse Conway maneuver.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:32Challenges of building systems
- 2:19Architecture for flow canvas
- 3:10Analyzing current teams
- 3:43Assessing the current flow of change
- 8:45Visualizing the current landscape
- 13:28Categorizing the problem space
- 17:10Modularizing the solution space
- 19:31Visualizing the future landscape
- 22:06Deriving future team organization
- 35:10Next steps: How to transition?
- 35:36Next steps: Reverse Conway maneuver
- 37:51Architecture for flow
- 38:14Summary
- 39:22Resources
- 39:35Outro
related talks
43mAdaptive Socio-Technical Systems with Architecture for Flow
45mAdaptive Socio-Technical Systems
46mAdaptive 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
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies