The workshop ends. Someone shares a cheerful photo. The team says it went well and returns to the inbox. A week later, the next workshop repeats the same confusing introduction and the same excellent exercise. Neither repetition was a deliberate choice.
The missing step is a review that changes something. Reflection becomes operational when a future action carries its result. Without that connection, even thoughtful discussion can become a meeting about a meeting.
NASA describes its Pause and Learn approach as an adaptation of the after-action review, used during a project as well as afterward. Its guidance emphasizes learning from the intended and actual course of events. Here is a small-team application.
Start with the event, not the team's personality
Choose a bounded piece of work: a product demonstration, a client handover, a publishing sprint or a single campaign. “How we are doing as a company” is too broad for a useful first review.
Bring the original objective and a few relevant artifacts. These might include the brief, timing notes, support questions or the version customers actually saw. Do not reconstruct everything from the loudest person's memory.
State the purpose before discussion begins. You are trying to understand the work and improve the next attempt. If a separate conduct or performance issue requires formal handling, do not disguise that process as an informal learning exercise.
Gather observations before explanations
Give each person a short quiet period to record what they noticed. This allows the facilitator to collect material before the first confident explanation shapes the entire conversation.
Then sort the notes into three columns:
| Column | Fictional workshop example |
|---|---|
| Intended | Participants would complete a first draft during the session. |
| Observed | Several asked where to begin; most finished after a live example. |
| Still uncertain | Whether the instructions, task difficulty or timing caused the delay. |
“People were disengaged” belongs in neither of the first two columns without more detail. What did someone actually do? Close the exercise? Ask for clarification? Leave early for another commitment? Similar appearances can have different explanations.
Preserve a success as carefully as a failure
Reviews can become collections of defects. Ask what should remain and why. Perhaps the live example helped participants begin. Perhaps a simple handover note prevented repeated questions. Record the ingredient that seems worth carrying forward, while acknowledging the evidence is limited.
In the workshop example, “keep the example” is still vague. A more useful instruction is: “Show a rough completed draft before asking participants to create their own, and make the example available beside the worksheet.” Now someone can reproduce the change.
Do not turn every success into a permanent rule after one event. It may depend on the audience, context or task. Preserve the context with the observation so the next team can decide whether it applies.
Choose one change with a visible consequence
A long improvement list is easy to approve and difficult to use. Select a change the team can implement before the next comparable event. Define what you expect to observe if it helps.
For example: “The facilitator will rewrite the opening instruction and introduce the example earlier. During the next workshop, we will note where participants request clarification and whether they can begin the first step unaided.”
That is an experiment, not a promise that all friction will disappear. If a different audience attends, record that difference. If several elements change together, avoid assigning the whole result to one edit.
Leave a handover, not a transcript
Your final review note can fit on one page: event, objective, key observations, unresolved questions, chosen change, owner and next review date. Link the evidence rather than pasting a wall of raw notes into the summary.
At the next planning meeting, open that page first. If the change was not attempted, discuss the obstacle before inventing another improvement. A lesson becomes useful through application, not through being written in a folder named “lessons learned.”
Celebrate the team for making the work more understandable. A strong review can preserve excellent craft, reveal a weak assumption and make the next attempt less dependent on memory. That is a better ending than “great job, everyone” on its own.
For decisions still ahead of you, use a decision journal.
Questions worth asking
When should an after-action review happen?
Hold it while the relevant details are still accessible. You can review a milestone or a single event without waiting for an entire project to end.
How do we stop a review becoming a blame session?
Agree that the meeting examines the work, gather observations before explanations and distinguish a learning discussion from formal performance management.
