Team building

Running team building for 100 people or more

A company of more than a hundred people gathered outdoors on a team building day in Singapore

Past about a hundred people, team building stops being a question of what to do and becomes a question of how to move.

The activity is usually fine. It was fine for thirty people and it is fine for three hundred. What changes is that every instruction, every transition and every queue is now multiplied, and the multiplication is where the day is won or lost.

Where the time actually goes

Three costs get left out of every large-group plan.

Briefing. Five minutes of instruction is never five minutes. Gathering a large group, waiting for it to quieten, delivering the brief and releasing it into position reliably takes fifteen to twenty minutes of elapsed time, and it takes that every single time you do it. Brief once at the start, then design stations that explain themselves.

Movement. A group of six walks across a floor in a minute. Twenty groups do not, because they leave at different times, stop to talk, and arrive out of order. Budget several minutes for every transition, and more if there are stairs or lifts involved.

Two people in black slogan T-shirts and red lanyards, seen from behind, wait with others at an entrance
Walking in, at a large team day our team worked on. Movement is the cost nobody plans for.

The slowest station. In a rotation, the whole floor moves at the pace of whichever station runs long, and the delay compounds each time round. This is the single biggest cause of a large day feeling chaotic, and it is fully preventable: time every station in a rehearsal, cut the long one, and give each an identical clock.

Where your day goes

A rotation, timed honestly. The proportion that is actually activity is usually the number that surprises people.

Four things that stop it collapsing

Stagger the starts. Releasing twenty groups at once creates one crowd walking in one direction. Releasing them across a few minutes, in an order you decided, costs nothing and removes the crush entirely.

A pile of white tote bags stuffed with black tissue and small black gift boxes tied with red ribbon
Kit for a large group, packed before the day, at an event our team worked on.

Staff a spare facilitator. Not for an activity, for the floor. Somebody whose only job is to see which station is running long and go and fix it. At scale this person is worth more than an extra station.

Solve food before you solve fun. Feeding two hundred people takes as long as an activity does. Multiple service points, or a staggered lunch by group, or the whole afternoon slips by forty minutes and nobody can point at why.

Make the wet weather plan work for everybody at once. The common failure is a shelter that holds half the group. If it rains, it rains on all of them, and a plan that only works for the first hundred is not a plan.

Time every station in a rehearsal. The whole floor moves at the pace of the slowest one, and the delay compounds each time round.

Do one thing properly

The instinct with a big group and a full day is to fill it: three activities, a talk, a lunch feature, a closing. What that produces is a day of transitions with fragments of activity in between.

One well-run activity with a real debrief, and enough slack for the day to breathe, is the better trade almost every time. The slack is not wasted. It is what absorbs the station that runs long, the rain, and the group that gets lost on the way back.

Which activity it should be follows from what has to be different on Monday, and our guide to team building activities compares the formats.

Common questions

How do you run team building for a large group?

Split into working groups of five to seven, run parallel stations rather than one activity, make every station the same length, and stagger the starts. The constraint at scale is movement between stations and briefing time, not the activity, so the design question is how to keep everybody occupied rather than what to make them do.

How long does it take to brief 200 people?

Far longer than the briefing. Gathering a large group, quieting it, delivering five minutes of instruction and releasing it into position reliably costs fifteen to twenty minutes of elapsed time, and it costs that every time you do it. Brief once, then let the stations explain themselves.

What goes wrong at large team building events?

Queueing. One station running five minutes long stalls every group behind it, and the delay compounds around the rotation. The other recurring failures are food service, toilets at breaks, and a wet weather plan that works for fifty people but not for the whole group at once.

Running one at scale

Tell us the headcount, the date and the site. We will come back with a format that survives the numbers, and an itemised quote you can read.