Marshmallow Challenge Instructions, Rules, and Debrief Tips

Updated: June 11, 2026

You want a crisp, reliable way to energize a room, sharpen collaboration, and teach rapid prototyping without a lecture. The Marshmallow Challenge does that in under 30 minutes when it’s run well. Below is the practical field guide: exact setup, clean rules, facilitation language, debrief moves that land, and variations that keep it fresh.

At a Glance

• Goal: Build the tallest free‑standing structure that supports a whole marshmallow on top.
• Standard kit per team: 20 spaghetti sticks, 1 yard tape, 1 yard string, 1 marshmallow. Marshmallow Challenge instructions. (marshmallowchallenge.com)
• Time limit: 18 minutes. Official guidance. (marshmallowchallenge.com)
• Why it works: It rewards early testing and iteration. See Tom Wujec’s TED Talk. (ted.com)

What the Marshmallow Challenge is and why it works

A team exercise where small groups race to build the tallest structure that can hold a marshmallow on top. It looks simple. It quietly surfaces group norms, planning habits, and how teams deal with uncertainty.

A pattern we keep seeing: teams that test early, learn the marshmallow’s real weight, and adjust quickly tend to win. That is the whole lesson in miniature.

Tom Wujec popularized the challenge and its findings. If you want a quick primer to share ahead of time or after the run, point people to his TED talk. (ted.com)

Key materials, time, and room setup

• Per team: 20 sticks of uncooked spaghetti, 1 yard of string, 1 yard of masking tape, 1 whole marshmallow. Source: the official Marshmallow Challenge site. (marshmallowchallenge.com)
• Organizer tools: Timer or projected countdown, measuring tape, camera, music playlist that ends at 18 minutes. Official guidance. (marshmallowchallenge.com)
• Room: Tables with enough spacing so tall structures do not interfere. A visible rules slide or whiteboard helps keep teams honest.
• Teams: 3 to 5 people works well. Keep teams balanced by mixing roles and personalities.

Pro move: bag each kit in a paper bag so distribution is instant and nobody starts early. It also adds a small reveal moment. (marshmallowchallenge.com)

Step‑by‑step facilitation instructions

Use this like a run sheet. Light, fast, precise.

1) Welcome and frame, 60 seconds. “Your task is to build the tallest free‑standing structure that can support a whole marshmallow on top. You have 18 minutes. Tallest wins.”

2) Show the rules, 60 seconds. Keep them big and visible. Repeat once. Ask, “Any clarifying questions now?” Then close questions.

3) Hand out kits, 30 seconds. One kit per team. Do not let anyone open early.

4) Start the 18‑minute timer. Say, “Time starts when I say go. Ready… go.” Play music at a normal volume. Keep an eye on safety with tape dispensers and scissors if provided. (marshmallowchallenge.com)

5) Facilitate lightly during the build. - Call time at 15, 10, 5, 2, and 0:30. People lose track when focused. - If a team is frozen in planning, a quiet nudge like “Try a quick test of the marshmallow now” usually breaks the stall. - Resist the urge to suggest designs. Your job is conditions, not architecture.

6) Hands off at zero. At the horn, say “Hands off the structure. Step back.” Disqualify only if someone is supporting it. Keep it light, not punitive. Official rule: must stand on its own at the end.

7) Measure and celebrate. Measure from table surface to the top of the marshmallow. Photograph winners. Recognize creative approaches that worked or almost worked.

8) Quick reset and debrief. Have teams leave their structures up for the first couple of questions so everyone can reference real decisions they made.

The official rules, clarified

The clean ruleset avoids arguments and keeps focus on learning.

• Goal: Tallest free‑standing structure wins. Measure from table surface to the top of the marshmallow. (marshmallowchallenge.com)
• Use only what’s provided: spaghetti, string, tape, and 1 whole marshmallow. No hidden extras from pockets or the room. You can cut string and tape and break spaghetti. You do not need to use everything. (marshmallowchallenge.com)
• Whole marshmallow on top: Do not cut or eat it. If it is not whole and on top at the end, the structure does not qualify. (marshmallowchallenge.com)
• Free‑standing at time: At 18:00, no hands, bodies, or external supports. If it falls after time is called but before measuring, it does not count. (marshmallowchallenge.com)
• Time: 18 minutes is the standard. Keep it consistent across all teams. (marshmallowchallenge.com)

How to measure, score, and break ties

• Measuring: Use a retractable tape. Place the end at the table surface next to the base. Measure to the highest point of the marshmallow, not spaghetti tips above it. Photograph as evidence if bragging rights matter.
• Scoring: Highest team wins. Consider small recognitions for “Most Improved,” “Most Elegant,” or “Best Prototype Under 10 Minutes.”
• Tie‑breakers: If exact heights match, use time to stability: which stood unsupported first in the last minute. If still tied, smallest material usage wins.

Facilitation pro tips from real events

• Say the word “test” early. Many teams skip it until the last minute. A gentle reminder at minute 12 saves heartbreak at minute 17:55.
• Keep energy steady, not frantic. Music helps pace without turning the room into chaos. End the playlist at 18 minutes to create a clean stop. (marshmallowchallenge.com)
• Stand where you can see wobble. You will spot the moment a team needs a micro‑cue to check top weight.
• Name the constraint clearly. “The marshmallow is heavier than you expect.” That single sentence often triggers a mid‑course correction. (marshmallowchallenge.com)
• Protect fairness. Visible rules reduce the “we thought we could…” debates. Keep a spare marshmallow for any that get squashed before time. (marshmallowchallenge.com)

Debrief questions that actually produce learning

What usually shifts the dynamic is the debrief. Keep it short, specific, and tied to behavior you just saw.

Start with facts, then interpretations, then applications:

• Facts: What did you try first? When did the marshmallow first touch the structure? What changed after that?
• Process: Where did you adapt quickly? Where did you cling to a plan that was not working yet?
• Collaboration: Who pulled the team forward at a stuck moment, and how? Who asked a question that changed direction?
• Assumptions: Which assumptions turned out wrong? How fast did you learn that?
• Transfer: Where at work do you have a “marshmallow” you have not tested yet?

To connect the exercise to team norms, bring in psychological safety without a sermon. Google’s Project Aristotle found psychological safety to be the strongest factor in team effectiveness. A quick bridge like “What made it easy or hard to speak up with a different idea in minute 8?” gets you there fast. See the re:Work guide on team effectiveness for a concise explanation and prompts. (rework.withgoogle.com)

Common mistakes and how to prevent them

• Saving the marshmallow for the last minute. Fix: top a quick stub early, learn the sag, adjust.
• Over‑planning. Fix: build a 90‑second prototype first, then improve.
• Anchoring on one design. Fix: run two micro‑paths in parallel for five minutes, then converge.
• Heavy top section. Fix: lighter platform, wider base, triangulation, guy‑lines with string.
• No time calls. Fix: facilitator calls at 15, 10, 5, 2, 0:30. Teams self‑announce at 5 minutes.
• Hands on at the horn. Fix: rehearse “hands off, step back” once before starting.

Useful variations for different groups and formats

• Two‑round iteration: 10‑minute first build, 5‑minute teardown and reflect, 12‑minute second build. Score only the second. The learning curve is visible.
• Silent start: First 3 minutes with no talking. Forces quick alignment on a first design before debate.
• Resource auction: Start short on string and tape, then sell more at minute 8 for tradeoffs.
• Remote or hybrid: Mail or courier kits in advance, or have local captains source materials. Use webcams aimed at the build area, a shared 18‑minute countdown, and photos for measurement. The same rules apply.
• Stretch target: Award a “prototype tested earliest” ribbon for the team that first supports a marshmallow for 5 seconds. It rewards the right behavior.

A well‑known insight from the field: kindergarteners often outperform MBA teams because they prototype immediately and avoid power jockeying. Use this not to dunk on adults but to celebrate the habit you want: early, repeated tests. See Wujec’s talk for the original framing. (ted.com)

Run it with Scavify: an easy digital layer

When you want automatic timers, photo proof, and a live leaderboard without juggling screens, Scavify’s challenge format fits naturally. Create a mini‑track for the build and another for the debrief insights. Browser or app, it scales to dozens or hundreds of teams in one room or across time zones.

Here are example in‑app prompts that pair well with the Marshmallow Challenge:

• [Photo | 50 pts]: First successful marshmallow-on-top test, timestamp visible.
• [Video | 75 pts]: Wobble test: 5‑second hands‑off stability clip.
• [Q&A | 40 pts]: What assumption changed after your first test?
• [Multiple Choice | 30 pts]: Which fix helped most at minute 10? Base, platform, guy‑lines, or tape joints.
• [Photo | 60 pts]: Final measuring photo, tape at base level clearly shown.

Quick prep checklist

• Kits bagged with 20 spaghetti, 1 yard tape, 1 yard string, 1 marshmallow.
• Projection for rules and a visible countdown.
• Measuring tape ready and labeled scoring sheet.
• Music playlist that ends at 18 minutes.
• Camera for final photos and winner shot.
• Cleanup plan for tape bits and stray spaghetti.

FAQs

How long should the Marshmallow Challenge run?

The standard is 18 minutes. It keeps pressure high enough to force choices without turning it into chaos. (marshmallowchallenge.com)

What exactly counts as “free‑standing”?

At time, the structure cannot touch people, walls, chairs, or props. If a hand supports it when time is called, it does not qualify. (marshmallowchallenge.com)

Do teams have to use all the materials?

No. Teams can cut string and tape, break spaghetti, and use as much or as little as they want. The paper bag is not allowed as a building material. (marshmallowchallenge.com)

How do I measure correctly?

Measure from the table surface to the top of the marshmallow. Do not include spaghetti that sticks up above the marshmallow. Photograph for clarity.

What team size works best?

Groups of 3 to 5 tend to balance speed and coordination. Very large groups slow down with coordination costs.

What are good tie‑breakers?

First to achieve hands‑off stability in the last minute, or least material used. Announce tie‑breakers before you start.

Is there a recommended way to debrief?

Start with what happened, then process, then transfer to real work. Prompt for early testing, adaptation, and speaking up with dissent. If you want evidence‑based framing, see Google’s re:Work guide on team effectiveness for prompts on psychological safety. (rework.withgoogle.com)

Where can I point skeptics for the origin and rationale?

Share the official Marshmallow Challenge site and Tom Wujec’s TED Talk. They cover materials, rules, and the prototyping lesson in plain language. (marshmallowchallenge.com)