The Three Team Interaction Modes

Definition

Beyond deciding what a team's purpose is, Team Topologies argues the relationship between any two teams should also be named and deliberate, chosen from three modes: Collaboration (working closely together, discovering something neither side yet knows how to specify), X-as-a-Service (one team consumes what another provides through a clean, low-interaction interface), and Facilitating (one team helps another overcome a gap, typically temporarily). Picking the wrong mode — defaulting to heavy collaboration where a clean service boundary would do, for instance — is treated as a design error, not a neutral outcome.

In the Book

Step 5, "Identify as-is and to-be team interaction modes," names the three modes directly (Collaboration, X-as-a-Service, Facilitating) as the target vocabulary for describing how teams currently work together and how they should work together going forward, again pointing to the shapes.teamtopologies.com visual reference. Step 6 builds on this by instructing that inter-team collaboration itself should be explicitly guided and limited to two purposes: informing and guiding the development of internal Platform and Complicated-Subsystem components, and driving rapid discovery/learning at points of technological, organizational, or situational uncertainty. As with the rest of this condensed source, no specific example pairing of two named teams and their chosen mode is given — the three-mode vocabulary and its two sanctioned uses for open-ended Collaboration are the grounded content.

Why It Matters

Treating "how do these two units interact" as a small, named choice — rather than letting relationships drift into permanent ad hoc collaboration or permanent hands-off service — makes coordination overhead visible and deliberately budgeted. Collaboration is powerful but expensive (it consumes both sides' attention and cognitive load), so reserving it for genuine discovery and defaulting to a service or facilitation relationship elsewhere is a transferable move for any organization managing many interdependent units, not just software teams.