The EPPA Debrief Loop: How to Debrief a Serious Game
The game generates the data. The debrief turns it into change.
Short answer: The EPPA debrief loop is a four-stage framework for debriefing a serious game so that what happens in the room becomes a measurable change in behaviour. The stages run in order: Experience (reconstruct what actually happened), Patterns (name the behavioural tendencies the game revealed), Principles (connect those patterns to leadership theory through the participants' own insight), and Application (concrete Monday-morning commitments, each tied to a named behaviour, situation, and date). A serious game produces behaviour under pressure. EPPA is the engine that converts that behaviour into learning that lands.
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 principle that sits under everything we build at Put The Player First: knowledge transfers, behaviour does not. A serious game is engineered to put people under real constraints - scarcity, asymmetric information, interdependence, cascading consequences - so that how they actually lead becomes visible. That visible behaviour is the only data worth developing from. But the game on its own changes nothing. People can have a vivid, high-stakes session and walk straight back to their desks behaving exactly as before.
The debrief is where that changes. EPPA is the loop that takes the raw behaviour the game generated and walks the group through seeing it, understanding it, and committing to doing something different with it. Run the game well and skip the debrief, and you have delivered an expensive activity. Run a deliberate EPPA debrief, and the same game becomes a development intervention with named outcomes. The game generates the data. The debrief turns it into change.
The four stages of EPPA, one at a time
E - Experience: reconstruct what actually happened
The first stage is purely factual. Before anyone is allowed to interpret, judge, or defend, the group rebuilds what happened in the game, decision by decision. Who chose what, when, and in response to what. This matters because memory is unreliable and self-serving under pressure: people remember the version that flatters them. Reconstructing the actual sequence of events gives the whole group a shared, agreed account to reason from.
The facilitator's job here is to ask "what happened?" and resist every early jump to "what does it mean?" Get the timeline solid first. Without a shared Experience, the rest of the debrief becomes an argument about whose version is true.
P - Patterns: name the behavioural tendencies the game revealed
With the facts agreed, the group looks for what repeated. Did people hoard resources when supply got tight? Did one function optimise its own scorecard while the company lost? Did the team go silent when the channel they relied on was removed? These are patterns - behavioural tendencies the game surfaced because the pressure was real.
The critical move is that the patterns come from the participants, in their own words. A facilitator who announces "you were not collaborating" gets defensiveness. A facilitator who asks "what did we keep doing every time the pressure spiked?" gets recognition. Patterns the group names themselves are patterns the group will own.
PR - Principles: connect the patterns to theory through their own insight
Only now does leadership theory enter, and it enters through the participants, not over them. Once a group has named a pattern - say, each leader optimising locally in a way that sinks the whole - the facilitator connects it to the principle underneath: local maxima versus global maxima, the way individually rational choices can be collectively destructive. The aim is for the participant to arrive at the principle and recognise it, rather than receive it as a slide.
This is the stage most lecture-based training inverts. It opens with the principle and hopes behaviour follows. EPPA earns the principle from behaviour the group has just lived, which is why it sticks. The insight is theirs.
A - Application: concrete Monday-morning commitments
The loop closes with action, and this is where most debriefs go soft. A good Application stage refuses vague resolutions. "Communicate better" is not a commitment; it is a wish. EPPA forces each participant to state a named behaviour, a named situation, and a date: what specifically I will do differently, in which recurring situation it applies, and by when. "In our Thursday pipeline review, I will surface the trade-off I am hiding before I am asked, starting this week."
That specificity is what survives contact with a busy week. It also gives L&D and managers something concrete to follow up on, which is how a one-day game turns into a measurable behaviour change rather than a fond memory.
How EPPA fits the Put The Player First system
EPPA does not stand alone. It is the debrief engine inside the wider Put The Player First framework, the single system Arvindh uses to turn any growth experience into a game. The framework designs the experience - the decision architectures that put behaviour under pressure - and EPPA is how participants claim what they learned from it. One builds the data; the other converts it.
If you are choosing or commissioning experiential work, the debrief is the part to scrutinise hardest. A vendor who can describe their debrief loop in this kind of detail is selling development. A vendor who cannot is selling an activity. For the bigger picture on where serious games fit in a development programme, see the serious games for leadership development guide, the Decision Labs approach to consequence-based practice, and the full catalogue of serious games we run.
Get new games and facilitation playbooks by email
One short email when there is something worth using: a new game, a debrief technique, or a behind-the-scenes look at a real session.
Frequently asked questions
What is the EPPA debrief loop?
A four-stage framework for debriefing a serious game: Experience, Patterns, Principles, Application. It moves a group from reconstructing what happened, to naming the tendencies the game revealed, to connecting those to leadership theory through their own insight, to concrete commitments in real work.
Why does the debrief matter more than the game?
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 patterns, connect them to principles, and decide what to change. Skip it and you ran an activity, not a development session.
How do you run an EPPA debrief?
In order. Experience: reconstruct what happened before interpreting it. Patterns: surface tendencies in the participants' own words. Principles: connect them to theory so the insight is theirs. Application: end with named commitments tied to a behaviour, situation, and date.
What makes an application commitment stick?
Concreteness. A named behaviour, a named situation, and a date. Vague resolutions like "communicate better" do not survive a busy week; "in Thursday's review I will surface the trade-off before I am asked, starting this week" does.