Team Topologies, 2nd Edition
I keep this at #34 because a modern operating model for structuring technology teams around value flow and cognitive load. I have not finished learning what it asks of me.
The long version
Skelton and Pais present four fundamental team types and three interaction modes for designing software organizations around fast flow. Their key constraint is cognitive load: teams perform better when boundaries, platforms, and collaboration patterns reduce the amount of system complexity each group must carry. It reminds me that the work of making machines useful without letting the work become automatic does not happen only to other people.
Why it is here
It connects organization design to architecture and delivery instead of treating team structure as an HR diagram. The framework helps diagnose handoffs, dependencies, platform friction, and ‘collaboration’ that has quietly become permanent coordination overhead. I want to carry one useful thing from it into the next difficult moment.
How to read it
Map your current teams, the value streams they serve, and their major dependencies. Estimate cognitive load qualitatively, then design one reversible boundary or platform experiment. Avoid renaming teams without changing ownership, interfaces, or incentives. I will mark the places that make me defensive or relieved.
What it taught me
- 01
Stream-aligned teams need sufficient ownership to deliver value independently.
- 02
Platform teams should provide compelling internal products that reduce cognitive load.
- 03
Collaboration, X-as-a-service, and facilitation are distinct, time-bounded interaction modes.
Before and after
What makes it easier
Where it leads
Software Architecture: The Hard Parts
Neal Ford; Mark Richards; Pramod Sadalage; Zhamak Dehghani
Platform Engineering
Camille Fournier; Ian Nowland
More about the author
Matthew Skelton and Manuel Pais are consultants and researchers in sociotechnical systems and organization design. Their Team Topologies framework has become a widely used vocabulary for connecting team boundaries, cognitive load, and software flow.
More by the same hand
Remote Team Interactions Workbook
Matthew Skelton; Manuel Pais