Orange Ball Race

What it is

The earth is about to be hit by an asteroid, and only one ship can launch before impact. Your team has to load its cargo — a pile of oranges — onto the ship faster than the team beside you. Every person must handle each orange as it travels down the line, a few positions carry odd constraints (a pass over the left shoulder here, a left-hand-only rule there), and if a single orange hits the floor it goes all the way back to the start. Orange Ball Race is a fast, funny, high-stakes relay that looks like pure chaos and turns out to be a precise lesson in roles, efficiency and nerve.

Underneath the scramble, the activity shows something every team needs to feel rather than be told: that each person’s role and responsibility genuinely matters, that efficiency comes from everyone becoming a reliable link in the chain, and that dropped oranges — mistakes — are part of learning, not something to fear. We use oranges on purpose: they survive a few drops, and if things go well you can eat the evidence afterward.

How it works

Two teams race side by side. Each gets a set of oranges that has to end up in a box at the end of its line, with every member touching every orange along the way and a handful of quirky handling rules mixed in to trip up the careless. Drop one and it restarts from the first person. Teams get a few minutes to strategize before the countdown, and the first team to load its ship — cleanly — survives the asteroid and wins the prize. (Full step-by-step setup, the exact handling rules and the debrief questions are in the downloadable guide below.)

What it reveals: communication

The winning move is almost never speed — it is a plan the whole line actually understands. In the few minutes before the countdown, teams have to agree on a strategy: line or circle, who stands where, how the awkward rules get handled, what happens the moment an orange drops. Watch what happens next and you see a team’s real communication habits in miniature. Did everyone hear the plan, or did two loud voices settle it while the rest nodded along? When the pressure hits and oranges start falling, does information keep flowing calmly down the line, or does the plan dissolve into people shouting over each other? The same breakdown that costs a team a round here — a plan understood by the planners but never truly shared — is exactly what stalls projects at work.

What it reveals: competition vs collaboration

Two teams, one prize, and a dramatic story make the competitive instinct kick in hard — which is precisely what makes the debrief interesting. The race is framed as us-against-them, and teams throw themselves into beating the group next to them. But nothing in the setup says the two teams can’t compare notes, share a smart handling trick, or even question whether “winning” had to mean someone else losing. Almost no one thinks to. That reflex — treating a challenge as zero-sum by default — is worth naming, because it shows up between departments and teams that are supposedly on the same side. The activity gives a team a safe, memorable moment to notice the difference between competing with each other and competing against each other, and to ask which one their day-to-day actually calls for.

What it reveals: roles, efficiency and mistakes

Because every person is required to handle every orange, no one gets to be a spectator — the slowest or least-confident link sets the pace for the whole team, and that becomes obvious fast. Good teams stop trying to make everyone identical and start playing to strengths, smoothing the handoffs, and protecting the tricky positions. And then there are the drops. A single dropped orange sending the whole run back to the start is brutal — but it is also the point. Teams that treat each drop as a disaster tense up and drop more; teams that shrug, reset and adjust get faster. Learning to treat mistakes as feedback rather than failure is one of the most transferable things a group takes away from the hour.

Interesting things to watch for

• How the team sets up: a line, a circle, something else — and whether both teams land on the same structure or invent very different ones.
• How the team absorbs the odd handling rules and differing responsibilities — who adapts, and who needs the plan explained twice.
• Cheating. It happens under time pressure; there is no need to stop it in the moment, but it is gold for the debrief — explored as a neutral question to the whole group, never aimed at one person.
• What a team does after its first dropped orange — blame and tighten up, or reset and problem-solve.
• Whether anyone ever considers cooperating with, or learning from, the other team rather than only racing it.
• Who goes quiet. Under pressure, some members withdraw from the strategy entirely — and just like at work, the question is whether the quiet ones ever got a real chance to be heard.

Variations

The exercise scales in difficulty and focus depending on what you want to surface. Blindfold some or all of the participants to force reliance on verbal coaching. Silence the louder voices — or everyone — which makes strategizing genuinely hard and reveals who steps up when the usual talkers can’t. Or hand each person a slip with a private role or ‘agenda’ they must fulfil without telling teammates what it is, so the group has to work out how the hidden constraints fit together. Each twist sharpens a different lesson, and the harder versions tend to be the most fun — within reason.

Who it’s for

Orange Ball Race suits groups of 8–35, split into competing teams of roughly 10–20, and runs indoors or outdoors in about 45–60 minutes including the debrief. Its medium energy and light-hearted, high-stakes story make it a strong fit for teams that need to feel the value of clear planning, dependable roles and a healthy relationship with mistakes — and for groups where the line between competition and collaboration is worth a conversation.

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?
• How did the team deal with the differing responsibilities of each member?
• How was planning for this ‘game’ different from how you plan at work?
• What did dropping an orange and starting over feel like — and how does that compare to how mistakes get treated on the job?
• Did you ever consider working with the other team instead of only against them? Why or why not?
• How does what happened here relate back to your life at work?

Frequently asked questions

How many people is Orange Ball Race for?
Orange Ball Race is built for 8–35 people. We can scale the setup up or down to fit your group.

How long does Orange Ball Race take?
Allow about 45–60 min (incl. debrief). Most of the real value comes from the debrief that follows.

Can Orange Ball Race be run indoors or outdoors?
Indoors or outdoors.

What does Orange Ball Race teach a team?
It focuses on communication and competition vs collaboration, and the debrief connects what happens in the activity directly to how your team works day to day.

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

Want a facilitator to run Orange Ball Race for your team? Explore our team building experiences and ongoing programs.