Problem Swap

A structured peer consultation. Everyone brings one real, current, stuck problem. In rotating pairs, you get four minutes of someone else's undivided attention on yours. The constraint that makes it work is that the listener is not allowed to give advice until the last minute.

What it is good for

• Problem solvingStructuring an ambiguous problem under a time limit.
• CollaborationWorking a shared problem where no one person holds all the information.
• Trust & safetyLowering the cost of admitting a mistake or asking for help.
• Creative thinkingGenerating options before judging them, and building on other people's ideas.

What you need

• A written problem statement from each participant
• A timer

The run sheet

1. Written problems, sent ahead (prep)

   One paragraph: what the problem is, what you have tried, what would count as progress. Writing it is half the value, and people who skip it get noticeably less out of the session.

2. Pair up and set the clock (2 min)

   Pairs, eight minutes each way. Explain the structure before the first round, not during it.

3. Minutes one to three: questions only (3 min)

   The listener may only ask questions. No suggestions, no 'have you tried', no stories about their own similar problem. This is the hard part and it is the whole technique.

4. Minutes four to six: reflect back (3 min)

   The listener describes the problem back as they understand it. The speaker corrects. People routinely hear their own problem restated and realise it is a different problem.

5. Minutes seven and eight: now advise (2 min)

   Now the listener may suggest. Having spent six minutes understanding, the suggestions are an order of magnitude better.

6. Swap, then rotate pairs (30 min)

   Swap roles, then re-pair and run it again with a different partner. Two or three rotations is the sweet spot.

Facilitator notes

• Enforce the no-advice rule loudly in round one. Everyone breaks it; naming it once makes round two work.
• This is the activity to reach for when a team says they do not want team building. It is unmistakably useful work and it builds trust anyway.
• Keep pairs cross-functional where you can. The naive question from someone outside the problem is the one that lands.

Debrief questions

Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.

1. Did your problem change shape when someone else described it back to you?
2. What was harder: not giving advice, or not getting it immediately?
3. What is the one thing you will try before we next meet?

Variations