An after-action review is a structured conversation held soon after completed work. Its purpose is to compare what the team intended with what actually happened, understand the causes behind important differences, and assign changes before memory fades. The method is simple enough for a short project and disciplined enough for a major event. The quality comes from preparation, candid evidence, and follow-through.
Prepare the meeting and facilitator
Schedule the review while the sequence is still recoverable. A window of twenty-four to forty-eight hours works for many ordinary events, though safety, recovery, or evidence collection can justify more time. Put the review on the calendar before the work begins when possible. Participants then understand that observation and learning are part of completion rather than an optional meeting added later. For another introduction to planning a review, read monday.com’s AAR overview.
Invite people who directly planned, performed, supported, or observed the work. A room filled only with managers produces a secondhand account. A room that is too large can suppress detail. Choose the smallest group that represents the important perspectives, then collect written input from others who hold facts the group will need.
Name a facilitator who can protect the process without defending the outcome. The facilitator opens with the event boundary, intended result, available evidence, and ground rules. They manage time, draw out quieter participants, pause unsupported conclusions, and keep seniority from deciding factual disputes. They should be independent enough to challenge the first convenient story. Deckary’s AAR template guidance is a related resource to compare while preparing an agenda.
Work through the four questions
Begin with the first question: what was supposed to happen? Use the plan that existed before the event, including objectives, roles, measures, assumptions, and decision points. This is not a chance to improve the plan retrospectively. The group needs the original intent because the difference between plan and reality creates the material for the rest of the review.
Ask what actually happened and build a shared sequence. Use timestamps, records, work products, system data, and direct observations. Let participants write independently before discussion so the first speaker does not anchor everyone else. Mark uncertainty openly. A disputed fact should remain disputed until evidence resolves it.
Next ask why the result differed. Move past labels such as communication problem or human error. Examine the conditions that shaped behavior: unclear authority, missing information, workload, incentives, handoffs, tools, changing assumptions, and timing. Use repeated follow-up questions carefully. The goal is a causal explanation strong enough to support a useful change. The article on after-action reviews from Wharton Executive Education provides further reading on this four-question approach.
Then ask what should be sustained or changed. Preserve successful practices with the same care given to failures. Convert each selected finding into a specific action, owner, due date, and check. Limit the list to changes with real consequence and authority. An enormous action register often protects the meeting from making priorities.
Protect candor and close with assignments
Keep the room candid and specific. A blame-free review still holds people accountable for choices. It simply examines those choices in context and directs criticism toward learning. Leaders can support candor by speaking after junior participants, acknowledging their own assumptions, and inviting evidence that complicates the official account.
Close by reading back the main findings and assignments. Confirm what remains uncertain, who will resolve it, and when the written record will circulate. The facilitator should publish a concise account while the discussion is fresh. Participants need a short period to correct factual errors without rewriting uncomfortable conclusions. For more reading on facilitating the discussion, consult MGRUSH facilitation guidance.
Carry the findings into normal work
Follow-up distinguishes a review from a ritual. Put assigned changes into the team’s normal work system. Revisit them at a defined date and test whether they changed behavior or results. Bring relevant lessons into the kickoff for similar work. The next team should encounter the lesson before the next decision, not after the next failure.
Consider a team completing an event with several handoffs. An immediate conversation can capture the details while they are fresh, but a useful review also checks the plan, the sequence and the decisions made with the information available at the time. That combination helps the team avoid turning an uncertain memory into a confident explanation.
The meeting length should follow consequence and complexity. A short recurring task may need twenty minutes. A complicated incident may require preparation, separate interviews, and several hours. Keep the four-question spine in either case. More ceremony does not compensate for weak evidence or missing ownership.
Help participants prepare useful evidence
Send a one-page preparation note before the meeting. State the event, the intended outcome and the records participants should bring. Ask each person to identify one useful observation in advance, including something that went well. This gives quieter colleagues a way into the discussion and reduces the chance that the agenda follows only the most recent complaint. Keep preparation proportionate: a routine review should not require a report from every participant.
When an explanation becomes vague, ask for a specific moment. If someone says communication failed, find the message, decision or handoff they mean. What information was available to whom at that time? What did the recipient understand? The answer may point to an unclear responsibility, a missing channel or an assumption that was reasonable under the circumstances. Each suggests a different change, so resist settling for a broad instruction to communicate better.
Make each assignment a feasible plan
For each proposed action, ask the owner to explain the first step and the evidence of completion. Updating a checklist might require a reviewer, a publication location and a trial during the next event. Training a group might require time on a real schedule. If nobody can describe a feasible first step, the action needs more work before the meeting closes. A clear assignment is a small plan, not simply a name beside an aspiration.
After the review, send the agreed record promptly and allow participants to correct factual errors. Keep a short window for corrections so the account does not remain provisional indefinitely. Disagreement about interpretation can be noted without rewriting the whole session. At the next relevant planning meeting, bring back the actions and check their status. This handoff connects learning to the team's normal work instead of creating a separate reporting ritual.
Review the review itself
Review the session itself once the record is complete. Did everyone with direct knowledge contribute? Did the group distinguish evidence from interpretation? Were important successes examined as carefully as problems? Did the final actions address the conditions identified? These questions help the facilitator improve the next agenda. A recurring review should become easier to run over time, while still leaving room for an event that needs a different kind of discussion.