Knowledge
Knowledge HubConcepts and strategic researchGlossaryDefinitions across six domainsFrameworksStructured strategy methodsTopicsConnected subject areasLibrary
PlaybooksPractical strategy guidesBooksBooks and long-form researchOperator VaultMember resources and toolkits
Explore Discover, the Knowledge Hub, playbooks, and the Operator Vault.
Glossary
Team topology
Team topology, used here in the sense of Matthew Skelton and Manuel Pais’s Team Topologies approach, is a way to organize software and digital delivery with four team types — stream-aligned, platform, enabling, and complicated-subsystem — and three interaction modes — collaboration, X-as-a-Service, and facilitating — so cognitive load and dependencies stay manageable as systems scale.
Why it matters
Scaling delivery often fails when every team is expected to be fully autonomous while sharing tangled platforms and unclear handoffs. Team Topologies gives leaders a specific vocabulary for matching team purpose to architecture and for choosing how teams should interact.
The canonical vocabulary term is singular (“Team topology”), but the named four team types and three interaction modes are components of the Skelton and Pais framework — not interchangeable synonyms for the whole approach, and not a claim that every team-organization design is Team Topologies.
It is a design aid inside organizational design and operating-model work, not a full enterprise operating model by itself.
Example (enterprise): A scale-up with twelve feature teams all blocked on the same authentication codebase introduces a platform team owning identity as a service, plus a short-lived enabling team coaching two stream-aligned teams on observability. Interaction modes are published so “help” requests do not silently become permanent dual-track ownership.
Mechanisms
- Classify teams using the Team Topologies types: stream-aligned, platform, enabling, and complicated-subsystem.
- Set Team Topologies interaction modes — collaboration, X-as-a-Service, or facilitating — to reduce accidental coupling.
- Revisit topology when cognitive load, dependency pain, or architecture boundaries change.
Boundaries
- Team topology / Team Topologies ≠ every possible team-organization design; other org-design approaches exist.
- Stream-aligned teams and interaction modes are components of Team Topologies, not synonyms for the whole approach.
- Team Topologies ≠ org-wide operating model; it focuses on team types and interactions for delivery systems.
- Team Topologies ≠ a mandatory four-team headcount formula; types are patterns for managing cognitive load.
Related topics
None linked yet.
Related concepts & frameworks
Further research
No related resources yet.