Everyone may have spoken during a tabletop exercise, the meeting may have finished on time and the attendance list may be complete. Those facts show that the event was organised; they do not show which operational question became clearer. For a client purchasing security services, the value lies in learning that can be used in the next real application.
The research behind a review
Tannenbaum and Cerasoli's meta-analysis of 46 samples found an average performance benefit from debriefs compared with control groups. [1] Its average effect cannot be transferred to a particular security team or a single meeting. UK exercising guidance also treats evaluation and learning as part of the activity. [2] The following questions are our practical application of these principles.
Return to the original question
If the objective was left as broadly as “develop the team”, the final discussion may also be vague. A narrower question could be: when the planned organisational contact cannot be reached, does the team know which approved communication route to use?
This example does not require an attack scenario or real intervention tactics. Roles and information flow can be discussed through an announced, harmless fictional situation. Authorised organisers should define boundaries that prevent the exercise from affecting actual operations.
At the review, read the same question again. What is clearer to participants than it was at the beginning? If the answer has not changed, investigate why rather than merely recording that the session was useful.
Compare expectations with observations
First explain the action expected under the current instruction. Then record what participants actually said or decided without immediately adding an interpretation. Do not present a useful idea developed afterwards as the correct answer everyone should already have known.
In the example, the team might know the backup contact's role but be unable to locate the source containing its details. That does not justify concluding that the whole team misunderstands its duties. Access to that particular information and the currency of its source can be considered separately.
Use five concrete questions
A brief review can ask:
- Which decision was expected?
- What information did participants have at that moment?
- Where did different interpretations or delays appear?
- Which practice worked well and should be retained?
- What will change before the next attempt?
Give participants an opportunity to correct the account of what they meant. A note-taker's interpretation is not necessarily the same as the speaker's explanation. Someone who has not spoken may also have useful observations; do not rely exclusively on the most senior participant's account.
Not every observation requires a new rule
A missing source of telephone details may be resolved by updating a document. Two departments understanding authority differently may require a joint decision by client and provider managers. Some observations should remain explicitly unresolved because the necessary information is not yet available.
At closure, identify the change to be made, its owner and when it will be reviewed again. These three elements connect a meeting note with actual follow-up. Share the outcome with the relevant people without circulating sensitive operational information more widely than necessary.
Check that absent shifts receive updates relevant to them. Do not rely on an officer who missed the review learning about a change by chance from colleagues. Record that the appropriate communication took place.
In the next short exercise, revisit the same decision point. Is the change being used, and has it introduced a new ambiguity? This check prevents the outcome from remaining only in the memories of those who attended. The review can then show whether learning has reached everyday practice, rather than merely announcing success.
