Team Topologies

Team Topologies is a must-read for anyone involved in building software at scale. It moves away from the “everyone should talk to everyone” fallacy and introduces a pragmatic, team-first approach to organizational design. By focusing on cognitive load and the flow of value, Skelton and Pais provide a clear vocabulary for discussing team structures and their interactions.

The core message of this book is beautifully illustrated on devopstopologies.com  . It describes patterns and anti-patterns of DevOps-focused teams, emphasizing that organizational design and software architecture are inextricably linked.

Core Ideas & Patterns

The Four Fundamental Team Types

To reduce cognitive load and clarify responsibilities, every team should fall into one of these four categories:

1. Stream-aligned Team: The primary team type. Cross-functional and aligned to a continuous flow of business value (e.g., a specific product or user journey). They take end-to-end ownership - “you build it, you run it.”
2. Enabling Team: A group of specialists who help other teams overcome obstacles and bridge knowledge gaps. They focus on mentoring rather than direct feature delivery.
3. Complicated Subsystem Team: Tasked with managing components requiring deep, specialized technical expertise that would overwhelm a stream-aligned team.
4. Platform Team: Provides internal tools and services to reduce the cognitive load of stream-aligned teams. They treat the platform as a product, focusing on the “Thinnest Viable Platform” (TVP).

The Three Interaction Modes

To manage communication and prevent bottlenecks, teams should interact in specific ways:

• Collaboration: Working closely together for a defined period to discover or innovate. High-bandwidth but temporary.
• X-as-a-Service: One team provides a service that another consumes with minimal interaction, promoting autonomy.
• Facilitating: One team helps another clear impediments or adopt new practices (the primary mode for Enabling teams).

Key Principles

• Conway’s Law : “Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.”
• Cognitive Load: The amount of information a team must process. If it exceeds capacity, flow stops.
• Reverse Conway Maneuver: Intentionally designing team structures to achieve the desired architecture.
• Thinnest Viable Platform (TVP): The minimum platform necessary to support stream-aligned teams without unnecessary bloat.