United We TransformCreate teamsGrade your agenda
Exercises/Closure and Transfer/Cross-Team Connections
General Collaboration Exercise ยท Closure and Transfer

Cross-Team Connections

Pairs from different teams interview each other about one operational strength and one current challenge. They capture patterns on shared notes to identify cross-department miscommunication drivers.

15 minutesTIME
4 to 24 peopleGROUP SIZE
In person, Remote, HybridSETTING
4 materialsMATERIALS
Planning pillar: Follow Through UWT groups this closure and transfer activity under Follow Through in its Gathering Effectiveness planning framework.

Choose this exercise

Purpose: Exchange accurate daily working realities across team boundaries to surface operational friction.

Use it when: Use when departments experience repeated handoff failures, siloed planning, or finger-pointing across workflows.

Skip it when: Skip when participants all belong to the exact same working team, or during active formal grievance investigations.

Group arrangement: Pairs composed of two people from different functional teams; groups of three if numbers are odd.

Timing: Expanded from the 10-minute icebreaker segment in the source to a complete 15-minute diagnostic exercise.

Materials and tools

Before participants arrive

  1. Divide the flipchart or whiteboard into two vertical columns labeled 'Team Strengths' and 'Current Challenges'.
  2. Ensure seating allows quick pairing across different departments or roles.

Say this to open

Find a partner from a department or team different from your own. You will take turns interviewing each other for three minutes each. Your task is to name one thing your team handles well day-to-day, and one specific operational challenge your team currently faces. Write each on a sticky note so we can see the broader picture across our organization.

How to run it

  1. Pair up and review prompt 2 minutes

    Participants find a counterpart from another functional group. If participant counts are odd, form one trio. The facilitator presents an example: 'Our team responds to urgent bug tickets in under an hour (strength), but we rarely get advance notice when marketing launches a campaign (challenge).'

  2. Interview first partner 3 minutes

    Partner A speaks while Partner B listens without debate. Partner A describes one clear team strength and one concrete team challenge. Partner B writes these onto two separate sticky notes, using one color or designated side.

  3. Interview second partner 3 minutes

    Sound a chime to switch. Partner B now speaks while Partner A listens and records Partner B's strength and challenge onto two separate sticky notes.

  4. Post and sort themes 3 minutes

    All pairs walk to the board and place their sticky notes into the corresponding 'Team Strengths' or 'Current Challenges' columns. Pairs cluster notes that describe identical or closely related issues.

  5. Review patterns 4 minutes

    Facilitator reads three distinct notes from each column aloud. The group reviews the visible cluster distribution without calling out individual performance.

Debrief questions

Finished output: A two-column board displaying categorized strengths and operational challenges across represented departments.

Remote

Use randomized breakout rooms of two people. Participants record their responses on a two-column collaborative digital board (such as Miro or Google Jamboard) labeled 'Team Strengths' and 'Current Challenges'. Return to the main room at 8 minutes for cluster review.

Hybrid

Pair in-person attendees with in-person counterparts. Pair remote attendees in online breakout rooms. Assign an in-person scribe to transfer digital board entries onto the physical wall so both audiences see the full set of notes.

Access and participation choices

If the session gets stuck

An odd number of participants leaves one person without a partner.
Create one group of three. Allocate 2 minutes per speaker instead of 3, keeping the total interview phase to 6 minutes.
Participants turn the interview into an airing of interpersonal complaints about specific colleagues.
Intervene and redirect focus back to processes, tools, schedules, and information handoffs rather than individuals.

Terms used here

Live facilitator

Run this exercise live

The facilitator console stays in this browser. Its QR handoff is a short-lived participant snapshot containing only public exercise instructions, phase, prompt, and timer state.

Run this with your AI assistant +

Works with Claude, ChatGPT, Gemini, or your own local model: paste this prompt and your AI will co-facilitate this exercise with you.

Help me prepare and run the exercise below. First ask for my participant count, time, setting, access needs and intended result. Check these against the stated limits. Use the supplied rules and materials. Explain any proposed changes before using them, and label them as adaptations. Do not invent source claims or require personal disclosure. Give me one step at a time when I say start. I manage the people, physical activity and clock; do not claim to observe the room. Ask me what happened before choosing a next step.

Reference revision: 02aa6fc31c6c2fbf8c8d6992bd518f672cdc74f4c5a68a46919db6315a63e36e

# Cross-Team Connections

Pairs from different teams interview each other about one operational strength and one current challenge. They capture patterns on shared notes to identify cross-department miscommunication drivers.

**Time:** 15 minutes. Expanded from the 10-minute icebreaker segment in the source to a complete 15-minute diagnostic exercise.
**People:** 4 to 24. Pairs composed of two people from different functional teams; groups of three if numbers are odd.

## Choose this exercise

**Purpose:** Exchange accurate daily working realities across team boundaries to surface operational friction.
**Use it when:** Use when departments experience repeated handoff failures, siloed planning, or finger-pointing across workflows.
**Skip it when:** Skip when participants all belong to the exact same working team, or during active formal grievance investigations.

## Materials and tools

- 1 pad of sticky notes per pair
- 2 fine-tip markers per pair
- 1 shared flipchart easel or whiteboard
- 1 countdown timer

## Before participants arrive

1. Divide the flipchart or whiteboard into two vertical columns labeled 'Team Strengths' and 'Current Challenges'.
2. Ensure seating allows quick pairing across different departments or roles.

## Say this to open

Find a partner from a department or team different from your own. You will take turns interviewing each other for three minutes each. Your task is to name one thing your team handles well day-to-day, and one specific operational challenge your team currently faces. Write each on a sticky note so we can see the broader picture across our organization.

## How to run it

### 1. Pair up and review prompt (2 minutes)

Participants find a counterpart from another functional group. If participant counts are odd, form one trio. The facilitator presents an example: 'Our team responds to urgent bug tickets in under an hour (strength), but we rarely get advance notice when marketing launches a campaign (challenge).'

### 2. Interview first partner (3 minutes)

Partner A speaks while Partner B listens without debate. Partner A describes one clear team strength and one concrete team challenge. Partner B writes these onto two separate sticky notes, using one color or designated side.

### 3. Interview second partner (3 minutes)

Sound a chime to switch. Partner B now speaks while Partner A listens and records Partner B's strength and challenge onto two separate sticky notes.

### 4. Post and sort themes (3 minutes)

All pairs walk to the board and place their sticky notes into the corresponding 'Team Strengths' or 'Current Challenges' columns. Pairs cluster notes that describe identical or closely related issues.

### 5. Review patterns (4 minutes)

Facilitator reads three distinct notes from each column aloud. The group reviews the visible cluster distribution without calling out individual performance.


## Debrief questions

- Which posted challenge appears across more than one functional department?
- How might an existing strength from one team offset a challenge posted by another?

**Finished output:** A two-column board displaying categorized strengths and operational challenges across represented departments.

## Remote

Use randomized breakout rooms of two people. Participants record their responses on a two-column collaborative digital board (such as Miro or Google Jamboard) labeled 'Team Strengths' and 'Current Challenges'. Return to the main room at 8 minutes for cluster review.

## Hybrid

Pair in-person attendees with in-person counterparts. Pair remote attendees in online breakout rooms. Assign an in-person scribe to transfer digital board entries onto the physical wall so both audiences see the full set of notes.

## Access and participation choices

- Participants may dictate their responses to their partner instead of writing.
- Participants may describe a generic workflow challenge rather than personal or interpersonal difficulties.
- Anyone may choose to observe silently as an interview scribe without sharing their own team data.

## If the session gets stuck

**An odd number of participants leaves one person without a partner.**

Create one group of three. Allocate 2 minutes per speaker instead of 3, keeping the total interview phase to 6 minutes.

**Participants turn the interview into an airing of interpersonal complaints about specific colleagues.**

Intervene and redirect focus back to processes, tools, schedules, and information handoffs rather than individuals.


## Terms used here

- Cross-Team Connections: A structured pair interview where members of differing functional groups compare operations.

## Sources and adaptation

Observed in WorkshopBank as the opening activity ('Cross-Team Connections') of the workshop agenda titled 'From Conflict to Collaboration: Building Stronger Inter-Team Relationships'.

Retained the core mechanic from step 1 of WorkshopBank's 'From Conflict to Collaboration' agenda (cross-team pair sharing one strength and one challenge). Added explicit time allocation, pair-to-board documentation, debrief prompts, and hybrid protocols for standalone execution.

[WorkshopBank](https://workshopbank.com/tools/frequent-miscommunication)

Current run sheet: https://unitedwetransform.com/exercises/frequent-miscommunication-workshopbank/

Sources and adaptation

Observed in WorkshopBank as the opening activity ('Cross-Team Connections') of the workshop agenda titled 'From Conflict to Collaboration: Building Stronger Inter-Team Relationships'.

Retained the core mechanic from step 1 of WorkshopBank's 'From Conflict to Collaboration' agenda (cross-team pair sharing one strength and one challenge). Added explicit time allocation, pair-to-board documentation, debrief prompts, and hybrid protocols for standalone execution.

See our editorial policy for AI use, sourcing and corrections.

Pairs well with