What is Pipe Cleaner Pyramid?
Pipe Cleaner Pyramid splits a group into teams of 3 to 5, hands each one a stash of pipe cleaners — usually 50 to 100 per team — and gives them 15 to 30 minutes to design, build, and test whether their pyramid stands on its own, with nothing else holding it up.
It works because pipe cleaners don't hold a shape by themselves — every joint a team bends is a bet on what will still be standing when the timer runs out. That constant, physical negotiation over the base and the angles is where the actual teamwork happens; the pyramid itself is just the scoreboard.
Skip it if the group's fully remote — this needs a shared table and a real pile of pipe cleaners, and the online version trades away most of what makes the physical one work. It's also not a two-minute filler: with real building and testing time built in, it wants the full 15 to 30 minutes to land.
The rules
- Build the tallest pyramid you can, using only pipe cleaners.
- Every team gets an equal supply of pipe cleaners — no borrowing between teams.
- The pyramid has to stand on its own by the end of the build, with nothing else holding it up.
- Build only inside your team's assigned workspace.
- Plan before you start building — sketch a design, or split up who does what.
- When time's up, hands off: pyramids get judged exactly as they stand.
Before you start
- Team size: 3 to 5 works best. Smaller teams keep everyone building instead of watching. Split a bigger group into several teams rather than crowding one pyramid.
- Materials: about 50 to 100 pipe cleaners per team. A mix of colors adds visual interest, and keeping extras within reach means no team stalls out mid-build waiting for more.
- Give each team its own space. Enough room between teams that reaching for a pipe cleaner doesn't mean reaching into someone else's build.
- Bring a timer, and a ruler or tape measure if height is part of scoring. The tape measure is optional — skip it if you're judging on creativity or structure instead of pure height.
- Decide your judging criteria before teams start. Height alone is the simplest version. Add creativity, structural complexity, or aesthetic appeal if you want a richer evaluation.
How to run it
- Introduce the task 1–2 min
Explain that teams are building the tallest freestanding pyramid they can out of pipe cleaners — self-supporting, nothing leaning on anything else.
- Team strategy 2–5 min
Give teams time to plan before anyone builds: sketch a design, assign roles, or just talk through an approach.
- Build 8–15 min
Start the timer and let teams build, adjusting their plan as the pipe cleaners bend and the design does or doesn't hold up. Call out occasional time checks to keep the pace up.
- Countdown 1 min
Announce the end loudly enough for every team to hear, let them finish any last adjustment, then have everyone step back before judging starts.
- Evaluation 2–3 min
Measure and compare the pyramids against whatever criteria you set — height, creativity, structural complexity, or aesthetic appeal.
- Debrief 3–5 min
Ask teams what strategy they used and where it broke down. "What did you change once building started?" usually gets the most honest answers.
← the wobble is where the creativity happens.
Facilitator tips
Variations
Swap pipe cleaners for a collaborative online drawing tool or a block-based building game, and run each team in its own breakout room. Keep the same plan, build, evaluate, debrief flow inside whatever the platform allows.
Score creativity, structural complexity, or aesthetic appeal alongside height for a competition that rewards more than just the tallest build.
Why it works
Reflection questions
The build goes fast — these turn it into an actual conversation about how the team worked, not just what got built.
- What did you learn about yourself during this activity?Gets at problem-solving and creativity — and how each person actually showed up in the group, not just what got built.
- How do you feel about the communication within your team?Communication is most of the game here — this surfaces what worked and what could go smoother next time.
- Did you encounter any challenges or setbacks during the activity? How did you overcome them?Every pyramid wobbles at some point — this gets the fix said out loud instead of left unspoken.
- What strategies did your team use to build the pyramid, and do you think they were effective?Turns "we built a pyramid" into an actual strategy conversation — what held, what didn't.
- If given the chance to do it again, what would you do differently?A second attempt, asked out loud — good for closing on what the team would actually change.