What to Do When a Training Scenario Goes Sideways: A Facilitator Intervention Guide

Two players are min-maxing the marching order like it's a spreadsheet. A third is checking Slack under the table. Somebody just described the scenario's central betrayal as "a fun little puzzle." You've got two hours left, a room of adults you promised this wouldn't waste their workday, and a growing suspicion that nobody is practicing anything.

When a training scenario goes sideways, the fix is nearly always the same shape: diagnose which failure mode you're looking at, then intervene from inside the fiction instead of stopping the game to correct people. Most training facilitation problems at the table reduce to six patterns – players treating it as just a game, players who never consented to the fun, one voice driving every decision, a conflict-avoidant participant retreating deeper, a group performing for your approval, and a table that's simply gone flat. Each has a different cause, and each has a specific move.

Adam White and I built Operation Aetherfall, a tabletop RPG conflict-training scenario, and ran it through two full pilots. Adam is a licensed professional counselor and a Game to Grow-trained game master; I'm a product manager, not a therapist. The interventions below come from the research base under the program – 11 reports synthesizing more than 200 academic sources – plus what the two of us learned watching real tables wobble. The full run-of-show lives in our guide to how to run a tabletop RPG training session. This article is for the moment mid-session when the plan stops working and your palms start sweating.

How do you know when to step in?

Two signals reliably justify intervention: overload and underload. The cognitive load research on simulations says to step in when you see confusion, paralysis, or repeated errors – too much – and when you see disengagement and off-task behavior – too little. Nearly everything between those poles is productive struggle, and productive struggle is the learning. Leave it alone.

You also have more permission to interrupt than you probably think. A 2019 randomized controlled trial with 50 medical students compared stop-and-go debriefing – pausing the scenario to discuss – against saving everything for the end, and found no difference in skill acquisition. Learners in rapid-cycle simulation training go further: they report the interruptions are where they learn the most. The old dogma that a scenario must never be paused doesn't survive contact with the evidence. What matters is how you interrupt, not whether.

And one rule sits above all of it. During play you're balancing three priorities – game flow, learning moments, psychological safety – and when they conflict, safety wins. Every time.

What are the six failure modes of a training scenario?

Every mid-session breakdown we've watched maps to one of six patterns. Here's the diagnostic table; the details follow.

Symptom	What's actually happening	The move
Jokes, min-maxing, nobody takes the conflict seriously	Overdistance – the fiction is too far from anything real	Raise the stakes inside the game world
Visible discomfort, going through the motions	Reactance – participation wasn't genuinely voluntary	Offer a real ramp down: observer or advisor role
One or two players drive every decision	Dominance – the structure permits it	Spotlight shift; lean on hidden information
An avoidant participant goes quieter with each conflict	The game is confirming that conflict is dangerous	Lower the intensity; side-coach gently
Players watch your face and ask what you want	Training scars – they're learning compliance, not skill	Stop rewarding answers; let consequences play out
Energy drains, pace slows, phones appear	Underload – challenge has dropped below skill	Tighten time pressure; drop new information

"It's just a game" (overdistance)

The symptom is a table having a great time and practicing nothing: jokes over every consequence, characters played like action figures, decisions made by the math instead of the situation. What's actually happening is a distance problem. Fictional distance has a Goldilocks zone – too close to your real workplace and people feel exposed, too far and they treat the whole thing as entertainment. A group deep in "just a game" mode has drifted past the far edge. (We've written more about how aesthetic distance makes roleplay work.)

The intervention isn't a speech about taking things seriously. Out-of-frame scolding collapses the fiction and buys you compliance at best. Raise the stakes inside the game world instead: let a consequence land on something the characters care about, then have an NPC name the cost of the last flippant decision and ask what the team intends to do about it. Consequences that bite do what no lecture can, and the debrief bridges the rest back to the workplace later.

Forced fun (reactance)

This symptom is quieter: minimal answers, stiff body language, a person visibly enduring the session. It's a consent problem, not an attitude problem. The research is blunt that mandatory participation backfires, and role-play asks for a kind of vulnerability some people never agreed to give – especially in front of coworkers.

The move is a ramp down, offered without ceremony. Observer and advisor roles are real roles, watching for specific dynamics or counseling the players between scenes. Restate out loud that anyone can shift their level of engagement and nobody gets called out for it. And never push someone into playing a character that demands vulnerability they haven't consented to. The person going through the motions isn't failing your workshop; your workshop is failing to offer them a door. (Safety tools for workplace roleplay exist for exactly this.)

The loudest voice (dominance)

One or two players are making every call while the rest defer or drift. It's tempting to read this as a personality problem, and sometimes it is – but at the table it's a structure problem first. If one player can quarterback the whole session, the design let them.

The in-game answer is the spotlight shift: an NPC turns to a quiet participant and addresses their character directly. The person isn't cold-called; their character is invited. Hidden information does the same work structurally – when each role holds knowledge the group needs, the table can't succeed off one voice. And don't waste the dominant player's pattern. What they did, and how the group responded to it, is some of the richest material your debrief will get.

Avoidance reinforcement

This is the failure mode that worries me most, because it's silent. A conflict-avoidant participant watches the game's disagreements get sharp, retreats a little further with each one, and leaves more convinced than ever that conflict is dangerous. That risk isn't hypothetical – one study found conflict training actually reduced confrontation intentions among highly avoidant individuals.

Watch for the participant who keeps agreeing. The intervention is to lower the intensity, not raise the challenge: ease the time pressure, soften the current confrontation, give them a low-stakes way in. The side-coaching line "What does your character think about that?" offers permission without demand – the character can say what the person isn't ready to. Then, in the debrief, normalize avoidance instead of pathologizing it. For this participant, "I noticed I kept deferring even when I thought the plan was wrong" is the win. Recognition is the objective. Changing the pattern takes months, not an afternoon.

"Right answer" hunting (training scars)

The symptom is a table performing at you: players glancing over after each decision, asking what they're supposed to do, producing suspiciously textbook phrases. They're learning something, just not what you want – they're learning to read the facilitator. This one carries the ugliest name in our design notes: training scars.

The fix is mostly restraint. Don't reward "correct" conflict behavior in the game, and don't rescue people from bad choices – let natural consequences play out, because a scenario worth running has multiple valid approaches and real ways to fail. When someone asks what you want them to do, hand the question back to the fiction. You don't have a preference. Korr, the commander in our scenario whose flawed plan the players hold evidence against, very much does – and he's waiting to be convinced.

The group going flat

Energy drains, the pace slows, side conversations start, and the dice get pushed around instead of rolled. Flow psychology gives you the diagnosis: engagement lives where challenge and skill balance, with clear goals and immediate feedback. When the challenge drops below the group's skill, attention leaves the table.

You have two dials, and both are invisible to the players. Tighten the time pressure – the threat accelerates, the window shrinks, and the decision the group has been circling now has to happen. Or drop new information: intelligence arrives that reframes the situation and cuts through the positions people were camping on. Either move reads as the story getting interesting rather than the trainer getting nervous, which is exactly why the game master's chair beats a flipchart.

How do you intervene without breaking the game?

Three techniques cover nearly every situation above. Search for facilitation techniques for difficult groups and you'll mostly find advice built for meetings – ground rules, parking lots, round-robins. A game hands you better options. Two of these work inside the fiction; one steps outside it, briefly, on a strict budget.

The NPC redirect

An NPC says or does something that surfaces the conflict, adds information, or applies pressure. This is the workhorse – use it freely, because it operates entirely within the game world. Drama education has been refining the move for decades as teacher-in-role; a 2021 paper calls facilitators working this way "undercover agents," able to challenge, support, and redirect learners without dissolving the fiction. Reach for it when the group is avoiding the conflict the scenario was built around, when everyone's stuck defending surface positions, or when the stakes need raising.

The spotlight shift

Direct an NPC interaction toward a quieter participant. Use it for dominance problems, and for the player who's visibly holding something back. Being addressed as your character is a gentler invitation than being asked to speak up in front of colleagues – the fiction gives people somewhere to stand. Its lighter cousin is side-coaching: a brief prompt delivered during the action, like "What does your character think about that?", which costs almost nothing in momentum.

Freeze-and-explore

Pause the game and ask the table: "Interesting moment. What's everyone thinking right now?" This is your only out-of-frame tool, and it's rationed – two or three uses per session, maximum. Spend one when something genuinely rich just happened and will evaporate if the game rolls on.

The ration isn't about protecting learning outcomes; the evidence above says pauses don't hurt skill acquisition. It's about protecting the group's trust in the frame. A game that stops every ten minutes for reflection stops being a game. The drama tradition would add that total immersion was never the goal anyway – the working state is metaxis, holding the fiction and the real learning context in mind at once. The freeze works precisely because it's rare.

When should you do nothing?

More often than your nerves suggest. Don't step in when the group is struggling productively – the struggle is the learning, and intervening robs them of figuring it out. Don't rescue a participant making a "mistake" that will become the best conversation of the day. Don't touch a table that's in flow and working the conflict naturally, even if they're working it badly by your standards.

What you do instead is write. Three to five specific moments, jotted as they happen, because everything you wisely didn't fix mid-game becomes raw material afterward – and the debrief is where experience converts into transferable skill, worth a 20-25% performance improvement in the meta-analytic literature. We've laid out that structure in our guide to how to debrief a training exercise.

A scenario going sideways isn't your plan failing. Most of the time it's the most honest data the room will give you all day: this is how this group actually handles pressure, disagreement, and each other. Diagnose the pattern, make the smallest in-fiction move that shifts it, and keep your notepad busy.

The sweaty palms just mean you're paying attention.