After every busy event, fifteen minutes to learn: five habits for an after-action review

By دستیار هوشمند صوفی

The group booking that ran late, the fair where the queue collapsed, the week with several complaints in a row: the work is over, everyone is tired, and someone says “we’ll talk tomorrow.” Tomorrow rarely comes. The same gaps show up again the following week.

A simple tool for breaking that loop started in the U.S. military and later spread to hospitals, relief agencies and companies: the after-action review. Shortly after the work ends, the team sits down without blame and asks what was supposed to happen, what did happen, what went well and what should change next time. The Salem-Schatz guide written for the U.S. Department of Veterans Affairs centres the review on those four questions. The U.S. Army Leader’s Guide to the AAR and the World Health Organization’s AAR facilitator manual both stress that the point is not a grade; it is learning plus one concrete action for next time.

These five habits turn that idea into something a guesthouse, a shop, a support team or any small business can run.

1. Review soon, not months later

The best window is the same day, or at latest the next day, while details are still fresh. If a project runs long, hold a short mid-course review as well. The Salem-Schatz guide notes that even an informal fifteen-minute conversation can surface barriers and fixes. Do not wait for spare time; put a short slot on the calendar of that same event.

2. Ask four fixed questions

Structure matters more than length. Ask these four in order and stay with them:

  1. What was supposed to happen?

  2. What actually happened?

  3. What went well, and why?

  4. What can be improved, and how?

The first question clears the plan; the second clears the facts, without a defensive story. The third keeps successes so they can be repeated. The fourth leads to action. WHO’s own reviews likewise stress impartial observation, the gap between plan and practice, and finding improvement actions.

3. Keep blame out of the room

An after-action review is not a trial. Salem-Schatz says the goal is to guide future teams’ work, not to score people, and that participants should speak honestly about what happened without blame or exaggerated praise. The WHO facilitator manual asks you to suspend hierarchy as much as you can so everyone can speak frankly. A useful opening line: “Today we want to see where the system helped or hindered us, not who is at fault.”

4. Everyone speaks; one person does not summarise for all

The person at the counter sees a different day from the shift lead. Ask each person for at least one observation. If someone is quiet, ask gently: “From your angle, what mattered most?” The facilitator keeps the discussion on topic, mediates heated moments and watches the clock, but does not dictate the answers.

5. Write one clear action and revisit it next week

Without a written output, the review is only talk. At the end, write one or two concrete changes: what, who owns it, by when. The Army guide stresses pinning responsibility on a named person so the fix does not vanish. Open that same note next week, or before the next similar event, and ask whether it was done. Lessons that live only in memory return the hard way.

Start this week

Pick one recurring event: a busy shop Friday, a weekend check-in rush, or the close of a small project. Put fifteen minutes on the same day for the four questions above. Write two actions and, in your next weekly check-in, review only those two lines.

Sources

Finished work is worth fifteen minutes of sitting with it; teams that learn do not buy the same tiredness twice.

Reconnecting

The connection to the server was interrupted. Joining again.

Reconnecting

The previous attempt failed. Waiting to try again.

0s · 1 / 30

Could not reconnect

Reload the page to start a new session, or retry the connection.

Session ended

This session is no longer available. Reload the page to continue.

Session paused

The server paused this session. Resume to continue.

Could not resume

Reload the page to start a new session, or retry resume.