A team building city game splits your group into small teams, gives each one a phone, and sends them into the streets of a real city to solve puzzles tied to real places. There is no facilitator standing at a flip chart, no trust fall and no enforced sharing. People walk, argue about an answer, notice a building they have passed a hundred times, and talk to colleagues they never normally sit near.
That is the whole idea, and it is worth being clear about what it does and does not deliver.
How it works in practice
You pick a city and a start point. On the day, the group divides into teams of roughly three to six, small enough that nobody can hide, large enough that people take different roles. Each team follows a route on a phone, solving location-based puzzles and challenges along the way, and scores points as it goes.
There is no fixed departure time and no guide waiting: you start when your group is ready. Most routes run between ninety minutes and two and a half hours, and teams can pause for coffee without breaking anything. At the end everybody arrives at the same place, which is usually a bar or a restaurant, and compares scores.
The how it works page sets out the mechanics step by step.
Why it works better than most team building
Three things do the work, and none of them is the puzzle.
Small teams force participation. In a group of forty, most people say nothing all day. In a team of four with a puzzle to solve, everybody contributes within ten minutes.
Mixed teams break the seating plan. Deciding the teams yourself, deliberately splitting departments and mixing seniority, is the single biggest lever you have over the outcome. Left to themselves, people team up with whoever they already eat lunch with.
Walking makes talking easier. Side by side, moving, with a shared task, is a much lower-pressure way to have a first conversation than sitting opposite someone in a workshop circle.
Group sizes and what changes
Below about eight people, a city game works but the competitive element is thin; it becomes a nice afternoon rather than a team event. Between roughly ten and sixty, it is at its best. Above that, it still works, larger groups just need a bit more thought about start points and the meeting place at the end.
For companies and larger groups we can help with the practical planning: staggered starts, a route that finishes where you have booked dinner, and a scoreboard for the end.
What it costs you, other than money
Half a day, realistically: the game itself plus getting people there and the meal afterwards. It works outdoors, which means it works in the rain but is genuinely less fun in heavy weather, have a plan for a wet November afternoon.
It also requires walking. A typical route covers a few kilometres over uneven city surfaces, and that is a real barrier for some colleagues. Ask the group in advance rather than assuming, and pick a shorter or flatter route where needed. Nobody enjoys being the person who has to opt out on the day.
When something else would be better
Being honest about this matters more than a sales pitch.
If the team has a specific, named problem, two departments that will not cooperate, a manager people do not trust, a merger that has gone badly, a city game will not fix it. A good day out can make people more willing to have the difficult conversation, but it is not the conversation. Facilitated sessions exist for a reason.
If the team is fully remote and rarely in the same country, the logistics of getting everyone to one city are the event, and the game is the small part. That can still be worth it, but be clear about which is which.
And if half the group would rather have the afternoon off, an activity that lasts two hours and ends at a bar is a much easier sell than one that lasts all day.
How to plan one that lands
Set the teams yourself and mix them. Say in the invitation how long it will take, how far people will walk, and where it ends, the two most common complaints about any team event are unclear timing and uncomfortable shoes.
Book somewhere for afterwards. The conversation that makes the day worthwhile usually happens in the first twenty minutes at the bar, when teams are still comparing what went wrong.
And do not over-formalise it. A prize matters less than most organisers think; recognition at the end, in front of everyone, matters more.
Where you can run one
City games work in any city with a walkable centre and enough history to hang puzzles on, which is most of them. You can see every city we currently cover, and if yours is not on the list yet, tell us, we add cities regularly.
Frequently asked questions
How long does a team building city game take?
Most routes run between ninety minutes and two and a half hours, plus whatever you plan afterwards. Teams set their own pace and can stop along the way.
How many people do you need?
It works from about eight upwards and is at its best between ten and sixty. Larger groups are fine with a little extra planning.
Do you need a guide or a facilitator?
No. Everything runs on the phone, so there is no fixed start time and no group waiting for a guide to arrive.
What happens if it rains?
The game still runs, and teams can shelter or pause. In genuinely bad weather it is worth moving the date rather than pushing through.
Is it suitable for people with limited mobility?
It depends on the route and the city. Ask before booking so the route can be chosen accordingly, and ask your own group before you announce the date.
Does it actually improve teamwork?
It reliably gets people talking who otherwise would not, which is a real and useful outcome. It will not resolve an underlying conflict on its own.
Plan one properly
The best team days are the ones with a clear plan and a low bar for taking part. If you want another angle, read outdoor team building activities for work, or get in touch and we will help you shape the day.