Team Topologies
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."
Related Terms
Bus Factor
Bus factor = 1 means one person leaving (or getting hit by a bus) destroys the project. They're the only one who knows how the payment system works.
Conway's Law
Conway's Law says your software architecture will mirror your org chart. Three teams? You'll end up with three services. Frontend team and backend team?
Platform Engineering
Platform engineering is building the roads so application developers can just drive.
Platform Team
A Platform Team builds internal tools and infrastructure so product teams can ship faster.