Team building
Most team building fails for the same reason: someone runs the activity and skips the conversation afterwards. The activity is not the training. The debrief is the training. Below are eighteen activities we have actually facilitated, with the setup, the timing, what each one reveals about a team, and the question to ask when it ends.
Three things separate an activity people remember from an afternoon they endure, and none of them are the activity itself.
A rough rule: no more than a third of your slot on the activity, at least a quarter on the conversation afterwards.
| Activity | Group size | Time | What it surfaces |
|---|---|---|---|
| Ten things in common | Any, in fours | 5 min | Question quality, curiosity |
| Two truths and a lie | 4-20 | 10 min | Assumptions held about each other |
| Bad idea brainstorm | 4-30 | 10 min | Willingness to be wrong in public |
| Back-to-back drawing | Even numbers | 15 min | Listening, checking for understanding |
| Lost at sea | 4-8 per group | 45 min | Whether the group beats its best individual |
| Marshmallow challenge | 4-6 per team | 40 min | Planning versus testing, status jockeying |
| Build a bridge | 2 teams of 4-8 | 60 min | Handovers between functions |
| Team timeline | 5-25 | 60 min | Conflicting versions of the team's history |
| Escape box | 4-8 per box | 45 min | Information hoarding under pressure |
| Raft build or river crossing | 10-100+ | Half day | Leadership with real consequences |
| Charity build | 10-200 | Half day | Meaning, cross-level mixing |
| Cook-off | 8-40 | Half day | Coordination without a designated boss |
| Virtual escape room | 3-6 per room | 60 min | Remote turn-taking and voice |
| Desk photo hunt | Any, remote | 15 min | Low-stakes visibility for quiet people |
| One object show and tell | 4-15, remote | 20 min | Personality without forced disclosure |
| Random coffee pairings | 20+ | Ongoing | Cross-silo weak ties |
| Working style manual | Any | 45 min | Friction nobody mentions |
| Appreciation round | 4-15 | 15 min | Who gets seen, and who does not |
No materials needed. Use these to open a meeting that matters, not to fill one that does not.
Groups of four, four minutes, ten things they genuinely share. Obvious ones banned: not the company, not the city.
Reveals: who asks good questions. Groups that reach ten ask about texture; groups that stall trade facts. Ask afterwards: which question got the most interesting answer, and why did that one work?
Three statements each, one false, and the group votes. Keep all three about skills, places, jobs or things people have made. Family, money, faith and health are off limits, and saying so up front removes the pressure quiet people feel.
Reveals: the assumptions colleagues already carry about each other. Ask afterwards: which lie did you believe, and what does that say about the story you had built?
Take a real problem the team is stuck on. Five minutes generating the worst possible solutions, competitively. Then five minutes on what the least bad one points at.
Reveals: how safe it is to say something half-formed here. Teams with low psychological safety produce cautious bad ideas, which is both a contradiction and a diagnosis. Ask afterwards: what stops anyone saying these in a normal meeting?
Pairs sit back to back. One describes a simple abstract diagram, the other draws it unseen and, in round one, without asking questions. Run round two with questions allowed, then compare.
Reveals: how much rework comes from instructions nobody checked. Active listening in six minutes. Ask afterwards: when did you realise you were not being understood, and why did you carry on anyway?
Same scenario, fifteen salvaged items. Everyone ranks them alone and silently, then the group agrees one shared ranking. Score both against the published expert ranking.
Reveals: whether the group beat its best individual. Often it did not, because the person who was right got talked over. Ask afterwards: who scored closest, and when did we stop listening to them?
Teams of four get twenty sticks of dry spaghetti, a metre of tape, a metre of string and one marshmallow. Eighteen strict minutes, tallest freestanding structure, marshmallow on top.
Reveals: teams that plan for fifteen minutes and add the marshmallow last collapse at minute seventeen; teams that test early adapt. It also exposes the three minutes spent settling who is in charge. Ask afterwards: when did you first test whether it held weight?
Two teams in separate rooms each build half a bridge to a shared specification, communicating only by written note or one liaison. The halves must then join and take a load.
Reveals: everything wrong with your handovers. The halves rarely meet, and the post-mortem sounds like a real cross-team project. Ask afterwards: what did you assume the other side knew, and what would checking have cost?
Roll paper along a wall. Everyone marks the team's history, highs above the line and lows below. Then walk it left to right, letting people narrate their own marks.
Reveals: several versions of the same history, and that one person's proudest moment was another's worst quarter. Good after a merger, restructure or fast growth. Ask afterwards: which event on this wall are we still reacting to?
A locked box of chained puzzles, solvable in forty-five minutes by four to eight people. Distribute clues so no one person holds them all. Buy one, or build one from padlocks and printouts.
Reveals: who hoards information under pressure, who broadcasts it, and who quietly solves things and never says so. Ask afterwards: what did you know that the group never heard?
Longer formats earn their cost when a team has a real fracture to repair or a new shape to settle into, not when someone needs to spend a budget. A team mid-storm in Tuckman's terms gets more from a facilitated day than another workshop.
Classic outbound training: build something that must carry the team across water, or move a group over a marked hazard with limited kit. Run it with qualified safety cover and a genuine opt-out.
Reveals: who takes charge once the stakes stop being hypothetical, and whether that is the person with the title. Ask afterwards: who led, who followed, and is that the same pattern as Monday morning?
Teams assemble bicycles, school kits or shelter boxes that go to a local organisation, ideally with recipients present at the handover.
Reveals: what the group is like when the work is obviously worth doing. It mixes hierarchy levels better than almost anything, because nobody's grade helps with a bicycle. Ask afterwards: what changed when the output mattered to someone outside the room?
Teams cook one course each against the clock, with a shared pass and a fixed serving time, then eat the result together. Reveals: coordination without an org chart, and dependency management you can taste. Check dietary needs and confidence privately beforehand, and give non-cooks a real role: timing, sourcing or plating.
Video calls flatten status cues and reward whoever interrupts comfortably, so remote activities need more structure, not less. There is a fuller set in our guide to virtual team building activities.
Breakout rooms of three to six, one shared puzzle set, sixty minutes. Give each room a timekeeper who does not solve. Reveals: remote turn-taking, since whoever cracks it is often just the one willing to speak over others. Ask afterwards: whose idea got dropped, and what would have made it easier to hear?
Prompts one at a time, ninety seconds each: something older than you, something that solves a problem, something you would grab in a fire drill. People hold objects to camera and say one line. It reveals nothing profound, and that is fine. It gives quiet people a low-stakes reason to speak.
Two or three people per meeting bring one object from their desk and take three minutes on why it is there. Rotate over weeks. Reveals: personality without forced disclosure, because an object lets people choose how much of themselves to share. It works where a compulsory fun fact does not.
Pair two people from different teams each fortnight for twenty minutes, no agenda. Automate it, keep it optional, and supply three questions so the call does not die in the first minute. Reveals: over months, the weak ties that make cross-team requests fast. Nothing works in week one, which is why most companies abandon it in week three.
Half a page each: how I prefer to receive feedback, when I think best, what I am bad at, how to tell when I am stressed, the fastest way to reach me. Share in pairs, then keep them findable.
Reveals: friction people have absorbed silently for years. Keep it to work behaviour. Ask afterwards: what did you learn that would have changed how you handled something last month? It pairs with better habits around giving feedback.
Ten minutes at month end. Each person names one specific thing another did and the effect it had: 'you rewrote that brief at 9pm and it saved the pitch', not 'you are great'.
Reveals: who is invisible. Run it a few times and two names will collect most of the recognition while somebody's steady work goes unmentioned. That gap deserves more attention than the exercise.
Four questions, in order, and resist filling the silences. What happened? How did that feel at the time? What does it remind you of in how we work here? What will we do differently, and starting when? Only the fourth changes anything, and it is the one facilitators run out of time for.
Good facilitation means asking, not telling. Explain the lesson and it becomes your observation instead of theirs, and people defend themselves against observations they did not make. To feel a good debrief from the inside, play The Weekly Challenge with your team and talk about your answers.
Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.
Questions
The best ones are short, relevant to how the team actually works, and followed by a proper discussion. Reliable choices are the marshmallow challenge for planning habits, lost at sea for decision-making, back-to-back drawing for listening, and a team timeline for groups carrying unresolved history. The activity matters less than the debrief afterwards.
Ten things in common, a bad idea brainstorm on a real problem, two truths and a lie kept to work topics, or back-to-back drawing. Each takes five to fifteen minutes, needs no materials, and can be debriefed in another five. Use them to open a meeting that matters rather than to pad one that does not.
As a rule, spend no more than a third of your total slot on the activity and at least a quarter on the conversation afterwards. A twenty-minute exercise with ten minutes of structured questions beats a two-hour event with no reflection at all.
Usually three reasons: attendance was compulsory but the purpose was never explained, the activity exposed people personally, or nothing changed afterwards. Fix those and most resistance disappears. People rarely object to spending time together; they object to being made to perform enjoyment.
Use more structure than you would in a room. Small breakout groups of three to six, a named timekeeper, and prompts that let people choose their level of disclosure, such as one object show and tell. Keep sessions short, run them inside existing meetings, and avoid the two-hour virtual social.
Ask four questions in order and let the silences run. What happened? How did it feel at the time? What does that remind you of in how we work here? What will we do differently, and starting when? Ask rather than explain: a lesson you deliver is your conclusion, while one the team reaches is theirs.
Keep reading
The same discipline applied to teams that never share a room.
GuideWhy the reflection, not the activity, is where the learning happens.
Free ยท 10 minutesOne crisis week, ten minutes, and a debrief worth having with your team.
Get in touch
Book a 30-minute discovery call and we'll shape an experiential programme around your goals.
Book a discovery call →