The Constraint Tower | Games for Trainers

Give three teams the exact same materials. Give them the exact same goal. Then quietly hand each team a different hidden constraint — and just watch. The Constraint Tower is one of those activities that tells you more about how people actually work together than anything they could say about themselves in a discussion. And the debrief almost runs itself, because everyone in the room just watched it all happen live.

The setup is simple. What it surfaces is not. On paper, three teams with the same materials building the same thing should get similar results. In practice, the hidden rules each team is working under change everything. Every single time.

How the game works

Split your group into teams of four to six. Everyone gets the same kit — index cards, tape, a ruler, and a small weight to balance on top. The goal is the same for all of them: build the tallest freestanding tower that can hold the weight for thirty seconds.

But each team also gets a sealed card that only the team leader reads privately. It contains a hidden constraint — something that changes how they can work, without the other teams ever knowing. Maybe they can only use half the materials. Maybe one person cannot speak during the build. Maybe touching a specific piece of tape triggers a time penalty. Nobody else in the room has any idea.

"What you see during the build — who steps up, who goes quiet, who finds a way through — is completely real. That's what makes the debrief so good."

Teams build. Towers go up. Some don't. Then you do the reveal — each team leader reads their constraint aloud. The room suddenly realises that what looked like one team being more skilled or more motivated was actually just different teams playing by completely different rules. That moment of realisation is the whole point of the game.

The hidden constraint types — and what each one reveals

The constraint you choose shapes what the game surfaces. Pick based on what you're trying to explore — or give different constraints to different teams so the debrief covers a wider range of behaviours.

Resource Constraint

Limited materials or budget

Shows how a team handles not having enough. Who pushes for what they need? Who lets things go? Does the group find a smart way through, or do they get stuck going in circles?

Communication Constraint

One member cannot speak

Shows what happens when someone in the group can't participate in the usual way. You quickly see who notices, who adjusts, and who just keeps going without realising someone has been left out.

Process Constraint

Must include a specific element

Reflects what most people deal with at work all the time — you have to do it a certain way, like it or not. It's interesting to see whether teams find ways to work within the rule or spend energy pushing against it.

Information Constraint

Only the leader knows the goal

One of the most telling constraints. When only one person knows what winning looks like, you see very quickly what happens to a team without a shared picture of where they're heading.

Time Constraint

Hidden time penalty triggers

Shows how people respond to risk when time is running out. Do they play it safe? Does someone decide to chance it anyway? And who actually made that call?

Role Constraint

No assigned leader

Fascinating to watch. Leadership tends to emerge quickly — but so does the quieter story of who gets talked over. Often a little uncomfortable for teams who consider themselves naturally collaborative.

Why it works — the psychology of pressure and performance

The reason this works so well is that nothing is abstract. Teams are not talking about how they would handle pressure — they are actually handling it, right in front of you. The behaviour you see during the build is genuine. And genuine behaviour is much harder to brush off in a debrief than something someone described from memory.

The hidden constraint is what makes this more than just a fun team activity. While Team A is building steadily, Team B is struggling — and from the outside it looks like a confidence or capability gap. The reveal flips that. The room realises Team B was not less capable. They were just working under completely different rules. Most people take that thought straight back to their actual jobs.

There is also something about building with your hands that loosens people up a bit. The usual professional composure drops away and you see things you would not normally see. Who takes charge. Who goes quiet. Who keeps trying different approaches when something fails. Because the whole room watched it happen, you can name those moments in the debrief without anyone feeling singled out.

How to run it — step by step

Prepare identical material kits

Each team gets exactly the same things: 20 index cards, 60cm of tape, a small weight (a coin or eraser works well), and a ruler. Keep the kits truly identical — if one team can see they have obviously less than another, it breaks the whole mechanic.

Assign and seal the constraints

Write each constraint on a card, seal it in an envelope, and give it to the team leader before you brief the full group. They read it privately. Be explicit: they cannot share it with their team. Say it directly to them, not as a throwaway line.

Brief the full group

Tell the full group: tallest freestanding tower, holds the weight for 30 seconds, 20 minutes to build. Mention that team leaders may have some additional information. Leave it at that. The ambiguity is deliberate — don't fill it in if people ask.

Observe, don't intervene

Walk around and watch. Take a few quick notes — who is leading, who goes quiet, how decisions are made, where things get tense, how people respond when something fails. You will use these in the debrief and you will not remember the specifics unless you write them down.

Measure and reveal

Measure the towers. Mark the winner. Then ask each team leader to read their constraint aloud to the room. Watch what happens — there is usually a moment of genuine surprise followed by a lot of nodding. That reaction is what you have been building toward.

Debrief with precision

Use the specific things you noted during the build. Talk about what you actually saw — not general impressions. Connect it directly to whatever your session is exploring. And name behaviours, not people, unless someone brings themselves into it.

The debrief questions that unlock the most

Debrief Framework

Q

Before you heard the other teams' constraints — what did you assume was going on with them?
Q

How did your constraint change the way your team worked — and did everyone actually understand why things felt the way they did?
Q

Back at work — where are you working under constraints that the people around you probably have no idea about?
Q

And where might you be judging how someone else is performing without knowing what they are actually dealing with?
Q

If you ran this again right now — same materials, same constraint — what would you actually do differently?

Adapting the Constraint Tower to different contexts

Workshop Adaptations

Where this game travels well

Leadership and management development: Give a team the constraint where only the leader knows the goal. What comes out of that debrief conversation about direction and communication is almost always something participants are dealing with in their actual roles.
Team effectiveness workshops: Run it with the real team rather than reshuffled groups. Watching your actual team operate under pressure shows things that no discussion about collaboration ever does. It works well at the start of a team programme because it gives everyone an honest shared reference point.
Change management: Frame each constraint as something participants would recognise from real life — a budget cut, a headcount freeze, a rule from above that nobody can change. Then talk about how we respond to constraints we did not choose and cannot get rid of.
Cross-cultural or global team programmes: The silent-participant constraint tends to be especially interesting in multicultural groups, where what counts as respectful participation varies a lot. One person's careful restraint is another person's being excluded. Name those differences in the debrief.
Innovation and creativity workshops: Use the must-include constraint to look at what happens to creativity when there is a rule you cannot negotiate around. There is usually a good conversation in the difference between constraints that block people and constraints that focus them.
Virtual delivery: You can run a version online using Miro or MURAL with virtual building blocks and digital constraints. It takes more setup than in person, but the things it surfaces — especially around communication and decision-making in distributed teams — can be even more relevant for remote groups.

What to watch for as a facilitator

The first five minutes are the most useful ones to watch. That is when teams are working out how to work together before the task takes over. Who sets the direction? Who just goes along? Who has something to say that no one picks up on? Those early patterns usually carry through the whole build.

Do not rush the reveal. When each team reads out their constraint, give the room a moment before you say anything. People almost always make the connection themselves — and when they do, it lands much harder than if you explain it to them.

Talk about what you saw, not what you think it means. "Two people in that team stopped contributing about halfway through" opens a conversation. "That team had an engagement problem" closes one. Stick to the observation and let the room draw the conclusions.

The takeaway

This game has staying power because it is honest. It does not ask people to imagine a scenario or discuss a case study. It gives them an actual experience — twenty minutes of real pressure, real decisions, and real group dynamics — and then asks them to look at it together. The tower that fell over is not a metaphor. It actually fell over. Everyone saw it. That is a very different starting point for a conversation.

The quality of the debrief comes down to how closely you watched during the build. The most useful moments are the specific things you noticed — the person who had the right idea at the wrong time, the leader who never checked in, the point where someone changed tack entirely and it worked. Those details are what turn a good activity into something people are still thinking about on the way home.

Pay attention during the build. That is really the whole job.