Team Topologies: Teams Built for Flow, Not the Org Chart

Stanislav Khalup examines Team Topologies through his platform experience. The book is treated as a model for organizing fast delivery from a DevOps perspective, not a comprehensive guide to life inside teams.

The discussion begins with Conway's Law: architecture reproduces actual communication, not the formal organization chart. The reverse Conway maneuver designs autonomous teams and their interfaces first. Dunbar's number, Tuckman's model, and cognitive load explain why a team should remain small and own a clear flow of value.

The episode centers on four topologies: stream-aligned, complicated subsystem, platform, and enabling teams. The model distinguishes a component, an internal platform product, and temporary expert assistance. Boundaries are practical: they reduce dependencies, localize knowledge, and let a product team build, deliver, and operate its outcome independently.

The three interaction modes—collaboration, X-as-a-Service, and facilitating—carry different costs. Close collaboration helps teams overcome shared uncertainty briefly, but should not become permanent. The closing assessment covers change triggers and the book's limits: a useful model sits beside shallow cases and limited treatment of quality, security, and life inside a team.