liveBook · Manning

Interaction mode

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

An interaction mode is a Team Topologies classification describing how teams interact to achieve a goal or exchange capabilities.

An interaction mode classifies how teams relate while achieving goals or exchanging capabilities. Team Topologies defines three modes and recommends choosing among them according to alignment needs, cognitive load, and changing context. section 11.2 section 11.2.2

Use the mode that best balances team alignment with independent delivery:

  • Collaboration: two teams work toward a shared outcome through synchronized work, shared rituals, joint decisions, and frequent communication. It supports close alignment but carries high cognitive load. section 11.2.2
  • X-as-a-service: one team consumes another team's capabilities, such as an API, with limited synchronization after onboarding, feature requests, or occasional support. section 11.2.2
  • Facilitating: one team temporarily helps another achieve its goal, including urgent support or upskilling, without making the relationship permanent. section 11.2.2

Treat interaction modes as evolutionary choices rather than fixed structures. Excessive collaboration, context switching, slower delivery, or heavy coordination can signal that boundaries or modes need reassessment, although practices and leadership may also be contributing. section 11.4.1 section 11.6

Switching from collaboration to service

Two teams may collaborate closely while clarifying responsibilities, then move toward X-as-a-service when stable boundaries and capabilities make repeated synchronization unnecessary. section 11.2.2 section 11.6

Figure 11.5 The three interaction modes of Team Topologies

Compare the three interaction modes and their relationship patterns in one visual model. section 11.2.2

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines three modes, explains their coordination costs, and connects them to organizational sensing without prescribing implementation details.
Examples
Uses shared rituals, API consumption, urgent deadline support, upskilling, and gradual movement from collaboration to X-as-a-service.
What it assumes
Uses Team Topologies principles and team types as the surrounding organizational-design vocabulary.
What you can do after
Diagnose costly team interactions and choose or evolve collaboration, X-as-a-service, or facilitating relationships.
How it connects
Connects team types, cognitive load, team topology, organizational sensing, and Conway's law.

Also explained in

Compare how 2 books explain interaction mode →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.