After-Action Review: Learn From a Project in Four Questions

The best time to learn from a project is just after it ends, while details are fresh. A 20-minute after-action review asks four questions: what we expected, what happened, why, and what to change next time, without blame.

By Rohan Rawat

Who this is for and when to use it

This is for project leads, small teams, event organisers, volunteers and individuals. Use it within a few days of finishing something: a product launch, a school fundraiser, a house move, a trip or an exam. It looks backwards to improve the next attempt, which is different from a pre-mortem, which looks ahead before you begin, and from a quarterly review, which is based on time rather than on a specific piece of work.

The four questions

  1. What did we expect to happen? Restate the goal, plan and success measures, using the original brief if you have one.
  2. What actually happened? Describe the events and results as facts: dates, numbers, what was delivered, what was not.
  3. Why was there a difference? Look at causes in the process, information, timing and resources. Ask "why" more than once.
  4. What will we change? Choose actions for next time, and note what to keep doing because it worked.

Run it in 20 to 30 minutes

Invite everyone who played a real part, and choose one person to facilitate and another to take notes. Spend about five minutes on the first two questions together, ten on causes and five on actions, leaving a few minutes to agree how the notes will be stored. If it runs long, stop and schedule a follow-up rather than rushing the actions.

Keep it blame-free and fact-first

The goal is to understand the system, not to find fault with people. Begin with facts before opinions, and phrase causes as "the handover happened late" instead of "Sam was late". Invite the quietest voices to speak first, and thank people for naming uncomfortable points. If someone is criticised personally, the facilitator can bring the focus back to what the process allowed. If a matter involves a safety incident, a formal complaint or legal duties, follow your organisation's own procedure rather than this informal review.

Turn lessons into one to three changes

Long lists of lessons are rarely used. Pick one to three changes that would have the biggest effect, and for each write the action, the owner and a date. A change such as "write a one-page brief before starting" can be shaped with a one-page project brief template. Also record what worked well, so people repeat it on purpose.

Example: a community book sale

Expected: 400 books sorted and priced by Friday, six volunteers, setup done by 9:00 on Saturday. What happened: 320 books priced, four volunteers came, doors opened at 10:15. Why: the donation drop-off ran a week late, volunteer reminders went out only two days before, and nobody owned the setup list. Changes: (1) set a drop-off cut-off date two weeks before the event, owner Asha, by 1 June; (2) send volunteer reminders at one week and two days, owner Ben, with the next event; (3) assign a named setup lead with a checklist, owner Chloe, by the next planning meeting. Keep: the labelled boxes, which saved time.

Store the lessons where you will find them

A review that sits in someone's notebook will not help the next project. Save the notes in a shared folder or with the project file, name them with the project and date, and link them from the plan for the next similar project. At the start of each new project, read the last review for five minutes.

A solo version for personal events

You can use the same four questions alone after a trip, a move, an exam or a family event. Write a short answer to each in a notes page the same day or the next, pick one change, and put it where you will see it next time, such as on your packing list or study plan. Five minutes is enough.

Edge cases

  • The project failed badly. Wait a day or two if emotions are high, but do not skip the review.
  • Senior people are present. Agree beforehand that everyone is equal in the room, and have the leader speak last.
  • Remote teams. Use a shared document so people can add points in advance, then discuss the themes live.
  • Nothing went wrong. Review what made it work, and what luck contributed.
  • Actions go nowhere. Check the previous review's actions first at the next meeting.

After-action review template

AFTER-ACTION REVIEW

Project/event: ____________   Date: ________
Facilitator: ________   Note-taker: ________   Present: ________

1. What did we expect?
______________________________________
2. What actually happened? (facts)
______________________________________
3. Why the difference? (process, not people)
______________________________________
4. What will we change? (1-3)
Action ____________  Owner ______  Date ______
Action ____________  Owner ______  Date ______
Keep doing: ____________________________
Stored at: ____________________________
Recap

After a project, ask what you expected, what happened, why and what to change. Keep it short and blame-free, choose up to three actions with owners and dates, and store the notes for the next project.

Next step

Choose a recent project or event and book 20 minutes this week to run the four questions. Plan ahead for the next one with a pre-mortem, write a one-page project brief, or zoom out with the quarterly personal review.