Team Interaction Design Workshop

Purpose

The Team Interaction Design Workshop helps organisations design team structures that optimize for fast flow of change. By mapping teams to four types (Stream-aligned, Platform, Enabling, Complicated-subsystem) and three interaction modes (Collaboration, X-as-a-Service, Facilitating), leaders can reduce cognitive load and improve delivery.

At a glance

How to run

1. Introduction (10 min) — Present the four team types and three interaction modes.
2. Map current teams (20 min) — List all teams. For each, identify its current type and primary interaction mode with other teams. Place on a visual map.
3. Assess cognitive load (15 min) — For each team, rate the cognitive load: how many domains, services, and responsibilities does it own? Identify overloaded teams.
4. Design target topology (25 min) — Propose changes: split overloaded teams, create platform teams, introduce enabling teams. Map the target interaction modes.
5. Identify transition steps (15 min) — What needs to change to move from current to target? People moves, service transfers, new platform investments.
6. Close (5 min) — Agree on next steps and timeline for implementation.

Materials needed

• Skelton and Pais's book or a summary (four types, three modes)
• Current org chart and team list
• Visual mapping board (physical or Miro)
• Cognitive load assessment template

Pitfalls & common mistakes

• Renaming without restructuring — Calling a team "platform" does not make it one. Change the responsibilities.
• Ignoring cognitive load — The primary signal for team design is cognitive load, not headcount.
• Too many interaction modes — Each team pair should have one primary mode. Multiple modes create confusion.
• Big-bang reorg — Evolve gradually. Large restructurings are disruptive.

Inclusion & accessibility

• Involve team leads and members in the design, not just management.
• Provide the framework summary in advance.
• Use visual mapping with text labels for accessibility.

Variations

• Team API workshop — Each team defines its API: what it provides, what it expects, and how to interact.
• Inverse Conway maneuver — Design the org structure to match the desired architecture.
• Platform-as-a-product workshop — Focus on designing the internal platform team's product offering.

When NOT to use this

• If the organisation has only one team — no topology to design.
• If leadership is not willing to restructure — the workshop produces unrealizable plans.

Source & further reading

• Skelton, M. & Pais, M. (2019). *Team Topologies*. IT Revolution.
• Conway, M. (1968). "How Do Committees Invent?" Datamation.