> For the complete documentation index, see [llms.txt](https://urd.gitbook.io/compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://urd.gitbook.io/compass/learning-and-adapting/learning-from-experience-and-sharing-insights/after-action-reviews-light-frequent-debriefs.md).

# After Action Reviews: light, frequent debriefs

### <mark style="color:orange;">What is an After Action Review ?</mark>

An **After Action Review** (AAR) is a structured, brief discussion held immediately after an activity, stage or event, to identify the key lessons to be learnt, whilst the details are still fresh in everyone’s minds. It requires no facilitation expertise, no template beyond a single page, and no more than an hour.

It is the entry point of the whole learning spectrum: the habit every team can build first, and the one that feeds the heavier methods described later in this section.

***

### <mark style="color:orange;">**The 4 Core Questions**</mark>

1. **What was supposed to happen?**
2. **What actually happened?**
3. **Why is there a discrepancy (positive or negative)?**
4. **What do we do with this information, for this project, or for the next one?**

> Four questions is already a good starting point for this kind of short, immediate exercise. Resist the temptation to add more questions.&#x20;
>
> The fourth question is the one teams skip most often. An AAR that stops at "what happened" is a debrief, not a lesson learning exercise. It only becomes learning once it is tied to an action.

***

### <mark style="color:orange;">**Making it work: key factors for success**</mark>

**Set a time limit**

30 to 90 minutes, no more, otherwise the method turns into a traditional meeting.

**Create a safe environment**

*T*he goal is to learn, not to assign blame; without this assurance, failures will never be brought to light. If people sense the AAR will be used to evaluate individual performance, honest answers disappear and with them, the only useful part of the exercise.

**Involve the right people**

The team that went through the experience, not just management. The details worth capturing are usually held by whoever was closest to the action.

**Write after, not during**

A one- to two-page summary is enough: context, findings, and the action selected. Writing during the discussion slows it down and shifts attention from talking to note-taking. To the extent possible, try to assign separate roles for facilitation and note taking. You can record the discussion to avoid taking extensive notes.

**Close the loop**

Explicitly link it to a decision, an action item, or the agenda for the next meeting. An AAR that produces nothing visible teaches the team that the exercise doesn't matter, and the practice dies within a few weeks.

| Use an AAR for                                                                                                                            | Don't use an AAR for                                          |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| The end of an activity, a short mission, a field visit                                                                                    | An experience spanning several phases or teams                |
| A near-miss, an incident, an unexpected obstacle                                                                                          | A question that needs input from stakeholders beyond the team |
| A recurring task, to refine it each time it's repeated (i.e. several rounds of distributions, recurring activities with different groups) | A lesson meant for external audiences or the wider sector     |

If what comes out of a debrief turns out to matter more than expected, that's not a failure of the method. On the contrary, it's a signal to move to a structured learning process.

***

### <mark style="color:orange;">Key points</mark>

* Four questions, one page, one hour. Resist adding complexity.
* No safety, no honesty: protect the space before expecting useful answers.
* An AAR without a retained action is just a conversation.
* Frequency matters more than depth: a short debrief done every time beats a thorough one done rarely.

### <mark style="color:orange;">Resources</mark>

{% file src="/files/G3GmcflLBB5MdNHFjB9h" %}