Team Topologies: Organising Technology Teams for Flow
Team Topologies (from the book by Matthew Skelton and Manuel Pais) provides a practical model for organising technology teams to maximise flow of value to users and minimise coordination overhead. It defines four team types and three interaction modes — a vocabulary and framework for intentional team design.
Four Team Types
- Stream-aligned teams: Aligned to a flow of work from a segment of the business domain. Most teams should be stream-aligned — they own end-to-end delivery for their domain and have everything they need to move without dependency on other teams.
- Platform teams: Provide internal services that reduce cognitive load for stream-aligned teams. The platform team builds and maintains self-service capabilities — cloud infrastructure, CI/CD, observability tooling.
- Enabling teams: Help stream-aligned teams acquire capabilities they need — not by doing work for them, but by coaching and building capability. Then they move on.
- Complicated-subsystem teams: Own components requiring deep specialist knowledge — algorithms, specialist databases, regulatory compliance systems.
Three Interaction Modes
- Collaboration: Two teams work closely together for a defined period to discover new approaches. Temporary and intense.
- X-as-a-Service: One team provides a well-defined service to another. Minimal interaction — just consume the service.
- Facilitating: An enabling team helps a stream-aligned team. One-directional, knowledge transfer focused.