The Egg Drop Challenge

The Egg Drop Challenge is a team building classic that has survived decades of trends for one reason: it is genuinely fun, and the moment of truth — watching a homemade contraption fall and either crack or bounce — produces the kind of shared suspense that bonds a group. The task is deceptively simple. Each team gets a raw egg and a limited kit of everyday materials, and a set amount of time to design and build something that will keep that egg intact when it’s dropped from a height. Then everyone gathers to watch the drops.

What looks like a party game is actually a compact lesson in how teams solve problems together. It’s a staple of experiential learning because it forces a team to reason, prototype and commit under pressure — and then gives them immediate, unarguable feedback. The egg either survives or it doesn’t. Here’s how to run it and pull the real value out of the debrief.

What the Egg Drop Challenge is

Teams are given one raw egg and an identical, limited set of materials — things like straws, tape, paper, string, rubber bands, cotton balls, balloons, newspaper and a couple of plastic bags. Working against a clock, they design and build a protective contraption around the egg. When time is up, each contraption is dropped from a fixed height onto a hard surface. The eggs that survive advance; if several survive, you can raise the height, or award the win to the lightest design or the one that used the fewest materials. The constraint is the whole point: everyone has the same kit, so the difference between success and a broken egg is how well the team thinks and works together.

How to run it

• Materials per team: one raw egg plus an identical kit — e.g. 10 straws, one roll-length of tape, a few sheets of newspaper, string, rubber bands, cotton balls, two balloons and two plastic bags. Keep spare eggs nearby.
• Group size: three to six people per team. For a large group, split into as many teams as you need and have them all build at the same time.
• Timing: roughly 45 minutes to an hour total — 5 minutes for rules, 20 to 30 minutes to design and build, 10 minutes for the drops, 10 minutes to debrief.
• The drop: pick one consistent height — a balcony, a stairwell landing or a step ladder — and drop every contraption from the same point onto the same surface. Lay down a tarp for cleanup, keep people clear of the landing zone, and have a neutral facilitator do the dropping so it’s fair.

Announce the rules and the judging criteria up front, start the clock, and let teams work without help. Then run the drops one at a time so every team gets its moment of suspense — the shared holding-of-breath is half the value of the exercise.

What it teaches

Underneath the mess, the Egg Drop Challenge is a tidy model of real project work. Teams have a hard goal, fixed constraints, limited time and no way to fully test their solution until the end — exactly the conditions most real work happens in. That combination surfaces several things at once. It rewards creative problem-solving, because the same kit can protect an egg in a dozen different ways — cushioning, a parachute to slow the fall, a rigid cage, or a structure that crumples on impact to absorb energy. It rewards rapid prototyping, because the teams that build a rough version early and reason about how it will behave beat the ones that argue over the theoretical perfect design. And it forces collaboration under constraints: with only one egg and one drop, a team has to align on a single approach, divide the work, and commit — there’s no room for two half-built ideas.

What to watch for as a facilitator

Watch how teams handle the fact that they can’t practice the drop. Do they reason about the physics — slow the fall, spread the impact, protect the shell — or do they just pile on padding and hope? Notice who proposes the design and whether quieter ideas get heard, how the team decides between competing approaches, and how they react if their egg breaks. The teams that treat a broken egg as information rather than failure are showing you exactly the resilience you want to name in the debrief. Also watch the clock behavior: the groups that leave time to reinforce and double-check almost always beat the ones still building at the buzzer.

Debrief questions

The drops are the fun part; the debrief is where the learning sticks. Try:

• How did you decide on your design — and did everyone actually agree, or did someone just win the argument?
• What did you do to make up for the fact that you couldn’t test a real drop first?
• If you had five more minutes, what would you have changed — and why didn’t you do it?
• How did the team handle the limited materials? Did constraints help or hurt your creativity?
• Where in our real work do we commit to one approach without being able to test it — and how do we de-risk that?

Variations

Once teams know the basic game, you can layer on complexity. Run a materials auction, where teams start with a budget and bid for supplies, so every straw and rubber band has a cost and design becomes an economic trade-off. Add a marketing pitch: before the drops, each team names its contraption and delivers a 60-second pitch, and a panel scores creativity and presentation alongside survival — great for cross-functional groups with sales and product in the room. Other twists include a rising-height “final round” among the survivors, a rule that the egg must be visible during the drop, or a fixed weight limit that rules out simply burying the egg in padding. Each variation shifts what the exercise emphasizes, from pure engineering to communication and persuasion.

Bring the lesson to your team

The Egg Drop Challenge is a reliable way to open a session on creativity, collaboration or working under constraints — and it sits comfortably alongside deeper problem-solving activities. If you’d like a facilitator to run it and tie the lesson back to how your team really operates, or you want more formats to run yourself, explore the activity library. When you’re ready, tell us your goals and we’ll design a session around them.