Alphabet Soup

By James Carter, founder of Building Teams — 25+ years designing team-building experiences for hundreds of leadership teams. Updated July 2026.

See it in action

What it is

Alphabet Soup is a fast, physical race against the clock. Two dozen lettered pads are scattered face-up across a large circle, and the team has to touch them in order — A to Z, or spelling out a word — in the shortest time they can manage. The catch: only one person may be inside the circle at a time, only one letter may be touched per trip, and that person must be all the way back out before the next teammate runs in. So the whole group is in motion, feeding runners in and out, and every second of hesitation shows up on the clock.

Most teams instinctively try to think their way to a perfect plan before they move. But the real lesson here is the one behind almost every business win: you rarely solve it in your head. You make a decision with the information you have, run it, see what the clock tells you, and do it better the next time. The team gets several attempts — and the gap between their first run and their last is where the whole exercise lives.

How it works

The facilitator lays out the lettered pads at random inside a large webbing circle, with a start/finish line set back from it. Time starts when the first runner crosses the line and stops when the last letter is touched and everyone is back behind it. The team plans, runs an attempt, gets its time, and is then given three or four more tries to beat it — usually setting a target time of their own along the way. Because there is real running involved, it doubles as a superb energizer for a group that’s fading after lunch or a long session. (Full step-by-step setup, storylines and debrief questions are in the downloadable guide below.)

What it reveals: continual improvement

This is the heart of Alphabet Soup. A team’s first attempt is almost always slow and clumsy; by the last, a group that’s paying attention can cut its time dramatically. That arc — measure, adjust, re-run, measure again — is exactly how real quality improvement works. It surfaces the difference between a team that treats each attempt as data and one that just tries to do the same thing faster by working harder. The most revealing question in the debrief is simple: what actually changed between your first run and your best one, and why didn’t you see it sooner?

What it reveals: decision-making and trial-and-learn

Watch a team stall on the start line, debating the theoretically optimal route, and you’re watching analysis paralysis in miniature. The clock is unforgiving toward groups that wait for certainty. Teams that commit to a decent plan, run it, and refine from what they learn almost always beat teams that hold out for the perfect one. It’s a vivid, physical demonstration that a good decision made now and improved is worth more than a perfect decision made too late — and that the fastest way to learn is often to act and observe rather than to keep deliberating.

What it reveals: communication

With only one person in the circle at a time, the team’s speed depends entirely on how well everyone else coordinates the sequence — who goes next, which letter they’re grabbing, where it sits. Plans that sound crisp in the huddle fall apart the moment the running starts and nobody can hear each other. You see quickly whether the group built a shared, simple system everyone understood, or a clever plan that lived only in one person’s head. And you can track whether the quality of that communication improves attempt over attempt, or whether the team keeps making the same coordination mistakes at speed.

Interesting things to watch for

• How the group spends its planning time — is it productive, or just talk that evaporates the moment the clock starts?
• How the team decides on its next move: does it genuinely gather input and vote, or does one voice quietly take over?
• Whether the group locks onto its first idea and closes off every other option, even when the times aren’t improving.
• How well everyone actually understands the plan — and whether they’re committed to it as a group or just going along.
• Whether each attempt is treated as a source of information, or the team simply repeats the same approach hoping to be faster.
• How the energy and mood shift between runs — who steps up, who checks out, and what caused it.

Variations

• Have the team set the time they think they need before their first attempt — groups almost always overestimate how fast they can go, which makes a great processing point.
• Give the group five attempts to go as fast as possible, and watch whether they genuinely change tactics or just try to do the same thing quicker.
• Take one or two letters out. Because everyone assumes the letters will all be there, this throws a real obstacle into a familiar task — and surfaces how the team copes when a ‘known’ process breaks.
• Impose silence once anyone crosses the start line, forcing all coordination into the planning phase.
• Rule that no two letters may be touched with the same body part — one hand, then a foot, a toe, a head — adding a constraint that demands a fresh plan.

Who it’s for

Alphabet Soup suits groups of 8 to 32, ideally outdoors or in a large indoor space with room to run. It’s a high-energy, low-cost exercise that fits almost any audience, and its lessons map cleanly onto process and workflow settings — the letters can stand in for steps in a manufacturing line, an administrative paper trail, a distribution channel, or a sequence of patient care. It’s a strong pick for any team focused on continual improvement, communication under pressure, or getting from planning to action faster.

Questions to spark the debrief

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

• How different was your first attempt from your last — and what made the difference?
• What was the quality of your communication, and did it improve over time?
• Were ideas shared, understood, and actually implemented?
• What could you have done to improve your planning?
• How is this activity similar to the way you work?
• In what ways can you apply what you learned here back to your daily work?

Frequently asked questions

How many people is Alphabet Soup for?
Alphabet Soup is built for 8–32 people. We can scale the setup up or down to fit your group.

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

Can Alphabet Soup be run indoors or outdoors?
Outside (Inside only with a large amount of room).

What does Alphabet Soup teach a team?
It focuses on change, communication, problem solving and quality improvement, and the debrief connects what happens in the activity directly to how your team works day to day.

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

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