Skip to content
Knowledge beta

Three Team Interaction Modes

Team Topologies Organizational Design

How teams interact matters as much as how they're structured. Get the interaction mode wrong and even well-designed teams will slow each other down.

Teams don’t just exist in isolation; how they interact matters as much as how they’re structured. The Team Topologies framework defines three deliberate interaction modes, chosen intentionally and evolved over time, not left to chance.

Collaboration

Two or more teams work closely together for a limited time to solve complex problems. This is high-bandwidth, iterative work, often used for innovation, discovery, new product development, or critical dependencies. Collaboration is expensive; it increases cognitive load for both teams. Use it when the problem is genuinely novel and neither team can solve it alone, then evolve to a less coupled mode.

X-as-a-Service

One team provides a service (e.g., platform, API, or reusable capability) to another with clear interfaces and expectations. This minimizes cognitive load for consumers and enables self-service. The consuming team doesn’t need to understand how the service works; they just use it. This is the target mode for most mature team interactions.

Facilitating

A team with specialized knowledge (e.g., enabling or coaching teams) helps another team improve skills, adopt new practices or tools, or overcome a challenge. This is often temporary and designed to build long-term capability, not create a dependency.

Evolving Interactions

Interaction modes aren’t static. A new platform capability typically starts in Collaboration mode (tight feedback loops, co-discovery), shifts to Facilitating as teams onboard, and matures into X-as-a-Service once the offering is stable and self-serve. The key insight is that you choose the mode for each relationship and revisit it as the situation evolves.

Resources