Team Topologies

Team Topologies: Organizing Business and Technology Teams for Fast Flow by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019, ISBN 978-1942788812)

Team Topologies is a framework for designing organizational structures that optimize for fast, sustainable delivery. Its central argument: team cognitive load and team interaction patterns determine software delivery performance more than individual skill or tooling.

The Four Team Types

Stream-aligned teams: Aligned to a single flow of customer value (product, service, user journey). Empowered to build and deliver end-to-end with minimal handoffs. The primary team type; all other types exist to support them.

Platform teams: Provide internal services that reduce the cognitive load of stream-aligned teams. Build “as-a-service” infrastructure and tools. Treat stream-aligned teams as customers.

Enabling teams: Composed of specialists who temporarily help other teams build capability or overcome obstacles. Do not do the work for the team; they enable the team to do it themselves.

Complicated subsystem teams: Own components requiring deep specialist knowledge (e.g., mathematical models, signal processing). Reduce cognitive load on stream-aligned teams by encapsulating complexity.

The Three Interaction Modes

Collaboration: Two teams work closely together for a defined period to discover solutions. High bandwidth, high cognitive load. Used temporarily when exploring unknown territory.

X-as-a-Service: One team provides, another consumes, with minimal interaction. Low friction, clearly defined API. Default mode for stable platform-consumer relationships.

Facilitation: One team helps another improve capability. The enabling team facilitates; the other team does the work.

Cognitive Load

A central concept: every team has a finite cognitive capacity. When teams are assigned too many responsibilities, contexts, or interactions, quality drops and flow slows. Organizational design should minimize extrinsic cognitive load (coordination, context-switching) so teams can direct capacity to intrinsic load (the actual work).

Relation to AME3 and Conway’s Law

Team Topologies explicitly builds on Conway’s Law and the “Inverse Conway Maneuver”: deliberately structure your teams to match the software architecture you want to produce, rather than letting architecture follow accidental org structure. This aligns directly with AME3’s De-Scaling Cycle and the principle that organizational design and technical architecture are two sides of the same problem.