Team building: how to run a day nobody endures

There's a phrase every team lead has heard at least once, muttered near the coffee machine: "another team building day." It sums up a stubborn misunderstanding. The company spends real money, sets aside a full day, and gets polite attendance and a lukewarm memory in return.

The problem is almost never the activity chosen. It's the order in which decisions were made. In the vast majority of cases, someone booked an activity they personally found appealing, then asked people whether they were free. Everything that goes wrong afterward stems from that reversal.

Why a team day fails

Three causes come up again and again, and none of them is about budget.

The activity quietly excludes part of the group. An escape room, a treetop rope course, go-karting or a twelve-kilometer hike look harmless. They aren't, for someone claustrophobic, someone overweight, someone with back trouble, a pregnant woman, someone hard of hearing in a noisy environment, or someone who can't swim. These people won't say so in front of the team. They'll find a reason not to come, and that reason will be believed.

The schedule spills past the workday. An activity that ends at 9 p.m. turns a company event into a personal burden. Single parents, people with a ninety-minute commute, people caring for a dependent are excluded by the schedule without anyone having decided so.

The purpose was never spelled out. "Strengthen cohesion" isn't a goal, it's a wish. A day with no clear purpose produces a string of activities, and participants can tell perfectly well that their time is being filled without anyone knowing why.

Decide the purpose before anything else

Three legitimate purposes exist, and they call for different kinds of days.

Getting people who don't know each other to meet. After a round of hires, a team merger, a year spent largely apart. The program should favor small rotating groups, mixed seating, and long unstructured time. An activity that keeps the same people together all day completely misses this goal.

Fixing something. Tension between departments, a hard period, a poorly received reorganization. A fun day fixes nothing — it can even deepen the cynicism if the underlying issue isn't addressed. This format needs structured time to talk, often an outside facilitator, and courage.

Celebrating. The end of a heavy project, a good result, a company anniversary. Here the goal is simply enjoyment, and that's perfectly legitimate. Just own it, and don't disguise a party as a strategy seminar.

A purpose written in one sentence and shared with the team before you consult them changes the nature of the answers you'll get.

The consultation: ten questions, three minutes, confidential

This is the step that separates a day people enjoy from a day people endure. It happens before anything is booked, otherwise it no longer collects constraints — it collects grievances.

What to ask everyone:

1. Dates that are impossible, distinguishing "impossible" from "would rather avoid."
2. The acceptable time window that day: by what time do you absolutely need to be free?
3. Physical constraints: is there anything that would make an activity difficult or unpleasant for you? Phrased this way, with no medical justification required.
4. Dietary restrictions and allergies, with severity level.
5. Starting point and mode of transport, and whether carpooling is possible or a ride is needed.
6. Three types of activities you'd enjoy and, more importantly, one you'd rather avoid.
7. The level of exposure you're comfortable with: some people hate games that involve talking about themselves in front of others. They're entitled to that.
8. Alcohol: wanted, indifferent, or a problem. A meaningful share of your colleagues don't drink, for reasons that are none of your business.
9. Whether you need quiet time at some point during the day.
10. What would actually make this day worthwhile for you. An open question, and often the most revealing one.

Two conditions make these answers usable: they must take under three minutes to fill in, and nobody should see anyone else's answers. A shared spreadsheet produces conformity answers; a confidential one produces accurate data.

That's exactly what OuiCanPlan is for: you describe the day in a few lines, the questions relevant to your situation are automatically asked of each participant, everyone answers via a simple link in two minutes about, and you get back a usable summary — viable dates, anonymized physical constraints, a tally of dietary needs, transport requirements — instead of a spreadsheet to sift through by hand. Free for up to ten participants, for three plans a month with a 7-day history, and with no advertising at all.

Building a program that holds up

A few principles that noticeably improve how a team day is received.

Always offer two parallel options for the main activity, one of them gentle. A hike or a guided tour. A sports course or a cooking workshop. And above all: present them as two equally valid choices, never as "the activity" and "the accommodation for people who can't do it." The wording determines who dares to pick the second one.

Long unstructured time beats fragmented time. Two hours of lunch with no agenda beat four thirty-minute breaks. That's when people actually talk to each other; everything else is just an excuse to bring them together.

No more than forty-five minutes of any facilitated activity in a row. Beyond that, attention drops off, and a whole day of overlong sequences leaves people with a memory of exhaustion.

Mix the groups on purpose. Letting people group themselves freely just reproduces the org chart and existing cliques — the exact opposite of the goal. Build the groups yourself, and change them for each sequence.

End in late afternoon, not late evening. If you're planning a dinner, announce it as optional, explicitly and in advance, and make sure leaving beforehand doesn't get noticed.

The question of mandatory attendance

It deserves to be settled early and stated clearly, because it changes a lot of things.

If the day is on work time and mandatory, it's paid as work time, travel is covered, and the employer bears the constraints that creates — including extra childcare costs. In that case, every activity needs a genuine alternative: you can't make a day mandatory and force a physical activity on people within it.

If it's optional, make sure it actually is. An "optional" activity where the manager mentally notes who showed up isn't optional. And an optional day scheduled on a Saturday mechanically excludes parents of young children: that's not a neutral policy.

The soundest formula in most organizations: on work time, attendance expected, content à la carte.

The budget, item by item

For a day with no overnight stay, plan on €60 to €180 per person depending on ambition. The line items people forget, and that blow up the budget:

• transport for participants, including mileage reimbursement for those carpooling;
• equipment rental or a backup indoor venue in case of rain;
• drinks beyond the package, which often account for 15% of the final bill;
• insurance if the activity is physical;
• a 10% contingency, without which nine budgets out of ten go over.

One piece of advice that applies to teams of any size: a simple, well-organized day beats an ambitious, poorly calibrated one. Nobody has ever left a successful picnic with a bad memory.

The day after matters as much as the day itself

A team day that leaves no trace is remembered, six months later, as money spent for nothing — even if it went very well.

Two gestures are enough. A short follow-up within forty-eight hours, five questions at most, anonymous: what was most useful, what was missing, the pace, the logistics, one open question. And a written recap of what came out of it, including the uncomfortable feedback and what you plan to do about it.

It's this second gesture that determines participation next time. A team that sees its feedback was actually read answers honestly the following year. A team that sees nothing come back answers politely, and the same cycle starts again.

In summary

A good team day isn't a spectacular one. It's a day where everyone recognizes themselves in the program because they were asked for their opinion once, early, seriously and confidentially. The activity, the venue and the meal matter less than people assume: what stays with people is having felt counted among those whose opinion mattered.

The case of remote teams

A team that never sees each other in person needs these days the most and organizes them the worst. Two pitfalls come up repeatedly.

The first is trying to reproduce, over video, an activity designed for in-person settings. A blind-taste music quiz for fifteen people on a video call, with the lag and the interruptions, mostly produces awkwardness. What works remotely is short — forty-five minutes at most —, in very small groups of three or four in separate breakout rooms, and structured: one question to work through, an announced time limit, a two-minute report-back. Open-ended formats fail because nobody dares speak first.

The second is bringing the team together in person only once a year, and stacking a strategy seminar, team-building and a celebration into two days. It's better to have two shorter get-togethers, each with a clear purpose, than one annual gathering that has to carry everything. And when there's only one in-person event a year, protect the unstructured time first: it's the one thing that genuinely doesn't work remotely.

What you should never do

• Announce the activity before consulting anyone. Once the paddleboarding is booked, the person who can't swim has no option left but to fall sick that day.
• Photograph everyone for social media without having asked permission. Some people don't want to appear, sometimes for serious reasons.
• Mix evaluation with socializing. A team day is never the moment to announce a reorganization or give individual feedback.
• Charge a participation fee, even a symbolic one. It quietly excludes people, and always the same ones.
• Schedule it on a Saturday without time off in compensation.