Traffic Jam

What it is

Traffic Jam is a classic problem-solving simulation that looks trivial and turns out to be anything but. Two equal teams stand in a line of marked spots — one team on the left, one on the right, facing the middle — with a single empty space between them. The task sounds obvious: the people on the left have to end up where the people on the right started, and vice versa. Then the rules land, the obvious approach dies, and the group discovers it has a genuine puzzle on its hands.

What makes it such a good team exercise is that no one can muscle through it. Traffic Jam is about process, not effort. The team has to slow down, see the whole sequence, and coordinate move by move — which is precisely why it surfaces how a group plans (or doesn’t), how it communicates when it’s stuck, and who steps up to lead when the plan stalls. It is a fast, low-setup activity that fits neatly into a workshop, an offsite or a break in a conference agenda.

How it works

The group forms two lines facing each other across one empty space — on mouse pads, taped X’s, chairs or paper markers, one person per spot. Each team has to cross to the other side, but only ‘legal’ moves are allowed: one person moves at a time, you can only step forward into an empty space, and you can only step around one person who is facing you. No moving backward, no turning around, and no move that shuffles two people at once. Get into a position with no legal move left, and the whole team resets to the start and tries again. (Full step-by-step setup, the marked-square diagram and the move-by-move solution are in the downloadable guide below — try it yourself before you peek.)

What it reveals: process thinking

Most teams charge in. They start swapping people around with no plan, hit a dead end, reset, and charge in again the same way — often repeating the identical failed sequence several times before anyone stops to ask what the pattern actually is. That moment is the whole point. Traffic Jam is really a lesson in cycle-time reduction and thinking “in process”: once a team stops reacting move-to-move and starts seeing the underlying sequence (left one, right two, left three…), the puzzle unlocks and completion time collapses. It’s a vivid mirror of work, where teams so often jump straight to execution without pausing to plan — and pay for it downstream.

What it reveals: communication & structure

The line itself is the lesson. Standing shoulder to shoulder in a fixed order, people can’t easily see or hear the whole group, and the structure quietly shapes how information flows — some voices carry, others get lost at the ends. It sensitizes a team to the communication difficulties that are baked into how a group is organized, not just what its members say. Watching who can coordinate the next move, who goes unheard, and how the group develops a shared shorthand is a direct read on how the same team handles information at work.

What it reveals: leadership

Groups almost always begin leaderless, unorganized and communicating poorly. Then, somewhere in the struggle, a player quietly starts directing traffic and the rest of the team lets them — a manager emerges. How and why that happened is one of the richest questions in the debrief: was it the person with the answer, the loudest voice, or simply whoever was willing to take responsibility? Because the puzzle needs everyone to see the pattern, it’s a natural conversation about shared leadership — the difference between one person carrying the team and the team carrying itself.

Interesting things to watch for

• The team attempts the same idea over and over without trying anything genuinely new — the classic sign of executing without planning.
• A group starts unorganized with no plan, then a leader emerges from the chaos. Note when it happens and who it is.
• Whether anyone stops the action to map the full sequence before moving — and how the mood shifts once they do.
• How closely the planning-versus-execution behavior mirrors what typically happens back at work.
• Frustration and how the team handles it — do people stay in it together, or do a few check out?

Variations

Collaboration vs. competition. With enough people for two groups, run them side by side. Tell them clearly they are not competing and that they may freely share what they learn about solving it — then watch what happens. Almost every time, the groups compete anyway, and the finished team will often gladly offer to help while the struggling team refuses the help, wanting to crack it alone. It’s a pointed, hard-to-argue-with demonstration of how easily — and for how many reasons — collaboration breaks down.

A second time through. If a team nails it, raise the stakes: ask them to complete the task while holding their breath, allowing them to appoint one ‘coach’ who may breathe while assisting. It reinforces the two big takeaways — that teamwork and communication are essential to understanding complex processes, and that teams can make significant process improvements in a very short time by drawing on the expertise of every member.

Who it’s for

Traffic Jam is ideal for groups that need to practice planning before doing, for teams working on cycle-time or process improvement, and for any session where you want a quick, portable puzzle that gets people thinking “in process.” It scales from a single team of eight to a room split into competing groups, needs almost no equipment, and works just as well indoors as out.

Questions to spark the debrief

The activity is the vehicle; the debrief is where the lesson lands. Questions we ask:

• What was your first thought about this event, and what do you think about it now?
• What was the problem? How did you break it down?
• How effective was the team at solving this problem — why or why not?
• What kind of leadership emerged?
• If you were frustrated, what caused it and how did you overcome it?
• Did the team stop to plan any strategy before attempting the task? Would that have helped? Do you see the same pattern at work, where we jump in too quickly without planning?
• How does what happened relate back to your life at work?

Frequently asked questions

How many people is Traffic Jam for?
Traffic Jam is built for 8–20+ people. We can scale the setup up or down to fit your group.

How long does Traffic Jam take?
Allow about 30–45 min (incl. debrief). Most of the real value comes from the debrief that follows.

Can Traffic Jam be run indoors or outdoors?
Indoors or outdoors.

What does Traffic Jam teach a team?
It focuses on problem solving, communication, leadership, critical thinking and decision making, and the debrief connects what happens in the activity directly to how your team works day to day.

Is there a free guide for Traffic Jam?
Yes. You can download a free step-by-step facilitation guide (PDF) for Traffic Jam from this page and run it yourself.

Want a facilitator to run Traffic Jam for your team? Explore our team building experiences and ongoing programs.