What is Protect the Castle?

Protect the Castle splits the room into even teams, each one defending a taped-off castle from foam balls launched by every other team. Teams plan their defense, then take turns — or all go at once — launching projectiles at rivals' castles while keeping their own standing. Play runs across multiple rounds, with breaks in between for teams to adjust strategy and swap roles.

It works because the game splits into two distinct skills. The planning phase rewards quiet strategists who think through angles and cover, and the execution phase rewards whoever adapts fastest once the first round exposes what didn't work. A team that nails the plan but never adjusts loses to a team that starts rough and gets sharper every round.

It needs open floor, room for several team-sized castles, and players who can throw and duck — skip it for a seated meeting or a room without space to spread teams out. And skip it for remote teams entirely: the whole game runs on physical castles and thrown objects, so there's no video-call version.

The rules

Split into even teams, and mark each one a castle with tape or an object.
Foam balls or other soft objects are the only projectiles.
Throws only happen from behind a shared launch line — no crossing it.
Hand-blocking and deflecting are allowed only inside a set perimeter around your own castle.
Decide the win condition upfront — usually last untouched castle standing, or first team to hit every other castle.
Play runs in multiple rounds, with breaks between them to refine strategy and swap roles.

Before you start

Team size: 3–10 players per castle. Split your 6–30 participants into even teams within that range — more, smaller teams for a bigger room, fewer, bigger teams for a tight one.
Materials: foam balls, tape or chalk, markers. Cones or boxes are optional extras — they give teams something to build cover around if you want more complex defense.
Mark equal castles and a shared launch line. Every castle should be the same size and the same distance from the line teams throw from. That's what keeps the round fair.
Set penalties before you start. Decide what happens for crossing the line or ignoring a hit, and say it during the rules explanation — not partway through a round.

How to run it

Split into teams and mark castles 3–5 min
Divide the group into even teams of 3–10, then mark each team's castle with tape or an object — same size, same distance from a shared launch line.
Set the win condition and rules 2–3 min
Explain how a team wins — last untouched castle, or first to hit every other castle — plus any projectile limits, round length, and the penalty for crossing the line.
Planning phase 3–5 min
Give teams time to position players and materials around their castle before a single ball flies. This is where the real strategy gets decided.
Launch and defend 10–20 min
Teams launch projectiles at rivals' castles while defending their own — taking turns or going simultaneously, your call. Hand-blocking is fine, but only inside each team's own perimeter.
Refine and rotate 3–5 min
Between rounds, give teams a short break to adjust tactics, swap roles, and — optionally — run a power-up round: a quick challenge or quiz that earns the winner a bonus like extra projectiles or a free shot.
Debrief 5–10 min
Close with a group discussion on what strategies worked, how communication held up, and where leadership showed up during play.

← the castle only falls once.

Facilitator tips

Swap the ball for a foam noodle near mobility limitsIf someone can't dodge or throw easily, hand them a foam noodle instead of a ball, or give them a seated defensive post inside their castle's perimeter.

Post the win condition, don't just say itWrite the rules and win condition somewhere visible before you start — it saves you from re-explaining mid-round and covers anyone who missed the verbal briefing.

Offer a written option for the debriefNot everyone processes a debrief out loud in real time. A written prompt sheet gets quieter voices into the discussion too.

Name a lead per teamOne person calling the plan beats five people improvising separately — assign it upfront instead of waiting for someone to volunteer.

Variations

Smaller castles or limited defenses

Shrink the castle size or cap how many blockers each team gets, and the game gets harder without any new equipment.

Power-up rounds

Between rounds, run a quick challenge or quiz. The winning team earns a bonus — extra projectiles, a shield extension, or a free shot.

Assigned roles

Give each team a designated thrower, blocker, and scout instead of letting roles happen on their own — good for groups that want more structure.

Why it works

Two skills, one gameThe planning phase rewards quiet strategists who think through angles and cover. The execution phase rewards whoever adapts fastest once the first round exposes what didn't work.

Rounds force adjustmentBecause play runs in multiple rounds with refinement breaks between them, a team can't coast on its first plan — the group that revises fastest usually wins, not the group with the best opening strategy.

Setbacks are low-stakes and repeatableGetting your castle hit is a safe, quick way to practice bouncing back — you get another round to fix it in the same session, not weeks later.

HELLO, MY NAME ISJon

"I like that this one splits so cleanly into two phases — the planning huddle and the actual chaos. Watching a team's calm plan get tested by the first hit, and then watching them fix it by round two, tells you more about a group than almost any other activity I run."

Jon Zajac · Founder & Chief Icebreaker

Reflection questions

7 questions for the debrief, once the game's over and the group wants to talk it through.

What strategies did you use to protect your castle?Shows the tactics each team leaned on — a window into their problem-solving approach.
How did communication play a role in your team's success or failure?Puts a spotlight on whether the plan actually got talked through in real time, not just decided by one person.
Did you adapt your strategy during gameplay, and if so, how?Adaptability wins more rounds than the first plan does — this is where that shows up.
What leadership qualities emerged among your team members, and how did they contribute to the group's performance?Names who stepped up, and how — a good prompt for people who don't think of themselves as leaders yet.
How did you balance offensive and defensive responsibilities during the game?Gets at the trade-offs every team makes with limited people and limited time.
What challenges did your team face, and how did you overcome them?A straightforward way into what went wrong, and how the team recovered.
How might you apply what you learned from this activity to other group projects or collaborative efforts?Bridges the game back to how the team actually works together outside the castle line.