Virtual Team Building Games
Activities for a remote team, run by whoever called the meeting rather than by a paid facilitator. Including the honest part: why most of them fail, and what to do about the people who did not want to be there.
What to run with a remote team
Ordered by how much time they need, from something that fits a weekly call to something worth booking a session for.
1. This or ThatOffice questions
2+ players5–15 minOne phone
The lowest-commitment thing on this list and the one most likely to be used more than once, which matters more than quality here — a five-minute activity people are happy to repeat every week beats an excellent one that gets run in January and never again. No preparation, no scoring, and no way for anyone to be visibly bad at it.
2. Would You RatherOffice questions
2+ players10–30 minOne phone
The best general-purpose choice for a mixed remote team, because the format forces participation without demanding disclosure. There is no right answer so nobody can be wrong, and no way to opt out with a shrug — everyone picks a side and says why, which is where a team genuinely learns how a colleague thinks rather than what they did at the weekend.
The unglamorous part that decides whether the session works. Deal people into groups rather than letting them choose, because a remote team self-selects along exactly the lines the activity was meant to cross — the same four people who already talk daily will end up together again, and the new joiner will end up with the other new joiner.
3–12 players10–20 minOne phone
The one that rewards knowing how your colleagues actually communicate, which is the specific thing remote teams lack and cannot get from a status meeting. Everyone receives the same word except one person, and finding them means paying real attention to phrasing. Keep it to a dozen people so everybody gets questioned.
3–10 players20–40 minOne phone
What to use when you have booked an actual hour and want something with a shape — twenty to forty minutes, real scoring, and a genuine ending. It rewards writing a convincing lie rather than knowing trivia, so the winner is not whoever happens to read the most, and a team that spans four countries is not quietly disadvantaged by geography-heavy general knowledge.
Why most virtual team building fails
The failure is rarely the activity. It is that the activity was scheduled by someone with authority, attendance is optional in a way everybody understands to be false, and the people who most need to be brought into the team are the ones for whom performing enthusiasm in front of colleagues is hardest. That combination turns a nice idea into an obligation, and obligation is the opposite of what team building is supposed to produce.
The tell is easy to spot once you know it. If the invitation needs a sentence encouraging people to come, the session is already in trouble, because that sentence exists to counter a reluctance you have correctly sensed and cannot argue away. Something short enough not to need justifying is a better answer than something good enough to be worth defending.
So the single most useful change is usually to make it smaller. Ten minutes at the start of a meeting people were already attending has no attendance problem, needs no defending, and can happen weekly. An hour in the calendar on a Thursday afternoon has to earn its place against real work, and it will lose that argument most weeks.
Timeboxing, and announcing the box out loud
Say how long it will take before you start, and say it in units people can count rather than in minutes. Five questions is a promise the group can watch you keep; a couple of minutes is a phrase that has meant twenty minutes often enough that nobody believes it any more.
Then finish early. A session that ends while people are still enjoying it is one they will agree to again, and the instinct to squeeze in one more round is the single most reliable way to convert a good activity into one that outstayed its welcome. This matters more remotely than in person, because a call has no natural drift-away point — people are trapped in it until someone ends it.
Teams spread across time zones
A distributed team has a structural fairness problem that nobody usually says out loud: whatever hour you choose, somebody is doing this at seven in the morning or nine at night, and it is almost always the same people. If the session is genuinely valuable, that cost lands repeatedly on the same colleagues, which is a worse outcome than not running it.
Two fixes, and neither is exotic. Rotate the time so the inconvenience moves around the team, and say explicitly that you are doing so, because the rotation only builds goodwill if people notice it. Or attach the activity to a meeting that already happens at that hour, which spends no new goodwill at all.
| What you have | What to run | Why that one |
|---|---|---|
| 5 minutes on an existing call | This or That | No setup, no scoring, stops on the agenda |
| 15 minutes, mixed team | Would You Rather | Participation without disclosure |
| A booked hour | Fake News Factory | Real scoring and a genuine ending |
| A small, settled team | Odd One Out | Rewards knowing how colleagues talk |
| A team that never mixes | Team Generator | Cuts across the groups that already talk |
The person who did not want to be there
Every remote team has at least one, and they are usually treated as the problem to be solved. They are better understood as the constraint the activity has to satisfy, because an activity that works for them works for everybody, and one that only works for the enthusiastic half was never team building — it was a reward for the people already comfortable.
In practice that means three things. Nobody has to speak first, so there is no round-the-call opening question. Nobody has to be funny on demand, because required humour is the most exposing thing you can ask of a quiet person. And passing is available, stated out loud before the first question rather than after somebody visibly needs it.
It is worth saying that this costs the session almost nothing. A group given permission to pass uses it far less than you would expect — the permission does the work, not the passing.
What to skip
- Anything requiring people to post something to each other in advance. Half the team will not have received it, and the session becomes about the post.
- Anything where opting out is visible. Optional participation that everyone can see is not optional.
- Anything depending on general knowledge weighted to one country, on a team that spans several. It reads as a quiz about who is local.
- Anything needing a facilitator's script to work. If it cannot be run by whoever called the meeting, it will be run once by someone paid and then never again.
- Scheduling it against real deadlines. A team under pressure experiences the activity as evidence that leadership does not know what the week looks like.
Common questions
- What are good virtual team building activities that need no facilitator?
- Question-based games run from one shared screen: the person who called the meeting reads a question and the team answers in the chat or aloud. Would You Rather is the most reliable for a mixed team, and Fake News Factory is the one worth booking a proper hour for.
- Why does virtual team building usually fail?
- Because it is scheduled by someone with authority, attendance is optional in a way nobody believes, and the colleagues who most need including are the ones who find performing enthusiasm hardest. The fix is usually to make it much smaller rather than better.
- How long should a virtual team building session be?
- Shorter than you think, and finished before people want it to end. Five to ten minutes attached to a meeting that already exists beats an hour in the calendar, because it needs no defending, nobody has to opt in, and it can happen every week instead of once.
- How do you handle a team spread across time zones?
- Rotate the hour so the inconvenience moves around the team rather than always landing on the same people, and say explicitly that you are rotating it — the goodwill only accrues if people notice. Better still, attach it to a meeting already happening at that time.
- What about people who clearly do not want to take part?
- Treat them as the constraint rather than the problem: an activity that works for them works for everyone. That means nobody speaks first, nobody has to be funny on demand, and passing is announced as allowed before the first question rather than after someone needs it.
- How should you split a remote team into groups?
- Deal them randomly rather than letting people choose. A remote team self-selects along exactly the lines the activity was meant to cross — the four people who already speak daily will group together, and the newest joiners will end up with each other.