Team Design Mapping tool
Selects Collaboration, X-as-a-Service, or Facilitating deliberately for each team relationship.
The three interaction modes describe a time-bounded working relationship. Collaboration needs a shared goal and end date, X-as-a-Service a clear interface, and Facilitating a specific capability gap.
Which interaction mode supports this outcome with the least persistent coupling?
Team Topologies Interaction Modes uses assign a team relationship to one of three modes using outcome, knowledge flow, and desired coupling. Assessments remain justified and context-bound.
Bound relationship
Name teams, outcome, and current friction.
Choose mode
Choose Collaboration, X-as-a-Service, or Facilitating from the knowledge flow.
Frame interaction
Agree interface, timebox, responsibilities, and exit criterion.
Review mode
Review flow data and capability, then stop or switch mode.
Review the interaction mode at its end date and switch or stop it.
For recurring or contentious team dependencies with a visible outcome.
interaction mode map with traceable sources, assumptions, and domain decisions.
Owners, dates, and next review for interaction mode map.
Fictional worked example
assign a team relationship to one of three modes using outcome, knowledge flow, and desired coupling as a precise working structure with a fictional example.
| Subject | Team relationship | Mode | Frame | Exit |
|---|---|---|---|---|
| interaction mode mapWorked example | Product ↔ enabling: adopt observability. | Facilitating due to capability gap. | Four weeks; three standard dashboards. | Self-operation achieved; then XaaS. |
The example demonstrates the domain logic of Team Topologies Interaction Modes; worksheets remain blank.
Start with the core question: Which interaction mode supports this outcome with the least persistent coupling?
When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Interfaces are classified by the purpose of the collaboration and the desired closeness. This makes it possible to manage friction, blockers, and unnecessary coordination better from the outset. The picture supports decisions about how teams can best complement each other.
The Interaction Modes concept from Team Topologies distinguishes three clearly defined ways of working together. Collaboration is intense and temporary, X-as-a-Service is a clearly defined ongoing service, and Facilitating is coaching by an enabling team. The mapping is often used alongside Team API and visualized as a heat map.
Explain the three modes with examples. Avoid mixed forms per pair; choose explicitly. Keep the mapping readable as a heat map.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Plan Team Topologies Interaction Modes around its domain steps and the concrete decision question.
To be confirmed
To be confirmed
Establish and review the practice Time: 60 minutes
Complete this worksheet on paper or in your own document during the work.
| Subject | Team A · team B · outcome | Collaboration · XaaS · Facilitating + reason | Timebox · interface · responsibilities | Criterion · next mode · review |
|---|---|---|---|---|
| interaction mode map |
Enter only real input, sources, and decisions.
Team Topologies: Team Interaction Modeling
Expected artifact: relationship profile
relationship profile · source · uncertainty · next decision
Entry:
...
Expected artifact: mode decision
mode decision · source · uncertainty · next decision
Entry:
...
Expected artifact: interaction contract
interaction contract · source · uncertainty · next decision
Entry:
...
Expected artifact: review decision
review decision · source · uncertainty · next decision
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/team-topologies-interaction-modes/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of Team Topologies Interaction Modes, choose Team API when you want to clearly document a team's mode of collaboration.
Clarifies purpose, roles, and working rules in a charter that makes collaboration tangible and verifiable.
Clarifies starting point, opportunities, and strategic options by framing the scope and target state, capturing the seven elements, and deriving change actions.
Surfaces stakeholder expectations, clusters conflicts, and turns them into concrete agreements.
Arranges components, relationships, and flows into a system picture that exposes dependencies and levers.
Jointly formulates valid working rules and clarifies how the team handles expectations, conflicts, and reviews.
