50+ Debrief Questions for Team Exercises (Organized by What They Surface)

The U.S. Army runs its after-action reviews on four questions: What was supposed to happen? What actually happened? Why was there a difference? What can we do differently next time? No slides, no workbook – and a meta-analysis of 61 studies covering 915 teams and 3,499 individuals found the practice improves performance with an effect size of d = 0.79, which is enormous by training-research standards.

Every debrief question worth asking is a sharpened version of one of those four. This article is the bank of 50-plus we draw from after Operation Aetherfall, our tabletop conflict-training scenario – organized by debrief phase (reactions, analysis, application) and, within analysis, by what each group of questions surfaces: hidden information, authority dynamics, decision quality, avoidance patterns, and emotional undercurrents. Each group comes with a note on when to reach for it and what a good answer sounds like, and the last section names the three questions to ask when you've only got ten minutes.

Where do these questions come from?

Half from the research, half from the table. The research half is the debriefing literature: the Army's after-action review tradition, healthcare simulation frameworks, and Thiagarajan's six-phase model for learning games, which walks the same arc in finer slices – How do you feel? What happened? What did you learn? How does this relate? What if? What next? The practice half is two full pilot runs of Operation Aetherfall: a roughly seven-and-a-half-hour session in which six players manage a commander named Korr who's working from a flawed plan, followed by a ninety-minute debrief.

The four classic AAR questions map onto this bank like so:

AAR question	What it's really doing	Where it lives in this bank
What was supposed to happen?	Establishing shared facts and intent	Analysis – decision quality
What actually happened?	Surfacing what people saw, knew, and withheld	Analysis – hidden information
Why was there a difference?	Examining reasoning, dynamics, and avoidance	Analysis – all five groups
What will we do differently?	Committing to a specific change	Application

You'll notice the AAR starts cold, straight into facts. We put a reactions phase in front of it because conflict exercises run hot – participants who are still activated from the experience can't examine their own behavior objectively yet. The full three-phase structure, with timing budgets and the research behind each phase, is in how to debrief a training exercise. This article is the ammunition.

One usage note before the bank: you won't ask fifty questions. A 40-minute analysis phase holds maybe eight, pointed at specific moments you noted during the exercise. Pick the groups that match what you actually watched happen, and leave the rest for next time.

Phase 1: Reactions – questions that let the pressure out

When: the first 10-15 minutes, before any analysis. What they do: emotional decompression. The instinct to skip this phase is strong and wrong.

• "How are you feeling right now?"
• "What was the most intense moment for you?"
• "What surprised you about yourself during the exercise?"

If someone starts analyzing ("I think I should have pushed back earlier..."), redirect gently. That's coming. Right now, just – how are you feeling?

A good answer here is a feeling, not a lesson. "Honestly, I'm still annoyed about the door decision" is perfect. "I learned the importance of communication" means they've skipped ahead.

We follow the spoken questions with three to five minutes of private writing. Three prompts, and nobody else reads the answers:

• One moment during the exercise where I handled a conflict well:
• One moment where I wish I'd done something differently:
• Something I noticed about my own conflict patterns:

The silent round keeps the loudest voices from setting the frame for everyone, and it gives quieter participants a formed thought to carry into the discussion.

Phase 2: Analysis – questions grouped by what they surface

When: the long middle – 40 to 50 minutes in our sessions. What they do: examine what happened, why, and what it reveals.

Two techniques make every question below work better. First, advocacy-inquiry, from Rudolph and colleagues at Harvard's Center for Medical Simulation: pair an honest observation with genuine curiosity about the person's reasoning. "I noticed you led with the structural data instead of challenging the plan directly – help me understand what was driving that." There's a full guide at advocacy-inquiry debriefing. Second, point questions at moments, not abstractions. I keep a notepad during the game because after four hours of running six players and a collapsing dungeon, my memory is mush – and "that moment when Bramm pushed back on Korr's timeline" produces analysis where "how did the group communicate?" produces fog. The AAR meta-analysis backs this up: one of the two strongest drivers of effectiveness was reviewing objective records of performance. In a training room, your notepad is that record.

One more finding worth taping inside the notepad: debriefs where the facilitator talked less than the participants were rated notably higher in quality. Ask, then wait.

Questions that surface hidden information

Use these when knowledge existed in the group and didn't move – someone knew something, and the team decided without it. In Operation Aetherfall this is engineered: every player holds a secret information card. In your exercise it'll happen on its own.

• "Was there information that could have helped the team but didn't come out until later – or didn't come out at all?"
• "When did you realize you knew something the group needed?"
• "What would have made it easier to share what you knew earlier?"
• "What did it cost the team when that information stayed hidden?"
• "Did anyone pull information out of a teammate by asking a question? What was the question?"
• "What did you assume everyone else already knew?"
• "When you finally did share it, what happened next?"

A good answer names the piece of information and the moment its holder sat on it: "I knew the passphrase was a gamble and I waited to see if anyone would ask." "We could've communicated better" is a shrug, not an answer.

Questions that surface authority dynamics

Use these when the exercise involved rank – a leader with a flawed plan, a participant who deferred, a challenge that landed or didn't.

• "How did you handle the disagreement with [the leader]? What did you try first?"
• "What made some approaches work better than others?"
• "Can you put words to what made a challenge feel constructive rather than insubordinate?"
• "What stopped the group from pushing back harder? What would have made it easier?"
• "Did anyone feel pulled to align with [the leader] even while holding doubts? What was the pull?"
• "What did you notice about how [the leader who took input well] communicated differently?"
• "When someone led with evidence instead of opposition, what changed in the room?"

A good answer describes a move, not a virtue. "Leading with what the survey team found gave him room to update without losing face" beats "I stayed respectful."

Questions that surface decision quality

Use these on the biggest decision of the exercise, especially if it happened fast. Groups are usually confident they decided well and usually hazy on how.

• "How did the group make [the decision]? Walk me through it."
• "Whose input was included? Whose wasn't? Why?"
• "Did anyone feel like the decision was made before everyone had been heard?"
• "Was there a moment where one person's perspective changed the group's direction? What made that happen?"
• "When [one person] wanted X and [another] wanted Y, what was underneath those positions? What did each of you actually need?"
• "When did the group get stuck arguing about solutions instead of understanding the problem?"
• "Did you land on consensus, the loudest voice, the highest rank, or the first idea somebody said out loud?"
• "When you had to justify a choice to your teammates, was it hard to put your reasoning into words?"
• "How often at work do you make a decision without explaining your reasoning to the people it affects?"

Those last two come from a villain. Overseer Vane, an adversary in our scenario, forces a player to mark Stress if they can't justify their last action to their teammates – the most reliable facilitator at our table is a monster with a stress mechanic. A good answer to this group narrates the mechanism: "Honestly, we didn't decide. Bramm said it twice and we started moving."

Questions that surface avoidance patterns

Use these when you watched someone hold back – and handle them with care. The goal is recognition, not shame. Most people hold back in situations like these; it's a very human response. The question is what it costs.

• "Was there a moment you held back from saying something? What stopped you?"
• "What did staying quiet feel like it was protecting you from?"
• "Did you disagree with a decision silently? What did you do instead of saying so?"
• "Did you notice anyone defer when they clearly had something to add? Did you notice yourself doing it?"
• "What would have made it easier to speak up in that moment?"
• "Where does this same holding-back show up in your normal week?"

A good answer is first-person with a named cost: "I didn't want to be the one slowing us down – and we walked into the wrong room because of it."

Questions that surface emotional undercurrents

Use these if any disagreement started to feel personal. If none did, use the workplace variants anyway – the pattern exists whether or not the game triggered it.

• "Did any disagreement start to feel personal? When did you notice the shift?"
• "What was happening right before you noticed yourself getting defensive?"
• "Once you noticed the feeling, what did you do with it?"
• "What would have helped de-escalate that moment?"
• "Was there a point where the tension in the room changed? Who felt it first?"
• "At work, when does a disagreement about a decision start feeling like a disagreement about you? What triggers that shift?"

A good answer locates the shift in time: "When she waved off my concern the second time, I stopped arguing for the plan and started defending myself."

Questions that bridge to real work

Use these to close the analysis phase, every time. Transfer doesn't happen on its own – the connection between the exercise and Monday has to be built out loud.

• "Where have you seen this exact dynamic at your job?"
• "What made this conflict feel familiar?"
• "How is what happened here different from how it usually goes at work?"
• "What did the exercise make possible that your work environment doesn't?"
• "What's the closest thing to [the scenario's dilemma] on your team right now?"
• "If you'd tried [the move that worked here] in your last real disagreement, what would have happened?"

A good answer has a real meeting in it. The moment someone says "this is exactly like our quarterly planning," the debrief has started doing its job.

Phase 3: Application – questions that turn insight into a plan

When: the final 25-30 minutes. What they do: convert insight into a written, specific, spoken-aloud commitment. Debriefs that end on insight instead of commitment leave most of their transfer potential on the table.

• "What's one situation at work – one that happens regularly – where you want to try something different?"
• "When I notice ______, instead of ______, I will ______." (written, as a fill-in)
• "What's the internal signal that tells you the situation is happening?"
• "Can you make the action more specific? What words would you actually say?"
• "What's the first thing that might get in the way of this plan?"
• "If it doesn't go well or you forget, what will you do?"
• "Who will check in with you in two weeks, and what will they ask?"

The if-then format isn't a style preference. Specific implementation intentions roughly double follow-through, from about 30% to about 67%, and sharing them aloud raises it again, from roughly 43% to 76%. The mechanics are in implementation intentions and training transfer, and the check-in question pairs well with a one-week follow-up survey if you want measurement alongside accountability.

A good answer has actual words in it: "If I feel the urge to stay quiet when I disagree in a meeting, I'll say 'I'm working from different assumptions – can I share them?'" A goal like "handle conflict better" is a wish wearing a plan's clothing.

What three questions should you ask if you only have ten minutes?

One from each phase. A ten-minute debrief with one question per phase beats thirty minutes spent entirely on analysis, because the phases are the mechanism – decompress, examine, commit – and skipping one breaks the chain.

1. "What was the most intense moment for you?" – reactions. It vents the pressure and simultaneously tells you where the richest material is, even if you weren't watching for it.
2. "Walk me through how the group made that decision. Whose input was missing?" – analysis. Decision quality is where the other four surfaces intersect: hidden information, authority, avoidance, and emotion all show up in how the choice actually got made.
3. "The next time you notice that same pattern at work, what will you do instead – specifically?" – application. Don't accept a theme. Get words they'd actually say.

The bank is for browsing, not broadcasting. Point a handful of these at moments you actually watched happen, in phase order, and save the rest for the next run. Fifty questions matter less than one moment named precisely.