interaction modes · team topologies

collaboration, x-as-a-service, facilitating. the three ways teams work together — and the cost of picking wrong.

three ways teams interact

teams don't work in isolation. the question is always how they work together, and for how long. team topologies says there are three modes, and picking the wrong one is one of the most expensive mistakes you can make.

collaboration two teams work closely on a shared goal, blurring boundaries temporarily to figure something out. high bandwidth, high cost. the right mode when you're discovering an interface or exploring unfamiliar territory. the wrong mode when you already know what the interface is.
x-as-a-service one team consumes the other's output through a stable, documented interface. no meetings needed. the default mode for mature platform relationships and for any complicated-subsystem team that's done its job. the most scalable; the most boring in the best way.
facilitating one team coaches another past a capability gap, then leaves. short, goal-bound, skills-transfer. the native mode of an enabling team. if it outlasts its purpose, it morphs into one of the other two modes (or into bureaucracy).

the rule: default to x-as-a-service

collaboration is expensive. it's meetings, handoffs, shared decision-making. every hour two teams spend collaborating is an hour neither team spent shipping. it's the right tool when you genuinely don't know the interface yet — but the minute you do, you should be moving toward x-as-a-service.

the way to tell if you've stayed in collaboration too long: if someone on each team could predict what the other team will say in every meeting, the interface is stable. stop meeting. publish the contract. let the consumer self-serve.

the cost signal. a platform that needs ongoing collaboration to use isn't a platform — it's a bottleneck. the better the platform, the less it appears in anyone else's calendar. if your platform team is in every consumer's retro, it has failed its contract, however hard they're working.

pick the right mode

six scenarios

for each situation, pick the interaction mode you'd recommend. watch for the subtle shifts — the right answer depends on where each team is in its lifecycle.

modes change over time

the same two teams will typically pass through all three modes as their relationship matures. a new platform capability starts in collaboration (the platform team co-designs with an early adopter), graduates to facilitating (the platform coaches the next few teams onto it), and settles into x-as-a-service (the rest of the org self-serves from documentation). lesson seven covers this evolution in depth; for now, just notice that the mode isn't fixed.

next: cognitive load — the hidden constraint that decides whether any topology can even work.