Complete firstBounded subject
The scope and purpose of Team Topologies Interaction Modes are stated as a concrete question.
Without scope, interaction mode map becomes arbitrary.
Method guideTeam Design
Team Topologies Interaction Modes
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
TimeHalf day
ParticipantsTeam-Leads plus Architecture
FormatWorkshop
MaturityEmerging
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant perspectives
Team boundaries and APIs, concrete shared outcomes, dependency and flow data and domain decision makers are available.
Without these perspectives, central claims in interaction mode map remain unsupported.
02
Preparation
What needs to be ready before start
Materials
Team boundaries and APIs, concrete shared outcomes, dependency and flow data, shared workspace, source links, and decision log.
People / roles
Representatives of both teams · team leads · enabling team if needed
Pre-read
Collect Team boundaries and APIs, concrete shared outcomes, dependency and flow data in advance and mark open assumptions.
Time needed
60 minutes
Setup
Prepare assign a team relationship to one of three modes using outcome, knowledge flow, and desired coupling visibly and calibrate assessment terms before starting.
03
Core question
The one question this method answers
Which interaction mode supports this outcome with the least persistent coupling?
04
Flow
Phases with goal, actions, output and pitfall
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.
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. |
1. Team relationship
- interaction mode map
- Product ↔ enabling: adopt observability.
2. Mode
- interaction mode map
- Facilitating due to capability gap.
3. Frame
- interaction mode map
- Four weeks; three standard dashboards.
4. Exit
- interaction mode map
- Self-operation achieved; then XaaS.
The example demonstrates the domain logic of Team Topologies Interaction Modes; worksheets remain blank.
- 1
Bound relationship
Bound relationship
Goal
Produce relationship profile so the core question “Which interaction mode supports this outcome with the least persistent coupling?” can be answered with stronger support.
Inputs for this step
- Team boundaries and APIs
- concrete shared outcomes
- dependency and flow data
Actions
- Name teams, outcome, and current friction.
- Record source, rationale, and open uncertainty directly in relationship profile.
Output
relationship profile
relationship profile · source · uncertainty · next decision
Quality check
Is a concrete outcome named rather than generic cooperation?
Pitfall
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface. Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Timing: 10–20 minutes
- 2
Choose mode
Choose mode
Goal
Produce mode decision so the core question “Which interaction mode supports this outcome with the least persistent coupling?” can be answered with stronger support.
Inputs for this step
- relationship profile
- concrete shared outcomes
- dependency and flow data
Actions
- Choose Collaboration, X-as-a-Service, or Facilitating from the knowledge flow.
- Record source, rationale, and open uncertainty directly in mode decision.
Output
mode decision
mode decision · source · uncertainty · next decision
Quality check
Does the mode fit the type of uncertainty?
Pitfall
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface. Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Timing: 10–20 minutes
- 3
Frame interaction
Frame interaction
Goal
Produce interaction contract so the core question “Which interaction mode supports this outcome with the least persistent coupling?” can be answered with stronger support.
Inputs for this step
- mode decision
- concrete shared outcomes
- dependency and flow data
Actions
- Agree interface, timebox, responsibilities, and exit criterion.
- Record source, rationale, and open uncertainty directly in interaction contract.
Output
interaction contract
interaction contract · source · uncertainty · next decision
Quality check
Are start, end, and expected capability clear?
Pitfall
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface. Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Timing: 10–20 minutes
- 4
Review mode
Review mode
Goal
Produce review decision so the core question “Which interaction mode supports this outcome with the least persistent coupling?” can be answered with stronger support.
Inputs for this step
- interaction contract
- concrete shared outcomes
- dependency and flow data
Actions
- Review flow data and capability, then stop or switch mode.
- Record source, rationale, and open uncertainty directly in review decision.
Output
review decision
review decision · source · uncertainty · next decision
Quality check
Does the next mode prevent unnecessary coupling?
Pitfall
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface. Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Timing: 10–20 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned interaction mode map with date, sources, owners, and next review.
Versioning / ownership
Retain date, source, assumption state, and decision for every version of interaction mode map.
Tool alternatives
- interaction mode map as board or document
- Source and evidence register
- Decision and action log
team-topologies-interaction-modes-working-template.md
Plan Team Topologies Interaction Modes around its domain steps and the concrete decision question.
Team Topologies Interaction Modes: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Establish and review the practice Time: 60 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Team boundaries and APIs, concrete shared outcomes, dependency and flow data, shared workspace, source links, and decision log.
- Roles: Representatives of both teams · team leads · enabling team if needed
- Advance information: Collect Team boundaries and APIs, concrete shared outcomes, dependency and flow data in advance and mark open assumptions.
- Overall time needed: 60 minutes
- Setup: Prepare assign a team relationship to one of three modes using outcome, knowledge flow, and desired coupling visibly and calibrate assessment terms before starting.
Prepare for the work steps
Bound relationship: Bound relationship
- Team boundaries and APIs
- concrete shared outcomes
- dependency and flow data
Choose mode: Choose mode
- relationship profile
- concrete shared outcomes
- dependency and flow data
Frame interaction: Frame interaction
- mode decision
- concrete shared outcomes
- dependency and flow data
Review mode: Review mode
- interaction contract
- concrete shared outcomes
- dependency and flow data
interaction mode map
| Subject | Team A · team B · outcome | Collaboration · XaaS · Facilitating + reason | Timebox · interface · responsibilities | Criterion · next mode · review |
|---|---|---|---|---|
| interaction mode map |
- interaction mode map: Worked example
Enter only real input, sources, and decisions.
Team Topologies: Team Interaction Modeling
Bound relationship: Bound relationship
Expected artifact: relationship profile
relationship profile · source · uncertainty · next decision
Entry:
...
- Is a concrete outcome named rather than generic cooperation?
Choose mode: Choose mode
Expected artifact: mode decision
mode decision · source · uncertainty · next decision
Entry:
...
- Does the mode fit the type of uncertainty?
Frame interaction: Frame interaction
Expected artifact: interaction contract
interaction contract · source · uncertainty · next decision
Entry:
...
- Are start, end, and expected capability clear?
Review mode: Review mode
Expected artifact: review decision
review decision · source · uncertainty · next decision
Entry:
...
- Does the next mode prevent unnecessary coupling?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/team-topologies-interaction-modes/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
team-topologies-interaction-modes-beispiel.md
Concrete filled scenario, fictional example
Product team ↔ enabling team: Facilitating for four weeks, goal: the team can operate three standard dashboards itself. Then platform team → product team as X-as-a-Service through a documented telemetry API. No permanent collaboration pairing.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Bound relationshipCollaboration becomes the permanent default or X-as-a-Service lacks a usable interface.View in phase
- Choose modeCollaboration becomes the permanent default or X-as-a-Service lacks a usable interface.View in phase
- Frame interactionCollaboration becomes the permanent default or X-as-a-Service lacks a usable interface.View in phase
- Review modeCollaboration becomes the permanent default or X-as-a-Service lacks a usable interface.View in phase
Trap
Bound relationship
Symptom
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface.
What to do
Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Trap
Choose mode
Symptom
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface.
What to do
Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Trap
Frame interaction
Symptom
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface.
What to do
Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
Trap
Review mode
Symptom
Collaboration becomes the permanent default or X-as-a-Service lacks a usable interface.
What to do
Re-establish outcome, knowledge gap, coupling need, and end date, then adjust the mode.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
interaction mode map answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.