Summary
Team Topologies is an organizational design framework, introduced by Matthew Skelton and Manuel Pais, for structuring teams in software-intensive organizations. It describes four fundamental team types and three modes of interaction between them, with the goal of enabling fast flow and sustainable software delivery.
What is Team Topologies?
The framework defines four team types: stream-aligned teams (aligned to a flow of work or a product), platform teams (providing internal services that reduce cognitive load for stream-aligned teams), enabling teams (helping other teams acquire missing capabilities), and complicated-subsystem teams (owning parts that need deep specialist knowledge). These teams interact through three modes: collaboration, X-as-a-Service, and facilitating.
A central idea is managing team cognitive load and designing clear team boundaries and interactions, rather than letting structure emerge by accident. The model pairs naturally with platform engineering and with delivery-performance measures such as DORA metrics, and it underpins the "enabling team" pattern—where experts temporarily integrate with a team, transfer knowledge, and step back so the team becomes self-sufficient. This makes it especially relevant for organisations adopting new practices, including agentic AI, where empowered, autonomous teams are a prerequisite.
Why is Team Topologies relevant?
- Clear team design: Four team types and three interaction modes replace accidental structure with intent
- Cognitive load focus: Boundaries are drawn to keep each team's load manageable
- Platform synergy: Complements platform engineering and developer-experience efforts
- Enablement model: Provides the structure behind temporary, knowledge-transferring enabling teams