Define the purpose of the review
A debrief can help explain what happened and what should change next time. Clarify whether it is an informal learning discussion or part of a formal organisational process. Use the relevant procedure and protect confidential information. Do not begin by selecting a person to praise or blame. Choose the decisions and coordination points that affected the work. A useful review examines an account that can be supported, rather than a story constructed only after everyone knows the outcome.
Recover the original expectations
Find the plan, assumptions and criteria available when the decision was made. Separate an expectation recorded at the time from a later recollection. A final result can make earlier uncertainty seem smaller than it actually was. Preserve the distinction between what was known and what became clear later. This does not excuse poor work; it makes the evaluation more accurate by connecting decisions to the information, authority and constraints under which people actually acted.
Distinguish the outcome from the process
A favourable result does not automatically establish that every decision was sound, and an unfavourable result does not identify which decision was wrong. Examine the reasoning, execution and relevant external conditions separately. Avoid making causal claims that the available record cannot support. State where the explanation remains uncertain. The review should help identify a plausible mechanism and a justified next step, not produce certainty simply because an organisation wants a neat account of success or failure.
Select one change with an owner
A lesson is more usable when it names an action, the appropriate owner and the condition under which it applies. Avoid a conclusion such as communicate better without defining the missing information or handover. Do not impose a new obligation without the relevant authority. Some proposed changes need further investigation rather than immediate adoption. Keep that status visible so the debrief does not turn a tentative idea into an unapproved process simply by recording it in confident language.
Preserve a useful record
Document the evidence, the decision about follow-up and any unresolved disagreement according to the organisation’s rules. A learning record should support future work without becoming an unauthorised file about individuals. Avoid including sensitive material that is not necessary for the approved purpose. At a later checkpoint, ask whether the agreed change was used and what it helped clarify. Do not declare a permanent lesson from one event without considering the conditions that made the event different.
Run a fictional debrief
Imagine a study-group project that met its deadline but required substantial last-minute reorganisation. Write the original plan, the observed outcome, two possible explanations and the evidence needed to distinguish them. Propose one small, authorised change for a future project and state when you would review it. Keep the example fictional rather than assigning motives to real classmates. The exercise should reveal how a successful output can still contain coordination questions worth examining, without treating every difficulty as proof that someone failed or every improvement as a universal rule.
