Wiring for Flow
summary
Argues that organizations behave like networks and that borrowing the internet’s hourglass model — an spanning layer that enforces a common protocol — lets diverse teams interoperate without central control. Shows concrete artifacts that act as spanning layers: API specs, Amazon six‑pagers, A3s, value‑stream charters, platform abstractions and LLMs (Gen) that collapse complexity into prompts. Claims these protocols as enabling constraints reduce cognitive load, let teams be self‑directed, and measurably speed coordination.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:24Internet origins and complexity
- 3:54Wiring the winning organization
- 7:25Protocols and spanning layers
- 10:12Examples of spanning layers
- 12:20Focus on organizational layer three
- 13:46Self-directed teams and information flow
- 14:08Closing and resources
related talks
43mAdaptive Socio-Technical Systems with Architecture for Flow
50mHow Flow Works and other Curiosities
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
42mHow Flow Works and other curiosities
43mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
46mAdaptive Socio-Technical Systems with Architecture for Flow