What is Spaghetti-Marshmallow Tower?
Spaghetti-Marshmallow Tower is a hands-on engineering challenge in one breath: each team gets a box of uncooked spaghetti and a bag of marshmallows, then races to build the tallest freestanding tower it can before time runs out. The one rule that decides ties: the tower has to hold itself up for at least 5 seconds once the clock stops.
It works because the materials are honest about failure. Spaghetti snaps under its own weight and marshmallows squish instead of holding a joint, so the first plan almost always collapses in the opening minutes — watching a team recover from that, fast, is where the real problem-solving shows up. It also hands every quiet person on the team a job: somebody has to hold the base steady while somebody else finishes the top.
It's built for a room that can spare a table per team and doesn't mind a little mess. For a fully remote group, or a space where food-based materials aren't practical, skip to the variations below — this one needs shared hands on shared materials more than most icebreakers do.
The rules
- Build the tallest freestanding tower you can using only the spaghetti and marshmallows you're given.
- The tower has to stand on its own for at least 5 seconds to count — no holding it up at the buzzer.
- Height is measured from the base to the highest point.
- Break, snap, or cut the materials however you like; nothing from outside the kit.
- Once time's up, hands off — no more building, no more fixing.
- Optional: award a separate point for the most creative or best-looking design.
Before you start
- Group size: 2–6 participants. Split into small teams if the room is on the larger end — even two people can go head-to-head as their own team.
- A box of spaghetti and a bag of marshmallows per team. Portion the materials into equal piles before anyone arrives, so nobody's negotiating for supplies once the clock starts.
- One cleared table per team. Give each team its own flat surface with room to move around it — a crowded table changes the physics problem before anyone's touched a noodle.
- Hide the ruler and the timer until go. Keep the measuring tape and stopwatch out of sight during setup — showing them early turns setup into strategy time you didn't budget for.
How to run it
- Explain the challenge and the one rule that decides it 1 min
Say it in one breath: spaghetti and marshmallows only, tallest tower wins, and it has to stand on its own for 5 seconds when time's called. Everything else is up to the team.
- Form teams and hand out materials 1–2 min
Split into small teams and give each one its box of spaghetti and bag of marshmallows. Keep the tape measure and timer back until this moment — equal materials, revealed at the same time, keeps it fair.
- Start the clock and build 15–30 min
Let teams design, test, and rebuild for the full window. They can break or cut anything they were given; once time's up, no more touching the tower.
- Measure and confirm the stand 1 min each
Measure base to highest point with the tape measure, and check the tower holds itself up for the full 5 seconds before you record a height. A tower that topples during measurement doesn't count.
- Optional: stress test and award creativity 3–5 min
If you want a second round, put each tower in front of a fan for a light wind test. Consider a separate point for the most creative or best-looking design, apart from height.
← the marshmallow always goes on last for a reason.
Facilitator tips
Variations
Hand out less spaghetti and fewer marshmallows than the full kit — the same challenge gets tougher and the tradeoff conversations get sharper.
Add tape or string for a team that's already run the classic version — a new joint option changes the whole design problem.
Keep the same materials and the same clock, but call for a bridge or another structure instead of a tower.
Why it works
Reflection questions
For classrooms and trainings that want the debrief — a few minutes of these turn the build into an actual conversation about how the team works.
- What strategies did your team try during construction?Surfaces the plan before the pivots — and which pivot actually worked.
- How well did your team communicate under the clock?Points straight at collaboration gaps without anyone having to name them first.
- What unexpected problem came up, and how did you handle it?Every tower hits one. This is where the adaptability story lives.
- How did your team divide the work?Surfaces who led, who built, and whether that split felt fair to everyone.
- What's the one creative idea you're proud of?Celebrates the move that worked, even on a tower that didn't win.
- Where else could this kind of planning under pressure show up at work?Connects the exercise back to Monday morning, which is the actual point.