All methods

Bridge Building

Typical duration:
45m

Sub-teams build halves of a bridge separately, then join them — testing cross-team communication, specification alignment, and collaborative engineering.

Purpose

Bridge Building splits participants into sub-teams that each build one half of a bridge in separate rooms. The halves must connect when brought together. The exercise powerfully reveals the cost of poor cross-team communication, unclear specifications, and assumption-making. It is an outstanding simulation of distributed team collaboration, API contracts, and integration challenges.

At a glance

  • Group size: 8–30 participants (2–4 sub-teams)
  • Duration: 45 minutes
  • Difficulty: Intermediate to Advanced
  • Facilitation style: Structured with separation rules
  • Setting: Indoors; two or more separate rooms

How to run

  1. Brief (5 min): Your teams will each build one half of a bridge. The halves must meet in the middle and support a toy car crossing. You have identical materials. You may send one ambassador between rooms every 5 minutes for 2-minute visits.
  2. Split and build (30 min): Teams work in separate rooms. Enforce the ambassador rule strictly. Provide identical material kits.
  3. Integration (5 min): Bring the halves together. Test the bridge. The toy car must cross without falling.
  4. Debrief (5 min): What assumptions did each team make? What information did the ambassadors carry? What would you do differently? How does this mirror cross-team work in your organisation?

Materials needed

  • Identical building kits per team: newspaper, tape, cardboard, scissors, straws, string
  • A toy car for the bridge test
  • Two separate rooms or screened areas
  • Timer

Pitfalls & common mistakes

  • Non-identical kits: Even slight differences introduce a confound. Prepare kits carefully.
  • Uncontrolled communication: If teams text or shout through walls, the exercise loses its point. Enforce separation.
  • No integration test: The magic moment is the join. Always bring the halves together even if time is tight.
  • Ignoring the ambassador role: Coach ambassadors that they represent both teams and must be clear communicators.

Inclusion & accessibility

  • Provide scissors and tools that work for left-handed and right-handed participants.
  • Assign roles (builder, designer, ambassador, tester) so everyone has a meaningful contribution.
  • Ensure separate rooms are equally accessible.

Variations

  • No Ambassador: Teams get a written specification only. Tests documentation quality.
  • Three-part Bridge: Three teams build thirds. Exponentially harder integration.
  • Bridge Building with Budget: Each material has a cost. Teams must build within budget.

When NOT to use this

  • When cross-team tensions are already high — a failed integration can reinforce blame rather than learning.
  • With fewer than 8 participants, where the sub-team dynamic is too thin.
  • When separate rooms are not available and the separation cannot be maintained.

Source & further reading

  • Cain, J. and Jolliff, B. (1998). Teamwork and Teamplay. Kendall Hunt.
  • Kaagan, S. (1999). Leadership Games. Sage Publications.

Turn the building blocks into an agenda

Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.

Try it free for 14 days
Bridge Building · GoodWorkshop