Defined Interaction Modes
Defined Interaction Modes refer to the structured ways in which teams within an organisation communicate and collaborate to achieve their objectives. These modes are explicitly defined to optimise interaction and minimise friction in the workflow.
Goal
The goal of defining interaction modes is to minimise the overhead involved in cross-team communication.
Context
If you need to collaborate with another team in order to deliver your work, this dependency becomes an excuse for why you haven't achieved your outcomes. In ZeroBlockers, we want to remove all of the blockers so we need to ensure that collaboration between teams is as frictionless as possible.
Interaction Modes
ZeroBlockers builds on the three interaction modes from Team Topologies by Matthew Skelton and Manuel Pais — Collaboration, X-as-a-Service, and Facilitating — and adds a fourth: Aligning. The reasoning for the addition is in the section below the table.
| Modes | Description | Best Suited For |
|---|---|---|
| Collaboration | Teams work closely together on a temporary basis, sharing knowledge and skills to solve complex problems or to innovate. | Situations requiring rapid innovation or problem-solving where expertise from multiple teams is needed. |
| X-as-a-Service | One team provides a service (e.g., a software service or a platform) that other teams use to build their own solutions more efficiently. | Stable, well-understood domains where the service can be clearly defined and consumed without ongoing collaboration. |
| Facilitating | One team coaches another team to become more capable. Recurring, bounded, and aimed at its own obsolescence — the coached team becomes self-sufficient. | When a team needs to build new capability or overcome a specific challenge. Enabling Teams operate exclusively in this mode. |
| Aligning | A directing team provides vision, strategy and objectives to the teams it directs, without specifying how to achieve them. Recurring, bounded, and permanent — strategic context never stops being needed. | When a team has decision authority over another team. Product Teams use this mode with Stream Teams. Ecosystem Teams use it with Product, Internal Product and Enabling Teams. |
Aligning and Facilitating — Why ZeroBlockers Treats Them Separately
Skelton and Pais have argued that the Facilitating mode can cover what ZeroBlockers calls Aligning. From a pure interaction-cost perspective they are right: both modes are recurring, bounded and low-overhead per session, and both involve one team providing context or guidance to another. ZeroBlockers uses a separate label because two structural differences matter at design time:
- Authority asymmetry. A Product Team has decision rights over the Stream Team — it can change strategy, structure, funding, OKRs, even disband the team. An Enabling Team has no such authority. The directed-by relationship is different from the coached-by relationship even when the per-session cost is similar.
- Permanence. A good Facilitating relationship ends. The Enabling Team's success is measured by the Stream Team needing less help over time. A Product Team's relationship with a Stream Team does not end and is not supposed to. Strategic context is always needed.
Conflating the two modes produces two implementation mistakes that show up consistently in the field:
- Enabling Teams drift into directing — running stream-team reviews, setting their priorities, conferring authority they were never given.
- Product Teams drift into coaching — staying in permanent collaboration with stream teams instead of governing them, never holding them accountable for outcomes.
The separate mode label is a design heuristic that catches both mistakes earlier. It is a deliberate divergence from Team Topologies for the specific case where a team taxonomy includes directing layers above the delivery layer.
Inputs
| Artifact | Description |
|---|---|
| Stream Team Charter | A clear definition of the scope of work for each Stream Team. |
Outputs
| Artifact | Description | Benefits |
|---|---|---|
| API Specifications | Establishing well-defined interfaces between different systems or services managed by separate teams. |
|
Rationale
API contracts, which are an example of the X-as-a-Service mode, let teams interact without any per-interaction overhead. When work genuinely requires closer cooperation a project can be set up for the duration of the work, applying the Collaboration mode for a bounded period. Facilitating mode is used by Enabling Teams to coach Stream Teams towards self-sufficiency. Aligning mode is used by Product Teams to provide strategic context to the Stream Teams they direct, and by Ecosystem Teams to provide portfolio context to the Product, Internal Product and Enabling Teams beneath them.
Anti-patterns
- Failing to specify mode: Not defining interaction modes can lead to confusion and inefficiency in cross-team collaboration.
- Over-specification: Defining interaction modes in excessive detail can lead to rigidity, stifling creativity and agility.