Skip to content

7 min read

After Action Review

Summary

An After Action Review (AAR) is a short, structured team debrief built around four questions — What did we expect? What actually happened? Why the difference? What do we do differently next time? — run after every milestone or action, not just at the campaign’s end.

Body

The AAR was developed by the U.S. Army and adopted across project-management and aid-evaluation practice. The campaign-adapted version is a 30–60 minute debrief the team runs after every milestone or named action. The four questions are:

  1. What did we expect to happen? What was the plan, the forecast, the assumption set?
  2. What actually happened? What did the data, the response, the outcome show?
  3. Why the difference? What in the assumption set was wrong, and what in the context shifted?
  4. What do we do differently next time? What concrete change enters the ToC, the risk register, the plan or the kanban?

The Commons Library’s Campaign Accelerator trains campaigners to run an AAR after each action and to file the lessons back into the theory-of-change and the risk register [source: commons-library]. The ALA Frontline Advocacy Toolkit’s evaluation chapter recommends the same discipline in library advocacy, with the explicit warning that skipping AAR when an advocacy project “appears to be finished” loses the lessons the next project depends on [source: ala-frontline]. The People Power Manual pairs the AAR with the Evaluation and success indicators chapter: AAR is the team’s internal learning mechanism; outcome evaluation is the external report [source: people-power-manual].

A useful AAR has five properties:

  • Blameless. The fourth question is forward-looking — what do we do differently? — not backward-looking — whose fault was it? Blame shuts down the information the AAR is designed to surface.
  • Time-bounded. 30–60 minutes. An AAR that runs for two hours has become a debate.
  • Owner of the lesson. Each AAR produces at least one named change to a specific document (ToC, risk register, plan) and a named owner.
  • Run even on a win. Wins hide mistakes — the why the difference? question is often most useful on a campaign that hit its goal through luck rather than the assumed mechanism.
  • Run at every milestone. Not just at the campaign’s end. The Commons Library treats the AAR as the rhythm that closes the campaign-cycle feedback loop [source: commons-library].

A common failure mode is to treat the AAR as a meeting rather than a discipline. The ALA Frontline Advocacy Toolkit warns that an AAR without a named owner of the change becomes a discussion without a result [source: ala-frontline]. The People Power Manual adds that an AAR that does not update a document is decorative: the lesson should enter the ToC, the risk register, the campaign plan or the kanban, and the document should change visibly [source: people-power-manual]. The Sierra Club’s AAR Worksheet, used inside the Sierra Club’s volunteer-leadership pipeline, operationalises the four-question structure as a one-page printable that a chapter leader can fill in within thirty minutes at the end of an action — no separate facilitator required — and pairs each question with structured sub-prompts (under why the difference: What worked well? / What didn’t work?) that help a less experienced leader run the debrief without prior training [source: sierra-club-aar]. A similar French-language tradition (the retour d’expérience — sometimes shortened to REX) pairs the four-question structure with a issues juridiques block that tracks arrests, police interviews, and follow-up legal proceedings; that block is the critical post-action learning in high-risk NV contexts where an AAR doubles as legal-team handoff.

Use it for

Closing the feedback loop at every milestone of the the-campaign-cycle; turning campaign experience into organisational learning; diagnosing why a tactic worked or did not; running a coalition debrief; producing the lessons the next campaign’s theory-of-change needs.

Examples

Learn more

Open Questions

(none)

FAQ

What is an After Action Review?

An After Action Review (AAR) is a short, structured team debrief built around four questions — what did we expect, what actually happened, why the difference, and what do we do differently next time — run after every milestone or action, not just at the campaign’s end.

What are the four questions of an AAR?

The four questions are: what did we expect to happen — the plan, forecast, or assumption set; what actually happened — the data, response, or outcome; why the difference — what in the assumption set was wrong and what in the context shifted; and what do we do differently next time — what concrete change enters the theory of change, risk register, plan, or kanban.

What properties make an AAR useful?

A useful AAR has five properties: it is blameless, with the fourth question forward-looking rather than backward-looking; time-bounded to thirty to sixty minutes; producing at least one named change to a specific document with a named owner; run even on a win, since wins hide mistakes; and run at every milestone, not just at the campaign’s end, as the rhythm that closes the campaign-cycle feedback loop [source: commons-library].

What failure modes does the AAR literature warn against?

A common failure mode is treating the AAR as a meeting rather than a discipline. ALA Frontline warns that an AAR without a named owner of the change becomes a discussion without a result. People Power Manual adds that an AAR which does not update a document is decorative: the lesson should enter the theory of change, risk register, plan, or kanban. [source: ala-frontline] [source: people-power-manual]

What does the Sierra Club AAR Worksheet add?

The Sierra Club’s AAR Worksheet, used inside the Sierra Club’s volunteer-leadership pipeline, operationalises the four-question structure as a one-page printable that a chapter leader can fill in within thirty minutes at the end of an action, with no separate facilitator required. Each question is paired with structured sub-prompts, including what worked well and what didn’t work under why the difference, that help a less experienced leader run the debrief without prior training. [source: sierra-club-aar]

Sources & verification

Last verified: 2026-07-09