Teams use several names for the conversation after an event. The terms overlap, but timing, tone, scope, and expected output differ. Choose the format based on the decision the team needs to make, the freshness of evidence, the consequence of the event, and the amount of preparation available. The label matters less than setting accurate expectations.
What each format is designed to do
A hotwash is immediate. Participants gather at the end of an exercise, response, shift, or event and capture fresh observations before they disperse. It is useful for perishable detail, urgent safety corrections, and questions that need later investigation. It should remain short and should not pretend to deliver a complete causal account while people are tired and evidence is incomplete.
A debrief is the broadest term. It can be a short operational check, a guided reflection, an information-gathering interview, or a team learning session. Define the purpose whenever using the word. Participants should know whether the session concerns wellbeing, performance, intelligence collection, factual reconstruction, or improvement decisions.
An after-action review compares the intended result with the actual result, explores why the difference occurred, and identifies what to sustain or change. It works best soon after the event with the people who performed the work. A neutral facilitator, shared evidence, and assigned actions make the method more reliable. For incident-review meeting preparation, consult Rootly’s postmortem meeting guide.
A postmortem usually follows a failure or incident and often emphasizes causal analysis, impact, detection, response, and prevention. Software and reliability teams commonly use the term. A blameless postmortem examines the system conditions around decisions while preserving accountability for improvements. It often produces a formal record for a broader audience.
A retrospective is usually tied to a recurring team cadence, such as the end of an iteration. It focuses on how the team worked and what experiment to try next. The event may be ordinary rather than exceptional. Regular cadence can make retrospectives psychologically safer, though repetition can also make them shallow unless facilitators vary the evidence and questions. SI Labs on retrospectives is additional reading when considering a recurring team review.
Choose the format for the decision
Choose a hotwash when immediate recall is the main asset and the team needs to flag urgent issues. Capture observations, safety concerns, missing facts, and names for follow-up. Schedule a fuller review before leaving. The hotwash becomes an input to later analysis rather than the final record.
Choose an AAR when there was a clear plan or intended result and the team can compare it with performance. The four-question structure works for projects, operations, campaigns, exercises, and launches. It is especially useful when the group needs to preserve both successful practices and corrections. Readers comparing review terminology can also consult Shamaym’s comparison.
Choose a postmortem when an incident demands a durable causal account, impact analysis, and prevention work. Give investigators enough time to collect records and interview participants. Separate urgent remediation from deeper corrective actions so restoration pressure does not narrow the explanation.
Choose a retrospective when a stable team needs frequent improvement at a manageable scale. Keep experiments small, assign them, and check the result at the next session. Use an AAR instead when a specific event, explicit plan, or cross-functional participant group requires a fuller reconstruction.
Sequence formats when the work needs it
Formats can be sequenced. A team can hold a hotwash immediately, conduct interviews the next day, run an AAR after evidence is assembled, and issue a report with an improvement plan. Naming each stage helps participants understand whether they are supplying observations, testing causes, or approving changes. For a second comparison of immediate discussion and later reporting, read Scope Safety on hotwashes and reports.
Avoid combining every purpose into one meeting. Emotional support, legal investigation, performance management, intelligence collection, and team learning have different confidentiality and authority requirements. A single room cannot always serve them safely. Route each need to the right process and explain the boundaries.
Whatever label is selected, publish a simple charter: event, objective, participants, facilitator, evidence, questions, output, distribution, and follow-up date. That one page reduces confusion and gives the facilitator permission to protect scope.
Evaluate the format by its result. Immediate notes should feed later work. A recurring retrospective should change an experiment. An AAR should produce agreed findings and actions. A postmortem should connect causes to prevention. The vocabulary is useful only when it helps a team choose the right discipline.
Explain the purpose in the invitation
Agree on the purpose before choosing a label. A team that wants immediate observations after an exercise may need a short hotwash now and a fuller analysis later. A group examining an unexpected outage may need a timeline and technical follow-up before it can reach useful conclusions. Write the purpose in the invitation. Familiar terminology helps only when everyone understands what the session will and will not produce.
Timing affects the kind of evidence available. Immediately after an event, participants can recall details that may fade, but monitoring records and downstream effects may still be incomplete. A later session can draw on more evidence while losing some fresh observations. A two-stage approach can preserve both: capture initial accounts, then reconvene when the important records are ready. Mark early impressions as provisional so they do not silently become the accepted explanation.
Match attendance and vocabulary
Match attendance to the method. A short field debrief may include the people who just completed the work; a wider review may need planning, support and decision owners as well. Senior observers should know whether their role is to listen, contribute evidence or make a decision. A meeting with too many spectators can discourage candor. A meeting without the right knowledge can produce an orderly but incomplete account.
Translate terms when teams cross organizational boundaries. One group may use postmortem for any project reflection, while another reserves it for incidents. Ask what questions the method covers, who facilitates and what record follows. This practical comparison is more useful than arguing over the correct name. A shared glossary can help recurring partnerships, but it should describe the team's actual process rather than impose a vocabulary nobody uses.
Review the method after using it
Evaluate the chosen format after the event. Did the time available suit the complexity? Were key records ready? Did participants leave with an accurate account and a manageable next step? If not, change the sequence rather than merely renaming the meeting. An immediate hotwash followed by a focused review may work better than one long session. The method should fit the work's learning needs and the decisions the organization can actually make.