Skip to content

Team Topologies

Medium — good to knowGeneral Dev

ELI5 - The Vibe Check

Team Topologies is a framework for organizing engineering teams around four basic shapes: stream-aligned teams that own a piece of the product end to end, platform teams that build internal tools for everyone else, enabling teams that coach others through a temporary skill gap, and complicated-subsystem teams for the one component that genuinely needs a specialist. The core idea is that your org chart is basically a preview of your software's architecture, so if the teams are a mess, the architecture will be too.

Real Talk

Team Topologies is an organizational design framework, from the 2019 book of the same name by Matthew Skelton and Manuel Pais, that defines four fundamental team types, stream-aligned, platform, enabling, and complicated-subsystem, and three interaction modes, collaboration, X-as-a-Service, and facilitating, for structuring engineering organizations to minimize cognitive load and cross-team coordination overhead. It formalizes and extends Conway's Law by treating team boundaries as a deliberate architectural decision rather than an organizational afterthought.

When You'll Hear This

"We restructured around Team Topologies, platform teams now serve the stream-aligned ones as a service." / "That reorg basically just applied Team Topologies without ever saying the name out loud."

Made with passive-aggressive love by manoga.digital. Powered by Claude.