The role of the Game Master: who holds the experience together while the team plays

Why a cooperative game needs someone outside the game

A cooperative game with asymmetric roles is designed, by nature, to give no one the full picture. That's exactly what makes it valuable — it forces communication — but it also means that if the team gets completely stuck, no one inside the game has the visibility needed to unstick it safely. That's where the Game Master comes in: the person who does see the whole board, in real time, and can step in when needed without ruining the challenge.

What the Game Master sees that players don't

Unlike each player role, who only sees their slice of the problem, the Game Master has full visibility into the session: the state of every system, each role's decisions, elapsed time, and in games like Crisis Room, even the hidden effects of each voting option before the committee discovers them by playing. That full view is what lets them give a useful hint without solving the problem for the team.

When to step in (and when not to)

The hardest skill for a good Game Master isn't having full visibility — it's knowing when to use it. Stepping in too early takes away the team's chance to solve the problem on their own, which is where most of the learning happens. Stepping in too late can create unnecessary frustration if the team has been completely stuck for a long stretch with no progress at all.

A good rule of thumb: give a hint once the team has gone several minutes with no visible progress, and make sure the hint points to where to look, not what to do. "Check whether someone has information about the Pressure system that hasn't been shared yet" is a good hint. "Trip breaker 3" is not — it solves the problem instead of helping the team solve it.

The Game Master also paces the session

Beyond giving hints, the Game Master plays a quieter but equally important role: keeping the session on pace. If a phase is running long, they can flag the time remaining. If they notice a specific role isn't participating (maybe because the rest of the team isn't asking for their information), they can ask the group an open question that invites that role in, without calling them out directly.

Preparing the debrief while the session is happening

One of the most underrated things a Game Master brings is arriving at the debrief with privileged information about the session: the exact moment the team got stuck, which decision changed the course of things, whether someone had key information and was slow to share it. Used carefully, that information turns the debrief from a generic chat into a conversation anchored in very concrete facts the whole team just lived through. We cover how to make the most of this in our guide to facilitating a good debrief.

An example of a good intervention

Picture a session of Profundidad Silenciosa where the team has gone eight minutes without progress: Sonar spotted a suspicious contact but didn't communicate it clearly, and the Helm keeps steering straight toward a mined area without knowing it. A Game Master who steps in too soon would say "there's a mine ahead, change course" — solving the problem instead of letting the team solve it. A good Game Master, instead, asks the group: "does everyone have the same information about what Sonar is currently seeing?" That question doesn't give the answer, but it points the team's attention to exactly where communication broke down, handing the group the chance to solve it themselves.

Who should be the Game Master?

It doesn't have to be the most senior person on the team. In fact, it often works better when it isn't: a Game Master who reports to someone on the team that's playing can feel pressure to intervene differently than they would with full freedom. The ideal person is someone who knows the game well (even if just from having played it before in solo mode with bots) and who has the patience to observe without rushing to fix things.

The Game Master in an organization with multiple teams

If your organization plans regular sessions across different teams, it's worth training more than one person as Game Master and rotating them between sessions. This also keeps a single facilitator from unintentionally becoming a bottleneck as you scale the team-building program to more teams across the company.

Facilitating without ever having played doesn't work well

A common mistake is assigning someone as Game Master without them having played the full session at least once. The best possible preparation is playing the game in solo mode with bots before facilitating it with a real team: it gives a concrete sense of where teams usually get stuck and what kind of hint actually helps at each moment.

The Game Master doesn't replace the debrief, it sets it up

It's a mistake to think that if the Game Master did their job well during the session, the debrief becomes unnecessary. They're two different moments with two different purposes: during the session, the Game Master keeps the pace and gives targeted hints; in the debrief, that same person (or someone else) turns what was observed into an explicit conversation with the team. A Game Master who intervenes well but then skips the closing conversation leaves half the value of their work unused.

Building Game Masters in your organization

If you're thinking about a sustained team-building program, investing in training good internal Game Masters is one of the highest-return decisions you can make. Check out the platform and start by practicing the role yourself before facilitating the first session with your team.