Team Topologies

Overview

Team Topologies (2019) by Matthew Skelton and Manuel Pais provides a practical framework for organizing technical teams based on how software actually gets built. The core insight: team structure should follow the software architecture (Conway's Law), and organizations should deliberately design team interactions to optimize for fast flow of change. The framework defines exactly four fundamental team types (Stream-aligned, Enabling, Complicated Subsystem, Platform) and three interaction modes (Collaboration, X-as-a-Service, Facilitating). This constraint forces clarity and reduces cognitive load, enabling teams to own bounded contexts end-to-end.

When to Use

• Reorganizing engineering teams for faster delivery and reduced handoffs
• Diagnosing why software architecture doesn't match business needs
• Reducing cognitive load on teams overwhelmed by too many responsibilities
• Planning platform team investments and internal developer experience
• Breaking monoliths into microservices with team boundaries that match
• Scaling organizations while maintaining autonomy and flow
• Applying Conway's Law deliberately rather than accidentally
• Transitioning from project-based to product-based team structures

The Process