Matthew Skelton & Manuel Pais
A practical language for designing teams around the flow of work.
Why it’s here
Good teams are not a staffing chart. They are an interaction design: deliberate boundaries, cognitive load, and a clear path for change to travel.
Ideas worth keeping
- Optimize for fast flow, not maximum utilization.
- Keep team cognitive load sustainable.
- Make interaction modes explicit and temporary where possible.
Read next
The Phoenix Project for the delivery problem, then Wiring the Winning Organization for the leadership architecture.
Lenses: Technology · Work & Systems · Leadership