Cross-team dependencies do not show up in the org chart. They show up in lead time. When a delivery requires coordination from five teams, the deadline is set by the slowest one. Every hand-off between teams carries a cost of context loss, wait time and communication rework that does not appear in any sprint report. It appears as lead time that grows without explanation and as velocity that falls while headcount rises.
Subcapability 01 of 04 · High Performance Teams
Team Topologies
Four team types and three interaction modes that apply Conway's Law intentionally, eliminate invisible coordination cost and multiply delivery throughput without adding headcount.
What is at stake
The team does not deliver slowly because it is weak. It delivers slowly because every change requires coordinating teams with their own queues, their own priorities and their own approval models. The cost of dependency does not appear in the budget. It appears in lead time that never closes and in market windows that pass.
What it is, in practice
How we work
Value flow and dependency mapping
We map the actual delivery flow for each product or journey, identify the hand-off points between teams and calculate the coordination cost of each dependency, making visible where the current topology blocks velocity with a number.
Topology design by value flow
We design the team structure based on the delivery flow the business needs, applying the four team types and three interaction modes to reduce required coordination to the minimum without losing systemic coherence.
Reverse Conway Maneuver
We design the team topology before designing the software, so the architecture that emerges reflects the expected value flow. The org chart becomes a system design input, not an accidental consequence of historical hierarchy.
Exit criteria for enabling teams
We define the explicit criterion for when the enabling team ends its engagement with each stream-aligned team, including the maturity indicator that confirms capability has been transferred, preventing the enabling team from becoming a permanent dependency.
Topology KPIs for C-Level
We install indicators that reveal topology health to the board: number of hand-offs per end-to-end delivery, percentage of stream-aligned teams over total, and deployment frequency as a direct signal that the value flow is unobstructed.
Measurable gains
What changes in the result when this subcapability matures.
Number of hand-offs per end-to-end delivery
Topology redesigned by value flow reduces the number of teams that need to coordinate for each delivery. Every eliminated hand-off reduces wait time, context loss and communication cost that previously had no address.
Deployment frequency for stream-aligned teams
Teams with end-to-end ownership and no external approval dependency deliver at a frequency that functional teams cannot match. Deployment frequency is the most direct signal that the value flow is unobstructed.
Wait time between request and platform capability delivery
A platform team with an X-as-a-Service interface and a defined scope responds with predictable time. The product team stops waiting in the infrastructure queue and starts consuming a service with an SLA.
Coordination cost as a percentage of engineering time
Alignment meetings, dependency confirmation emails and scope clarification sessions have measurable cost in engineering hours. Topology that reduces required coordination returns that time to roadmap delivery.
Frequently asked questions
What distinguishes Team Topologies from a traditional reorganization?
A traditional reorg rediscovers hierarchy. Team Topologies redesigns the delivery flow. The difference is the criterion: instead of grouping people by specialty or by product, the topology groups them by the value flow each team needs to produce with the lowest possible coordination cost. The result is structure that reflects what the business wants to deliver, not how the company grew historically.
What is the Reverse Conway Maneuver in practice?
Conway's Law says any organization that designs a system produces a design that copies the communication structure of that organization. The Reverse Conway Maneuver inverts the order: first define how the system should be structured to serve the business value flow, and from that, organize teams so that architecture emerges naturally. Teams produce the software that reflects their communication structure. Design the structure first.
When to use Collaboration and when to use X-as-a-Service as an interaction mode?
Collaboration is intensive and expensive in communication overhead. It serves for bounded periods of joint discovery, when two teams need to learn about each other's domain before defining the interface between them. X-as-a-Service serves when the interface is established and the consuming team can operate autonomously. Using Collaboration indefinitely where X-as-a-Service would work is one of the most common ways to create coordination overhead without realizing it.
How does the enabling team avoid becoming a permanent dependency?
By defining exit criteria before entering. The enabling team starts with a specific capability elevation objective and an indicator that confirms when the stream-aligned team can operate without support. When the indicator is reached, the enabling team leaves or moves to another stream. An enabling team without exit criteria becomes permanent technical support, which is the opposite of what the model proposes.
How many teams are needed for each type?
It depends on the product portfolio and the number of distinct value flows the company operates. A common starting point is one stream-aligned team per user journey or autonomous product domain, one platform team per set of shared technical capabilities, and enabling teams activated as needed to raise specific capabilities. There is no fixed ratio. The criterion is the value flow and the coordination cost of each configuration.
Other subcapabilities in this capability
Ownership & Autonomy
End-to-end ownership with autonomy calibrated by alignment that replaces one-off heroism with predictable results and eliminates the hand-off where invisible quality cost accumulates.
Cognitive Load Management
Three cognitive load types applied to team design that reduce extraneous load, free space for real work and turn an overloaded team into one that delivers predictably.
Engineering Metrics & DORA
The four engineering metrics that correlate with organizational performance and shift management from narrative to data, connecting delivery velocity to financial results.
Want clarity on where to invest first?
A complete technology capability assessment with an evolution roadmap connected to financial result.