Leadership
Run an after-action review that changes the next attempt
Build a shared account of a work episode, understand decisions in context and give each useful lesson an owner and a next test.
A launch finished late, the team worked through the weekend and everyone has a theory about why. An after-action review can turn those accounts into a useful change. It can also become an hour of defending decisions unless the manager gives the conversation a clear purpose and an evidence base.
Choose one episode to examine, such as the approval process that delayed the launch. The review should explain the difference between what the team expected and what happened, then identify something worth sustaining or changing before the next comparable task.
Set the scope before people arrive
State which event, period and decisions are in scope. Gather the original plan, relevant messages, delivery records and any agreed measures. Invite people who saw different parts of the work, including those affected by the handoffs. Their accounts may differ because they had different information.
Explain how the discussion and notes will be used. A learning review should not promise confidentiality that you cannot provide. If a separate personnel or formal investigation process is required, clarify its relationship to this meeting rather than disguising it as an informal discussion.
There is a research basis for structured reflection. A meta-analysis by Scott Tannenbaum and Christopher Cerasoli, first published online in 2012, found that debriefs improved effectiveness on average across the samples studied. Its findings do not mean every retrospective produces a fixed performance gain. The focus and structure of a review still matter.
Reconstruct events before explaining them
Ask what the team intended to happen and what actually happened. Build a short timeline that distinguishes records from recollections. Note where the evidence is incomplete. An accurate disagreement is more useful than a tidy story that leaves out a participant’s experience.
For the delayed launch, identify when the approval was requested, what the request contained and when anyone realized the approver was unavailable. Avoid beginning with the conclusion that someone communicated badly. That label can hide several different problems, each needing a different response.
Review successful moments too. Perhaps an early check by customer support caught an error before release. Ask what enabled that check and whether it can be repeated. A useful review preserves effective practice rather than treating everything about a difficult event as defective.
Ask what made the action reasonable at the time
Once the timeline is clear, explore the information, constraints and assumptions behind important decisions. A manager can describe an observation, explain the concern and ask an open question: the request waited two days; what did you understand the approval route to be?
In an observational study first published in 2022, Michaela Kolbe and colleagues examined communication in healthcare simulation debriefings. Certain sequences combining observations, opinions and open questions were associated with participants explaining their thinking. That is evidence from a specific training setting, not proof that an office script will produce the same result.
Use the question to learn, not to demand a confession. Let participants correct your interpretation. Distinguish an individual decision from the conditions around it, including workload, unclear authority and conflicting instructions. Taking conditions seriously is compatible with naming responsibilities clearly.
Turn an explanation into a testable change
Choose a small number of changes linked to the evidence. If the problem was an unknown backup approver, adding another status meeting may not help. A more direct action is to name an approved backup and check the route before the next launch.
Assign an owner, an occasion to try the change and a way to judge whether it helped. Record the practice to retain as carefully as the correction. NASA’s 2024 account of an asteroid-impact exercise described an after-action report covering strengths, gaps and improvement recommendations: a useful distinction between learning what worked and listing everything that went wrong.
Check whether the lesson changed the work
Send a concise record that separates findings, uncertainties and agreed actions. Give participants a chance to correct factual errors. Before the next comparable event, ask whether the change is in place and whether its owner has the support to carry it out.
After that event, check the result. A lesson becomes useful when it changes a decision or a routine. Without that return to the work, even a candid review can end as another document the team has no reason to open.
