Home/Activities/Sneak a Peek

Challenge · A great activity for everyone

Sneak a Peek

One rep per team gets a timed look at a hidden model, then reports back so the team can build a match from memory and description alone. It works because a description of a physical object always loses something in translation — and watching exactly what survives the trip is the whole game.

What is Sneak a Peek?

Sneak a Peek splits a group of 6–30 into teams of 3–5, then makes a hidden, pre-built model the only source of truth in the room. Each round, one team member gets 10–30 seconds to look at it — no notes, no photos — then reports back so the team can build a match from memory and description alone.

It works because building from a description is a different skill than building from a sight. The viewer has to decide, fast, which details actually matter — shape, color, count, order — and the team has to turn whatever survives that sentence back into a physical object. Rotate a new viewer in for the next round and you get a second opinion, sometimes a correction, sometimes a new kind of wrong.

It needs more setup than most icebreakers on this site — you're building an actual model ahead of time and finding a layout where teams can't see it, or each other's builds, without leaving their seats. Skip it if you're short on prep time, short on table space, or working with a group that's already run a build-from-memory exercise recently.

The rules

  1. Split into teams of 3–5 and hide the model behind a barrier until it's someone's turn to look.
  2. Each round, one team member gets 10–30 seconds to view the model — no notes, no photos.
  3. That viewer returns and describes what they saw; the team builds or adjusts from the description alone.
  4. Build phases run 2–4 minutes before the next viewer takes a turn.
  5. Rotate the viewer role through the team so more than one memory shapes the build.
  6. When time's up, reveal the real model and compare it against every team's version.

Before you start

  • Group size: 6–30 participants. Split into teams of 3–5 people each — enough teams to make the reveal worth comparing.
  • Build the model before the session. Construct it out of building blocks, complex enough to be a real challenge but reproducible in the time you've budgeted.
  • Set up barriers and table placement. Arrange team tables so no one can see the model — or another team's build — without leaving their spot. A folder, screen, or any opaque material works as the barrier.
  • Gather the materials. Building blocks (LEGO or any uniform set works), a timer or stopwatch, and something to serve as a barrier.
  • Ban notes and photos before the first look. Say it up front — whoever takes a peek carries nothing back but memory.

How to run it

  1. Explain the rules 1–2 min

    Walk through the goal, the team roles, and the one rule that matters most: whoever takes a peek carries nothing back but memory.

  2. First team member takes a peek 10–30 sec

    One rep per team gets a timed look at the hidden model — no notes, no photos, nothing but what they can hold in their head.

  3. Team builds from the description 2–4 min

    The viewer returns and describes what they saw; the rest of the team builds or adjusts based on that description alone.

  4. Rotate in a new viewer 3–5 min each

    A different team member takes the next peek, then reports back for another build phase. Repeat for as many rounds as your time allows.

  5. Reveal and compare 3–5 min

    When time's up, bring out the real model and compare it against every team's build before moving into the reflection questions.

← the build only knows what survived the sentence.

Facilitator tips

Offer more than one buildPrep an easier model alongside the main one so first-time builders and LEGO veterans aren't racing on the same track.
Keep descriptions plainCoach viewers toward plain, concrete words over jargon — the team can only build what actually made it into the sentence.
Rotate who gets to lookSend a different person on each viewing round, including the quiet ones — more memories in the mix means a better build.
Reach for tactile piecesTextured or visually distinct blocks make the reveal and comparison work for participants with visual impairments too.

Why it works

Description survives one translation, rarely twoThe viewer converts a shape into words, and the team converts those words back into an object. Watching exactly which details don't survive that round trip is the whole point.
A new viewer changes what gets caughtDifferent team members notice different things — proportions, color, count. Rotating the viewer each round tends to catch what the last one missed, or introduce a new kind of wrong.
The reveal is an instant fact-checkComparing every build to the real model at the end turns "how did we do" into something everyone can see, not just something they report.
HELLO, MY NAME ISJon

"I love the moment a rep comes back and two people on the team swear they remember completely different things. It's proof memory is selective before it's proof communication is hard."

Jon Zajac · Founder & Chief Icebreaker

Reflection questions

For teams that want the debrief — these turn the build into a real conversation about how you communicate under a time limit.

  1. What specific strategies did you use to remember the details of the model during your sneak peek?Surfaces which memory tricks actually worked — worth reusing next time recall is on the line.
  2. How did you ensure clear communication within your team while describing the model?Gets at what made a description land, versus what needed repeating twice.
  3. What was challenging about translating a 3D structure into verbal instructions for your teammates?Names the exact place spatial description broke down — the answer is usually specific.
  4. How did you adapt your approach to building the model as you progressed through multiple rounds?Tracks how the strategy actually changed round to round, not just whether it did.
  5. What insights did you gain about your own communication style or strengths during this activity?A quick self-check on how you communicate under an actual time limit.
  6. How can the lessons learned from this icebreaker activity be applied in real-life situations, both personally and professionally?Moves the exercise out of the room and into Monday's meetings.

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.