Career & Leadership › Technical Leadership

Team Topologies

Stream-aligned, platform, enabling and complicated-subsystem teams.

Team Topologies is a framework for organizing teams around the flow of value and the interactions needed between them. It describes stream-aligned teams, platform teams, enabling teams, and complicated-subsystem teams, along with interaction modes such as collaboration, facilitation, and providing a service.

The framework can help expose why work is slow. A product team may depend on a platform team for every deployment change, or a specialist subsystem may be owned by a team without enough expertise. Naming the interaction can clarify whether the relationship should be temporary collaboration, supported enablement, or a stable service contract.

Do not copy a diagram from the framework and assume it fits your organization. Team boundaries affect communication, incentives, and technical architecture; reorganizing without changing interfaces may simply move queues. Team design also cannot remove every dependency or replace clear ownership.

Backend boundaries might separate product services from shared infrastructure. Frontend organization can clarify who owns cross-cutting interaction work. Data organization may distinguish pipeline ownership from central platform support. Choose interaction modes deliberately and revisit them as workload shifts. Make the cost of coordination visible so staffing and planning reflect it. Adjust the interaction mode when the workload changes. Name owners for each interface you keep.

Backend, frontend, and data engineers can map how work crosses their system boundaries and where teams wait for one another. Revisit the model as products and skills change, and include the cost of operating new team boundaries. See inverse Conway maneuver, platform thinking, and team cognitive load.