Why does the debrief matter more than the game itself?

The game produces behaviour under pressure, which is the raw data. But behaviour does not transfer on its own. The debrief is where participants see their own patterns, connect them to principles, and decide what to do differently on Monday. Skip or rush the debrief and you have run an activity, not a development session. Learning lands in the debrief, not the game.

What makes an EPPA application commitment stick?

A commitment sticks when it is concrete: a named behaviour, a named situation, and a date. Vague resolutions like communicate better do not survive contact with a busy week. EPPA forces each participant to state what they will do differently, in which recurring situation, and by when, so the insight has somewhere real to land.

The EPPA Debrief Loop: How to Debrief a Serious Game

Q: What is the EPPA debrief loop?

The EPPA debrief loop is a four-stage framework for debriefing a serious game: Experience, Patterns, Principles, Application. It moves a group from reconstructing what actually happened in the game, to naming the behavioural tendencies the game revealed, to connecting those patterns to leadership theory through the participants' own insight, to committing to concrete changes in real work. The game generates the data; the debrief turns it into change.

Q: How do you run an EPPA debrief?

Run the four stages in order. Experience: reconstruct what actually happened, decision by decision, before interpreting it. Patterns: ask what tendencies showed up under pressure, in the participants' own words. Principles: connect those patterns to leadership theory so the insight is theirs, not the facilitator's. Application: end with named commitments tied to a specific behaviour, situation, and date.

Two people in a seated conversation during a studio interview

Short answer: EPPA is a four-stage way of debriefing a serious game so what happened in the room becomes a change in behaviour outside it. In order: Experience (rebuild what actually happened), Patterns (name what kept repeating under pressure), Principles (connect those patterns to leadership principles through their insight, not my lecture), and Application (commit to something real, with a named behaviour, a named situation, and a date). The game produces behaviour under pressure. EPPA is what converts it.

Key takeaways

Stage	The question it answers	What the facilitator does	Output
E - Experience	What actually happened?	Reconstruct the game decision by decision before anyone interprets it	A shared, factual account of the session
P - Patterns	What did we keep doing under pressure?	Surface behavioural tendencies in the participants' own words	Named patterns the group recognises as theirs
PR - Principles	Why does that happen, and what does theory say?	Connect patterns to leadership theory via participant insight, not a lecture	A principle the group owns, not one handed to them
A - Application	What will I do differently, and when?	Force concrete commitments: named behaviour, situation, date	Monday-morning actions each person can be held to

Why the debrief, not the game, is where learning lands

Here is the thing nobody selling experiential learning says out loud. The game is the easy part. Hand out cards, run some rounds, everybody has a brilliant time and somebody posts a photo on the company channel. Monday comes. Nothing happens.

Knowledge transfers. Behaviour does not. A serious game is engineered to squeeze people between real constraints - scarcity, asymmetric information, interdependence, cascading consequences - so that how they actually lead becomes visible while it is happening. That visible behaviour is the only data worth developing from. And on its own it changes precisely nothing. People can have a vivid, high-stakes afternoon and walk straight back to their desks behaving exactly as before.

The debrief is where that turns. EPPA takes the raw behaviour the game just produced and walks the group through seeing it, understanding it, and committing to doing something else with it. Run the game well and skip the debrief, and you have delivered a very expensive activity. Run a deliberate EPPA debrief, and the same game becomes a development session with names and dates attached to it. The game generates the data. The debrief turns it into change.

Facilitated tabletop role-playing session with an engaged group of players

The four stages of EPPA, one at a time

E - Experience: rebuild what actually happened

The first stage is boringly factual, on purpose. Before anyone is allowed to interpret, judge or defend, the group rebuilds the game decision by decision. Who chose what, when, and in response to what. This matters because memory under pressure is unreliable and deeply flattering. Everyone remembers the version where they were being reasonable.

So my only job here is to keep asking "what happened?" and to refuse, politely and repeatedly, every attempt to leap to "what does it mean?" Get the timeline solid first. Without a shared Experience, the rest of the debrief is just an argument about whose version is true.

P - Patterns: name what kept repeating

With the facts agreed, the group looks for what happened more than once. Did people start hoarding the second supply got tight? Did one function optimise its own scorecard beautifully while the whole table lost? Did the room go completely silent the moment I took away the one channel everybody had been leaning on? Those are patterns, and they showed up because the pressure was real.

The critical move is that the patterns come from them, in their own words. A facilitator who announces "you were not collaborating" gets a room full of folded arms. A facilitator who asks "what did we keep doing every time the pressure spiked?" gets recognition, and usually a groan. Patterns a group names themselves are patterns a group will own.

PR - Principles: connect the patterns to theory through their own insight

Only now does leadership theory get to walk in, and it walks in through the participants rather than over them. Once a group has named a pattern - say, every leader optimising locally in a way that sinks the whole thing - I connect it to what is sitting underneath: local maxima versus global maxima, the way a stack of perfectly rational individual choices adds up to a collectively daft outcome. The point is that they arrive at the principle and recognise it. Not receive it as slide fourteen.

This is the stage most training runs backwards. It opens with the principle and hopes behaviour catches up. EPPA earns the principle out of behaviour the group has just lived through, which is exactly why it sticks. The insight is theirs. I mostly held the door open.

A - Application: concrete Monday-morning commitments

The loop closes with action, and this is the stage where most debriefs go soft, warm and useless. "Communicate better" is not a commitment. It is a wish with a nice haircut. EPPA makes each person state a named behaviour, a named situation and a date. What I will do differently, in which recurring situation, and by when. "In our Thursday pipeline review, I will surface the trade-off I have been hiding before somebody asks me for it, starting this week."

That level of specificity is what survives contact with a busy Tuesday. It also hands L&D and line managers something real to follow up on, which is the whole difference between a measurable change and a fond memory of a good afternoon.

Reconstruct. Name. Connect. Commit. That is the entire engine, and it fits on a napkin.

How EPPA fits the Put The Player First system

EPPA does not stand on its own. It is the debrief engine inside the wider Put The Player First framework, the one system I use to turn any growth experience into a game. The framework builds the experience - the decision architectures that put behaviour under pressure - and EPPA is how the players claim what came out of it. One makes the data. The other converts it.

If you are choosing or commissioning experiential work, the debrief is the part to interrogate hardest. Ask a vendor to describe their debrief loop in this kind of detail. If they can, they are selling development. If they start talking about the energy in the room... they are selling an activity. For the wider picture, have a look at the serious games for leadership development guide, the Decision Labs approach to consequence-based practice, and the full catalogue of serious games I run.

Get new games and facilitation playbooks by email

One short email when there is something genuinely worth using: a new game, a debrief move that worked, or a look behind the curtain at a real session. Not weekly. I do not have that much to say.

Frequently asked questions

What is the EPPA debrief loop?
Four stages for debriefing a serious game: Experience, Patterns, Principles, Application. It moves a group from rebuilding what happened, to naming what kept repeating, to connecting that to leadership principles through their own insight, to committing to something concrete in real work.

Why does the debrief matter more than the game?
The game produces behaviour under pressure, which is the raw data. Behaviour does not transfer on its own. The debrief is where people see their patterns, connect them to principles, and decide what to change. Skip it and you ran an activity.

How do you run an EPPA debrief?
In order, no shortcuts. Experience: rebuild what happened before interpreting it. Patterns: surface what repeated, in their words. Principles: connect them to theory so the insight is theirs. Application: end with named commitments tied to a behaviour, a situation and a date.

What makes an application commitment stick?
Being specific. A named behaviour, a named situation, a date. "Communicate better" does not survive a busy week. "In Thursday's review I will surface the trade-off before I am asked, starting this week" does.