Team Topologies

Team Topologies is a framework by Matthew Skelton and Manuel Pais for organizing technology teams around the flow of change. Rather than designing teams to match technical layers (frontend, backend, database), it starts from how work flows through the organization and designs team boundaries to minimize cognitive load and maximize autonomy.

The core insight is that team structure is architecture. Per Conway’s Law, the software a group produces will mirror its communication patterns. Team Topologies treats this as a design tool rather than an inevitability — you shape the teams to get the architecture you want.

Key Building Blocks

Four Team Types — Every team in the organization maps to one of four types: Stream-aligned, Platform, Enabling, or Complicated-subsystem. Stream-aligned teams own end-to-end delivery of a slice of value. The other three types exist to reduce the cognitive load on stream-aligned teams.

Three Team Interaction Modes — Teams interact via Collaboration, X-as-a-Service, or Facilitating. These modes are deliberately chosen and evolved over time, not left to chance.

When to Reach for It

Team Topologies is most useful when:

• Teams are slow and it’s not clear why
• Reorgs keep happening but nothing improves
• Dependencies between teams dominate the work
• You want to align team structure to flow and value streams