Team topologies and cognitive load
Teams have a limited cognitive load. The shape of a team and the ways it interacts with other teams are designed around that limit, and a platform team exists to reduce the load on the teams that ship product. How work flows is something to design.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Designing or redesigning teams and their boundaries; deciding what a platform team is for.
Where it stops working
It gives a design vocabulary and no formula. The four team types and three interaction modes describe options, and judging which one fits is still the manager's job.
Where the standard uses it
- DE-5Designing how work flowsProcess selection, developer experience, and AI-assisted workflows.
- SV-6Organisational design and leading changeTeam structures, ownership boundaries, reorgs, and transitions.
Sources
- Matthew Skelton and Manuel Pais. Team Topologies: Organizing Business and Technology Teams for Fast Flow. IT Revolution Press, 2019. In the bibliography
Used alongside it
- AI-assisted developer productivity contested
- Aligned autonomy practice
- Conway's law practice
- Developer experience practice
- Goodhart's law practice
- Leading change practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Team topologies and cognitive load. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.team-topologies-and-cognitive-load). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/team-topologies-and-cognitive-load