methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method sessionHalf day (4 h)WorkshopInteraction-Heat-Map

Session: Team Topologies Interaction Modes

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with Team-Leads plus Architecture. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Interaction-Heat-Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Introduce modes with examples

    20 min

    Explain three modes. Collaboration: two teams work closely together temporarily (for example new feature, architecture change). X-as-a-Service: one team consumes clearly defined service of another. Facilitating: enabling team supports stream-aligned team through coaching, durably bounded. Hint: If modes are unclear, participants choose wrong. Bring concrete own examples, not abstract theory.

    FacilitatorInteraction-Heat-Map
  2. 2

    Phase 2: Map current interaction

    60-90 min

    Mark current state per team pair. Which mode runs today. If unclear, mark. Mark friction points with red note. Hint: Honestly describe what runs, not what ideally should run. Mismatch between target and actual is common source of friction.

    FacilitatorVereinbarungen pro Paar
  3. 3

    Phase 3: Discuss target modes

    60-90 min

    Define target mode per team pair. Discuss rationale. For change between actual and target, think transition plan (for example Collaboration -> X-as-a-Service through service buildup). Hint: Avoid mixed forms. Exactly one mode per pair. Anyone saying "sometimes Collaboration, sometimes Service" has not understood mode. Conscious choice is core.

    FacilitatorInteraction-Heat-Map
  4. 4

    Phase 4: Agreements and heatmap

    30-45 min

    Complete heatmap with target modes. Document agreement per pair (what mode means concretely, which communication channels, SLA). Transition plan for changes. Hint: Heatmap without agreements is diagram. Concrete agreement per pair with example workflow. Agreement should be 1-2 sentences, not abstract definition.

    OwnerVereinbarungen pro Paar
  5. 5

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerInteraction-Heat-Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Team Topologies Interaction Modes

Goal

Artifact: Interaction-Heat-Map

Working Question

Which interaction mode fits per team pair, and how do we agree modes bindingly to reduce interface friction?

Context

Team list with main responsibilities (Stream-Aligned, Platform, Enabling, Complicated-Subsystem); current interface relationships; known frictions or escalations; planned platform initiatives.

Setup

  • Format: Method session
  • Duration: Half day (4 h)
  • Mode: Workshop
  • Participants: One facilitator with Team Topologies experience; team leads of all involved teams; architecture lead or engineering director as sponsor; scribe for agreements.
  • Owner: One facilitator with Team Topologies experience
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Interaction-Heat-Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with heatmap template (team list vertically and horizontally, cells for interaction modes); definitions of three modes with examples; list of current interface problems; pens with three colors for modes.

Preparation

Heatmap with teams in rows and columns. Colors per mode: blue=Collaboration (intensive, temporary), green=X-as-a-Service (clearly defined service, durable), yellow=Facilitating (coaching, enabling). Definitions visible.

Agenda

  1. Phase 1: Introduce modes with examples (20 min) Owner: Facilitator Action: Explain three modes. Collaboration: two teams work closely together temporarily (for example new feature, architecture change). X-as-a-Service: one team consumes clearly defined service of another. Facilitating: enabling team supports stream-aligned team through coaching, durably bounded. Hint: If modes are unclear, participants choose wrong. Bring concrete own examples, not abstract theory. Output: Interaction-Heat-Map

  2. Phase 2: Map current interaction (60-90 min) Owner: Facilitator Action: Mark current state per team pair. Which mode runs today. If unclear, mark. Mark friction points with red note. Hint: Honestly describe what runs, not what ideally should run. Mismatch between target and actual is common source of friction. Output: Vereinbarungen pro Paar

  3. Phase 3: Discuss target modes (60-90 min) Owner: Facilitator Action: Define target mode per team pair. Discuss rationale. For change between actual and target, think transition plan (for example Collaboration -> X-as-a-Service through service buildup). Hint: Avoid mixed forms. Exactly one mode per pair. Anyone saying "sometimes Collaboration, sometimes Service" has not understood mode. Conscious choice is core. Output: Interaction-Heat-Map

  4. Phase 4: Agreements and heatmap (30-45 min) Owner: Owner Action: Complete heatmap with target modes. Document agreement per pair (what mode means concretely, which communication channels, SLA). Transition plan for changes. Hint: Heatmap without agreements is diagram. Concrete agreement per pair with example workflow. Agreement should be 1-2 sentences, not abstract definition. Output: Vereinbarungen pro Paar

  5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Interaction-Heat-Map

Closeout

  • Update result artifact: Interaction-Heat-Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Interaction-Heat-Map: Team Topologies Interaction Modes

Working Question

Which interaction mode fits per team pair, and how do we agree modes bindingly to reduce interface friction?

Context

Team list with main responsibilities (Stream-Aligned, Platform, Enabling, Complicated-Subsystem); current interface relationships; known frictions or escalations; planned platform initiatives.

Participants

  • Owner: One facilitator with Team Topologies experience
  • Participants: One facilitator with Team Topologies experience; team leads of all involved teams; architecture lead or engineering director as sponsor; scribe for agreements.

Input

Whiteboard or Miro board with heatmap template (team list vertically and horizontally, cells for interaction modes); definitions of three modes with examples; list of current interface problems; pens with three colors for modes.

Template

Team Topologies Interaction Modes Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Interaction heat map:
  • Agreements by pair:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Interaction-Heat-Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Team Topologies Interaction Modes Working Template

View templateCompact working template for Team Topologies Interaction Modes with context, input, output artifacts, and next step.
canvas

team-topologies-interaction-modes-working-template.md

Compact working template for Team Topologies Interaction Modes with context, input, output artifacts, and next step.

Team Topologies Interaction Modes Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Interaction heat map:
  • Agreements by pair:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Interaction-Heat-Map.
  • Re-run semiannually or on org change. Mode change with date and rationale. Make transition phases visible (for example "Q3: Collaboration, Q4: X-as-a-Service targeted"). Archive previous version.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet