Home/Activities/Team Architect

Challenge · A great activity for everyone

Team Architect

Small teams get a pile of mismatched materials, a time limit, and one shared target — a tower, a bridge, an egg that has to survive a drop — then build it before the clock runs out. It works because the target does the judging: a structure either meets the brief or it doesn't, so the room argues design, not opinion.

What is Team Architect?

Team Architect hands small teams a limited, slightly odd pile of materials — popsicle sticks, string, a stray egg, whatever's within reach — and one shared target: build a specific structure, or simply the tallest thing standing when the clock runs out. A timer keeper counts down while teams design, build, and, if you're testing designs, put the result to the test.

It works because the materials do the constraining. A stack of popsicle sticks and a roll of tape burns through the obvious options fast, so a team has to actually collaborate on what's left. Add a real check at the end — an egg drop, a weight test — and the debrief runs on evidence instead of who argued loudest.

Skip it for a room that can't spread out or share physical materials — this is a hands-on build, not something that translates to a video call. It also needs a few minutes of facilitator prep to settle on a target and a materials list before teams walk in; a fully improvised version tends to stall on "wait, what are we building?"

The rules

  1. Choose a space, indoors or outdoors, before teams show up.
  2. Assign one person as the timer and set the build's time limit up front.
  3. Decide the materials — preselected, or whatever's already in the room.
  4. Split into two small-to-medium teams, or a few groups of three or four.
  5. Name the target before the clock starts — a specific structure, an egg-drop rig, or simply the tallest build.
  6. If you're testing designs, every build gets tested against the same standard, and a tie triggers a shorter sudden-death round.

Before you start

  • Group size: 4–16 participants. Two small-to-medium teams work well at the smaller end; split into several groups of three or four once the room fills up.
  • Pick your space. Indoors or outdoors both work — playing outside opens up natural materials like branches and leaves as part of the pile.
  • Decide your materials before teams arrive. Preselect a kit, or point teams at what's already in the room; office supplies like paper clips, tape, and staplers work in a pinch.
  • Name a timer keeper. One person watches the clock and calls time — a phone, an egg timer, or a wall clock all work fine.
  • Decide what's being tested. An egg drop, a weight check, or just the tallest build — state the objective and, if there's a test, what counts as passing.

How to run it

  1. Pick the challenge beforehand

    Decide what teams are building — a specific object, something functional, or simply the tallest structure standing — and whether there's a formal test at the end.

  2. Choose the materials beforehand

    Preselect a kit or point teams at what's available in the room (or outside, if you're playing there). Say it once, clearly, before anyone starts grabbing.

  3. Split into teams 1–2 min

    Sort into two small-to-medium teams, or several groups of three or four, with roughly even numbers on each side.

  4. Brief the room 2 min

    State the target, the materials on offer, and the time limit in one pass, so no team starts building on a misunderstanding.

  5. Build 20–40 min

    Start the timer and let teams design and build against the clock. Encourage them to communicate and adapt when a plan hits a snag.

  6. Test and declare a winner 5–10 min

    If you're testing designs — an egg drop, a weight check — every build gets the same test. Otherwise, judge by the target you named upfront. Break a tie with a shorter sudden-death round: add onto the build, or start something new.

← same pile, wildly different builds.

Facilitator tips

Stock a second set of materialsAdd larger-format alternatives — chunkier blocks instead of popsicle sticks, thick markers instead of fine-tip pens — so fine motor differences don't decide who gets to build.
Brief with a picture, not just wordsPair the verbal brief with a labeled materials photo or a simple sketch so the target lands the same way for visual learners and anyone who processes instructions differently.
Check the space for mobility needsPlaying outdoors or in a room with limited seating? Confirm there's a clear path and room to work for anyone with mobility needs before teams start moving around.
Lead with collaboration, not competitionSay up front that the win is a good build, not the fastest one — it keeps quieter members offering ideas instead of ceding the pile to whoever grabs first.

Why it works

Resourcefulness beats resourcesThe pile is limited and a little odd — string, newspaper, a stray egg — so the win goes to whoever finds an inventive use for what's there, not whoever grabbed the most supplies.
Testing settles the argumentAdd a real check at the end — an egg drop, a weight test — and a build either survives it or it doesn't, so the debrief runs on evidence instead of opinions about whose design looked best.
Plans change mid-buildMaterials run short, a joint won't hold, the timer keeps ticking — teams have to adjust in real time instead of executing a fixed plan, which is where the adaptability actually gets practiced.
HELLO, MY NAME ISJon

I like this one because you can hand six teams the exact same pile of materials and get six completely different builds back. The materials barely matter — what people decide to do with them is the actual show.

Jon Zajac · Founder & Chief Icebreaker

Reflection questions

6 questions for teams that want the debrief, not just the build.

  1. What specific skills did you use to complete the challenge?Turns a vague "that was fun" into an actual list — problem-solving, creativity, whatever people actually did with the pile.
  2. How did your team communicate and work together during the activity?Gets people naming which conversations helped the build and which just ate the clock.
  3. What obstacles did you encounter while building your structure, and how did you overcome them?Surfaces the actual fix, not just the fact that something went wrong.
  4. How did you feel when your team's design was being tested or judged?Names the nerves that come with a public test — useful groundwork for the next time something they built gets evaluated.
  5. What would you do differently if you were to play this game again?A second attempt, asked out loud, before anyone's actually building again.
  6. How can the skills and strategies used during this icebreaker be applied to your work or personal life?Draws the line from the pile of materials to the actual job — the point of running this at all.

Jon Zajac

Founder & Chief Icebreaker

I started IcebreakerSpot because I believe strong connections are the foundation of successful teams. This site exists to make it easy to find and share the icebreakers and team-building activities that build trust, spark collaboration, and help groups do great things together.