Team Building for Multicultural Teams: Why Games Work Where Quizzes and Happy Hours Fail

An HR director at a fintech company with 180 people in 21 countries told us about the year she ran a New Year quiz. It was built in one language with a live translation into English, and the questions were about films and music. One group wrote to ask why it was in the wrong language. Another wrote to ask why all the films were American and none were the ones they had grown up with. Attendance was low, the feedback was angry, and she did not organise anything for a year. "I put my hands down," she said.

Nothing was wrong with the quiz. Everything was wrong with the assumption underneath it: that a team from 21 countries shares a stock of references to be quizzed on. It does not. Any activity that rewards knowing the same things will split such a team into the people who know them and the people who do not, and it will do so in public, on camera, in front of colleagues.

This is a guide to the formats that do not do that, written from what organisers of teams in 20, 30, 55 and 80 countries have told us on calls, and from the one thing all of them had in common: the formats that worked were games with mechanics everyone already knew.

Why do quizzes and happy hours fail for international teams?

Because both run on shared background, and a multicultural team's defining feature is that it has none.

A quiz runs on shared knowledge. A trivia round about music, films, geography or "fun facts" is a test of whose culture wrote the questions. The fintech team found this out the hard way, and it is not a matter of writing better questions: a question neutral for a colleague in Lisbon is not neutral for one in Almaty, and the organiser cannot know which is which in advance.

A happy hour runs on shared conventions. How much to say about yourself, when a joke is appropriate, how long a silence is allowed to be, whether interrupting is rude, whether to turn the camera on. Those conventions differ by culture, and a 30-minute social between a team in Germany, a team in Brazil and a team in India is three different events happening in one call. The people who are fluent in the dominant culture's conventions carry it. Everyone else waits for it to end.

Two truths and a lie, show and tell, "share a fun fact" all have the same problem in a smaller box. They ask people to produce personal content on demand in a second language, in front of colleagues, under conventions they did not grow up with. For many people that is the single worst part of the working week, and it is positioned as the warm-up.

What is the one format that works across cultures?

A shared task with rules that need no explaining. In practice, a game.

Here is the reasoning, and it is mechanical rather than inspirational. A game has four properties that conversation formats lack:

1. The rules are the same for everyone and they are written down. Nobody has to infer how to behave from cultural cues.
2. The subject is the puzzle, not you. Nobody is asked to disclose anything personal to take part.
3. Participation is action, not speech. A person who is shy in English can still solve, move, collect, click. Their contribution is visible on the shared board, not dependent on finding the right words.
4. The common ground is in front of you, not inside you. Conversation happens because of the task, not instead of it: "the code has four digits and we have three" is a sentence anyone can say in any level of English.

When we asked the same HR director what did work for her team, she named the mechanics everyone on earth has met: dodge the thing, collect the thing, beat the clock. "Does everyone know those?" we asked. "Everyone." A platform level, a maze, a falling-blocks puzzle, a timed code to crack, these are the lingua franca of the last forty years. People from Warsaw, Nicosia and Chisinau did not grow up on the same films. They grew up on the same games.

That is the whole thesis, and it is narrower than "games are fun". It is: choose activities where what people need to know in advance is zero, and where what they contribute is an action rather than a statement about themselves.

What about time zones? Nobody can be on the same call

Two things we learned from organisers of teams across 30 and 80 countries, and one thing we learned from reading 4,772 public forum posts about workplace team building.

The first thing: the live event is not the problem people name. In the forum corpus, "time zone" appears in 14 posts out of 4,772. The complaints that dominate are about being required to attend, and about attending outside working hours. People do not say "the time zone is wrong". They say "I don't want to be in another meeting" and "that's my time". An organiser at a 120-person company in 30 countries put it exactly like this: "I'm staying here in front of a computer the whole day, most people are, and then if we suggest a 30-minute activity, for them it feels bad."

The second thing: the organisers who have solved it did not find a better meeting time. They changed the shape. The 2,000-person company wanted no live session at all: "any time at all", teams assemble themselves, three or four short games across a week, each 10 to 15 minutes, "entertainment without taking people away from work". The 120-person company wanted the same: one short task a day, played whenever it suits each person, points adding up on one leaderboard across the whole company, and a short live finale for the people who want it.

So the time-zone answer is not a clever calendar. It is: run the game asynchronously over a week or a month, let people play in their own hours, keep the live part short and optional, and put it at the end as a celebration rather than at the start as the event. A leaderboard does the work the live room used to do. The 120-person organiser already ran a step-counting challenge this way and described the effect herself: "people sometimes just walk a little bit more because, well, I want to be on the leaderboard."

How do you handle languages inside the game?

Three rules from the calls, all of them cheap.

The game and the host run in the company language. Inside a team, people speak whatever they like. The fintech HR director said she could already hear her executives objecting to a game forced into one language, and agreed instantly to this split. The puzzles are visual and mechanical, so the team can argue about them in Polish, Greek or Russian and still solve them in English on the shared board.

Let teams form themselves, or form them deliberately, but say which. Random assignment is fair and lonely. Self-selection is comfortable and reinforces the clusters you wanted to break. The hospitality company with 75 remote salespeople chose deliberately, "so people who don't often interact are forced to interact", and told the team that was the point. Either works. Silence about it does not.

Watch for the language barrier that is really a social one. A games studio moving its company language to English told us the problem was not vocabulary but fear: "when the company always spoke Russian, people are a bit shy, everyone has an accent." A game is the lowest-stakes place to speak a second language badly, because nobody is listening to your grammar, they are listening for the next clue. The same HR lead described the effect as the game "putting people in a friendly atmosphere" first, and the language following.

Does the theme matter? Christmas, Halloween, national holidays

More than organisers expect, and in a specific way.

The fintech HR director hesitated over a game called "Save Christmas" because of colleagues in Israel, Georgia and Kazakhstan: "I'm not sure how they'll take it." She chose a game set in a snowed-in hotel at midnight instead, winter without the religion. The hospitality company chose a hotel mystery over a sports game because the setting matched their work, and the organiser's reasoning applies to culture as much as to industry: "then they think it's been tailored just for them."

The rule that follows: a setting the whole team shares beats a setting that half the team celebrates. Winter, a hotel, a heist, a temple, a spaceship, an arcade. Not a holiday, unless you are certain everyone on the list keeps it. The occasion can live in the framing and the prizes. The game itself should be neutral ground.

What does this look like for a team that has never met?

The extreme case, and increasingly the normal one. The 75-person sales team inside a hotel group had people who had worked together for five years and never met except on video; they were not even invited to the company's global conference. The 180-person fintech had never held a company-wide event at all. The 120-person recruiter flies everyone to one city once a year and the organiser said, of the warmth it produces, "but this doesn't last, as you know."

For these teams the order of operations matters:

1. Faces first, at low stakes, asynchronously. Two weeks before anything live, a photo prompt everyone can answer in their own time: the view from your desk, your dog, a holiday photo. The hospitality organiser asked for exactly this and explained why: "our team really likes showing photos", and it is participation without performance. By the time the game starts, forty faces are familiar.
2. Then the shared task, in teams of four to eight, mixed across countries on purpose, with the rules on screen and the clock running. The 2,000-person company's event team asked whether they could build the teams themselves and hand us the lists. Yes, and the deadline for that list is the one date the whole plan hangs on.
3. Then the short live finale, optional, where the leaderboard is read out and the winning team gets something that is not a gift card. Fifteen to thirty minutes. The people who hate meetings can skip it and still have played.

The 120-person organiser summed up the need in one line that we would put on the wall: "I think we should have different kinds of platform for different people, because some like games and some don't." She is right, and the game is the one format where the people who "don't" can still take part without saying a word.

The short version

• A multicultural team has no shared references and no shared conventions. Quizzes test the first, happy hours test the second. Both exclude in public.
• A game with simple mechanics needs neither. The rules are written down, the subject is the puzzle, participation is action, and the common ground is on the screen.
• Time zones are solved by shape, not scheduling: async over a week, short optional live finale, leaderboard as the shared room.
• Game and host in the company language, any language inside the team.
• Neutral setting, never a holiday the whole list does not keep.
• Faces first, then the task, then the celebration.