Team Interaction Modes

Three defined ways teams interact: collaboration (two teams work closely for a time, high bandwidth but blurred boundaries), x-as-a-service (one team consumes what another provides with minimal coordination), and facilitating (one team helps or mentors another). Each interaction should be a deliberate choice.

Why it Matters

Unmanaged interaction between teams is a major source of delay and friction. Making the mode explicit, and time-bounding collaboration in particular, keeps boundaries legible and flow fast.

Signals

• Teams know which mode they are in and why; collaboration is temporary and purposeful.
• Anti-signals: permanent collaboration that erodes ownership; expecting service-like reliability from a team you actually need to collaborate with.

Benefits

Clear expectations between teams, reduced coordination overhead, and boundaries that stay understandable.

Risks

Defaulting to collaboration everywhere is expensive and blurs ownership. Treating something as a service before it is stable enough to consume that way leads to broken dependencies.

Tensions

Collaboration enables discovery but costs autonomy; x-as-a-service maximizes autonomy but demands a mature, well-defined interface. Choosing a mode too early or too late both hurt.

Examples

Two teams collaborate intensively while building a new integration, then shift to x-as-a-service once the interface stabilizes. An enabling team facilitates another until it gains a capability, then steps back.