A debrief becomes valuable when each important gap has an owner, a next step and a way to verify progress.
Capture what happened, not just an opinion
Record the decision or event that exposed a gap. “Communication was poor” is difficult to act on; “the team could not find a trusted supplier contact without the unavailable workspace” identifies a specific dependency.
Distinguish observations from assumptions. If the team did not test a recovery procedure, record that it remains unverified rather than concluding it will work.
Prioritize by consequence
Consider how each gap could affect coordination, containment or restoration of a critical service. Some issues can be corrected quickly; others require changes across teams or suppliers.
Avoid treating every observation as equally urgent. A smaller set of owned priorities is often more useful than a long list without an implementation sequence.
Define closure evidence
Assign an owner and a review date. State what evidence would show that the improvement is effective: a verified contact route, an updated approval process, or a successful scoped restoration test.
Do not close an item solely because a document was edited if the original problem was whether people could use it under pressure. Match validation to the gap.
Schedule the next learning step
A follow-up can be focused on the most consequential change. It does not always require repeating the full exercise. Keep the result and its limitations alongside the original observation.
See Tabletop Exercises and Recovery Drills for a structured approach to scenarios, evidence and improvement.
Put the guidance into practice
Discuss the scope, responsibilities and evidence that would help your team make progress.
Convert an observation into something that can be tested
During an exercise, participants discover that nobody knows who can authorise isolation of a business-critical system. Writing “improve the incident plan” loses the specific issue. Record the decision that stalled, the role expected to make it and the information that role needed. The resulting action might be to agree delegated authority, update the relevant procedure and rehearse the decision with the deputy present. This creates a verifiable improvement rather than a document-editing task with no operational test.
Evidence to collect
- Capture the observation and its effect on the scenario, separating evidence from assumptions.
- Assign one accountable owner and identify the contributors or approvals the action depends on.
- Define a completion criterion that demonstrates the changed capability or decision route.
- Set a review date and record accepted exceptions or reasons for deferring the action.
What a useful result looks like
Review actions in a follow-up meeting with the people who can remove dependencies. Closing an item because a document was updated may be appropriate for a wording correction, but not for a capability that still needs rehearsal. Keep a link between the original observation, the change made and the validation evidence. Use the next exercise to test unresolved or high-consequence decisions.
Does an exercise need a pass or fail score?
Not necessarily. Its value often lies in exposing assumptions and unclear responsibilities. Define objectives beforehand and report what was observed against them. Avoid using a single score to imply that untested systems or scenarios are ready.