After a busy project, a team quickly develops a shared version of what happened. That story can be convenient and incomplete. An after-action review gives people a structured way to compare the plan with the experience before the details disappear into a confident summary.
The WHO after-action review guidance describes a structured method for learning from events and improving future work. Its emergency-response context differs from an ordinary business project, but a team can adapt the review discipline: compare expectations with events, examine what worked, and decide what to improve.
Start with a short factual timeline
Bring the original brief, key dates and a few relevant records. Give participants time to note their own observations before the most senior person offers an explanation. This helps preserve differences in what people saw.
Separate an event from an interpretation. “The approval arrived on Thursday” is an event. “Nobody cared about the deadline” is an interpretation that needs examination. A useful facilitator asks what information was available at the time and what prevented a different action.
Use one event to practise the method
Imagine a product launch in which customer-support instructions arrived late. The review might establish that the team expected a draft on Monday, received it on Thursday and improvised replies in between. The next question is not merely who was late. It is whether ownership, dependencies and the approval route were clear enough to support the original plan.
Keep successful practices in the discussion too. If a temporary contact channel helped support staff get answers, decide whether it should become part of the next launch process.
Leave with fewer, clearer actions
Choose a small number of changes with an owner, a due date and a way to check whether they helped. “Improve communication” is too broad to observe. “Include support instructions in the launch readiness check” is something a team can test.
Distribute a concise record that preserves unresolved questions. Agreement on a tidy story is not the same as learning; a good review makes the next project easier to run.