Adaptive Socio-Technical Systems with Architecture for Flow
summary
Combines Wardley Mapping + Domain‑Driven Design + Team Topologies to cut change lead time by removing architectural and team blockers: map user‑anchored value chains, spot evolution gaps (build vs buy), decompose a monolithic online‑school into bounded contexts, form stream‑aligned, platform and enabling teams, and run a reverse‑Conway, incremental cloud migration. Platform starts as docs/templates then self‑service APIs; enabling teams upskill stream teams; outcome is faster, lower‑cognitive‑load delivery and clearer ownership for continuous feedback.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:52Challenges of building systems
- 2:55Starting from the user perspective
- 4:35Understanding the value chain
- 5:58Mapping the current state
- 7:33Assessing current flow of change
- 13:30Assessing efficiency gaps
- 14:49Architecture for flow
- 23:504 team types of Team Topologies
- 26:053 interaction modes
- 27:13Architecture for flow
- 32:04Platform value chain
- 34:35Upskilling teams on missing capabilities
- 36:04A mix of mindsets per team
- 37:55Unlocking blockers to flow
- 38:10How to transition?
- 38:20Reverse Conway maneuver
- 39:03Evolution of Team Topologies
- 40:15Architecture for flow
- 40:25Summary
- 41:28Looking ahead
- 42:08Resources
- 42:20Outro
related talks
40mAdaptive 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
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