What is an after action review?
An after action review (AAR) is a short, structured debrief built on four questions: what did we expect to happen, what actually happened, why was there a difference, and what will we keep doing or change next time. The US Army made it standard practice, and hospitals, emergency services and businesses have used it since, because it suits any team that has just finished something and wants to learn from it while the details are fresh. It's lighter than a full post-mortem, and nothing has to have gone wrong. Here's how it runs in TeamRetro. Everyone adds their own observations privately first, so the most senior person in the room doesn't set the story before anyone else has written a word. Ideas are then grouped, discussed and voted on, which keeps the session on the gaps that matter instead of every detail of the day. The last question turns the discussion into lessons learned, and the actions you agree on get an owner and a due date, so they come up again at your next session. Use it after a launch, an event, a client pitch, a busy shift, a training exercise or a sprint that didn't go as planned. Keep it short: most teams finish in 30 to 45 minutes. Export the report when you're done, so the lessons stay findable for the next team in the same situation.
After action review format
What did we expect to happen?
What was the plan, the goal and the standard we aimed for?
Start with the plan, not the outcome. Ask what the goal was, what success looked like and what standard the team was working to. Keep it factual and save judgment for the later questions. If people remember the plan differently, capture each version: a plan that wasn't shared is often the first lesson of the session.
What actually happened?
What really happened, step by step, from each person's view?
Build a shared account of events before anyone explains them. Each person saw a different part of the work, so ask what they saw and when, not what they think caused it. Agree on the order of events if it matters. If blame starts creeping in, steer it to the next question.
Why was there a difference?
What explains the gap between plan and reality, good or bad?
This is where the learning sits. Look at gaps in both directions: when something went better than planned, ask why as well, so you can repeat it. Keep asking why until you reach a condition the team can change, such as a missing step, an untested assumption or an unclear owner, rather than a person to blame. Use voting to pick the two or three gaps worth the most discussion.
What will we keep or change?
Which lessons learned will we carry into the next one?
Turn each gap into a lesson someone outside the room could use: a step to add, a check to run, a habit to keep. Separate what the team can change itself from what needs someone else's help. Then agree on a small number of actions, each with an owner and a due date recorded in TeamRetro, so they come up at your next session. Two or three owned actions beat a long list nobody follows up on.
When to use this retrospective
- A launch, event, campaign or pitch has just finished and you want to compare the plan with what happened while it's still fresh
- Something went better than expected and you want to know why, so you can repeat it on purpose
- A shift, exercise or busy period didn't go as planned and you need a short, blameless debrief, not a full investigation
- Your team runs the same kind of work often, such as releases, onboarding or client deliveries, and you want each one to teach the next
- You want a debrief that fits in 30 to 45 minutes instead of a half-day post-mortem
Suggested icebreaker questions
- In one word, how did it go compared with what you expected?
- What is one moment from this piece of work you'll remember?
Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →
Ideas and tips for your retrospective meeting
- Run it within a day or two. An after action review works because it captures detail before people forget it or retell it
- Say the ground rule out loud: you're reviewing the plan and the work, not grading people. Ask the most senior person to speak last
- Give the first question real time. If the team can't agree on what was supposed to happen, that's a finding in itself
- Look at what went better than planned as well as what went worse. A win you can't explain is hard to repeat
- Keep reviews short and regular. Several small reviews after routine work teach more than one big review a year
- Open each review by checking the last one's actions. Knowing they'll be checked is what gets them done
Frequently asked questions
What is an after action review?
What are the four questions of an after action review?
How is an after action review different from a post-mortem?
How long does an after action review take?
Who should take part in an after action review?
How do you capture lessons learned from an after action review?
Related templates
Close out last year and set this year's team goals.
End of Year Retrospective
Look back on your team's year and plan the next one
Project Kickoff Planning
Agree on goals, risks and milestones before work starts.
Project Post Mortem Template
Review any project or incident, capture lessons learned