Lesson Overview
A section does not improve by accident. It improves because, again and again, it looks honestly at what it has just done, finds where its intent and its execution parted company, and changes something before the next task. A section that does this gets better fast. A section that does not repeats the same handful of mistakes for years without ever understanding why. The tool that turns a task into a lesson is the after-action review, and running one well is among the most useful skills a junior leader takes from this course.
Lesson 06 took you onto the ground to lead a section through a field task. This lesson is what happens once that task is over and the section gathers, muddy and tired, to make sense of it. You met the after-action review once before: Foundations of Military Leadership named it as one face of Evaluate and gave you three plain questions to ask. That was the idea; this is the craft. A short method you can run anywhere, the honesty that decides whether it works, and the harder business of turning what you find into a change that sticks.
The review is not a form, a parade, or a ritual. It is a habit of mind made into a habit of the section, and its whole power comes from honesty: a review that flatters everyone teaches nothing, and one that hunts for someone to blame teaches people to hide. By the end you will be able to explain why the after-action review is the engine of a learning section, run one using the four questions, set and hold the honest, blame-free, accountable tone that makes it work, capture lessons so they change behaviour and feed back into training and standards, and explain why a leader who can be corrected by their own soldiers is stronger for it.
Key Terms
- After-action review (AAR): the structured conversation a section holds after a task, asking together what was meant to happen, what actually happened, why there was a difference, and what to do differently next time.
- Hot debrief: a very short review held on the spot, within minutes and often where it happened; the field cousin of the full AAR.
- Lesson: not something merely noticed, but a change made because of it. A lesson that does not change behaviour has been observed, not learned.
- Blame-free: attacking the problem and not the person, so people speak openly. Not the same as consequence-free.
- Accountable: owning honestly what you did, what you did not do, and what you will change. The partner to blame-free.
- Sustain and improve: the two halves of every finding, what to keep and what to fix. A good review names both.
- Tone: the climate of the review, honest or guarded, set above all by the leader and by whether they own their own mistakes first.
Why the after-action review matters
Two sections train side by side for a year. Same kit, same drills, same tasks. At the end one is markedly better: steadier, quicker, surer of itself, and an instructor who did not know them would assume it had the better soldiers. It usually did not. What it had was the habit of reviewing its work honestly and changing because of what it found, and over a year that habit compounded into real capability. The other section worked just as hard but never stopped to learn, so it carried the same mistakes from January to December and arrived no wiser than it began.
That is the whole case. A section improves at the speed it learns, and the review is how it learns. Experience on its own teaches nothing: do a task badly ten times without examining why, and the tenth attempt is as poor as the first, only better practised at being wrong. What turns experience into improvement is honest reflection, done together and turned into a change. The review is the hinge between having an experience and learning from it. It pays a second dividend too: a lesson the section reasoned out for itself is believed and acted on, where a lesson handed down is merely obeyed. Foundations called this the reason a lesson sticks; running the review well is how you make it happen on purpose.
WHY THE AAR IS THE ENGINE OF A LEARNING SECTION
Without it: With it:
do a task do a task
| |
move on REVIEW it honestly
| |
do it again (same way) find the difference, decide a change
| |
same mistakes do it again (changed)
| |
no better in a year better each time -> compounds
Experience alone does not teach. Reviewed experience does.
For a small humanitarian home-defence force the argument is sharper. The Army is young and will rarely have the advantage of numbers; its edge has to be the quality of its people and how fast they improve. It has no long operational history, no shelf of campaigns whose lessons an earlier generation paid for. Almost everything this Army knows it will learn from its own tasks, most of them ordinary, many in support of the civil authorities. That makes learning honestly from action a necessity, not a refinement: a force that learns quickly from small things will be ready when a large thing comes.
The method: four questions
The after-action review is rightly known for being simple, and you should keep it so, because a complicated review does not get held. At its heart are four questions, asked in order, of the whole section together:
- What was meant to happen?
- What actually happened?
- Why was there a difference?
- What will we do differently next time?
That is the entire method. You can run it from memory, on the ground, with no paper, in the time it takes to drink a brew. Foundations gave you three questions as a first sketch; this is the working form. It splits "why" into two steps, naming the difference and then explaining it, and it makes the change a step in its own right, because the change is the point of the exercise.
THE FOUR QUESTIONS (run them in order, every time)
1. WHAT WAS MEANT <-- the plan, the intent, the standard
TO HAPPEN? (agree this first, or the rest drifts)
|
v
2. WHAT ACTUALLY <-- the facts, plainly, no blame yet
HAPPENED? (build one shared, honest account)
|
v
3. WHY WAS THERE A <-- the real cause, not the surface
DIFFERENCE? (keep asking "why" past the easy answer)
|
v
4. WHAT WILL WE DO <-- the change: specific, owned, doable
DIFFERENTLY NEXT TIME? (this is the whole point; do not skip it)
Work them through with a concrete case. A section is tasked to move relief stores from a delivery point to a community hall and lay them out by mid-morning, before families arrive at midday. They finished, but late, and in some disorder.
What was meant to happen. Agree out loud what the task actually was: stores laid out by the far wall, in order, by mid-morning, so the hall was ready and calm before the families came. This sounds redundant but is not, because half of all confusion comes from people having held different pictures of the task all along. Let anyone who heard it differently say so now; often that is the first lesson.
What actually happened. Build an honest account in plain facts, no judgement yet. The water was moved quickly and well; the blankets were carried over in a rush near the end, stacked where they partly blocked a fire exit, and had to be moved again; the job finished twenty minutes late, with families already arriving. Agree the facts before anyone reaches for a cause, because the moment "why" starts, the account turns to argument and the facts bend to fit whoever is defending themselves.
Why was there a difference. This is the heart of the review and the step most often botched, because people stop at the first answer. "The blankets went wrong because Private A stacked them in the wrong place" is an answer, but it is the surface, and it is a person, not a problem. Keep asking. Why were they stacked there? Nobody had said where the exits were. Why was the stacking rushed? Too long on the water left too little time for the blankets. Why? The plan never broke the job into its parts or set a time for each. Now you have something worth fixing: not "Private A is careless" but "our plan did not allocate time across the serials or mark the exits," which sits with the plan and the briefing, that is, with the leader.
What will we do differently next time. The review earns its keep here or not at all. The change must be specific enough to act on, owned by someone, and within the section's power. Vague resolutions like "be better organised" change nothing. Concrete ones change behaviour: "In orders we will split a task like this into serials with a time for each, and we will always brief the fire exits and other hazards before we move anything." Without this step the first three questions are an interesting talk about the past; with it, the past has improved the future.
Running one well
A sound method runs badly if the review is run badly. A handful of practical disciplines make the difference.
RUNNING AN AAR: THE PRACTICAL DISCIPLINES
SOON hold it while it is fresh, ideally same day;
memory fades and excuses harden overnight
EVERYONE whole section present; the soldier who saw the
THERE thing the leader missed is often the junior one
EVERYONE anyone may speak freely, regardless of rank;
FREE TO SPEAK rank in the room kills the honesty you need
ON LEARNING the question is "what do we change?", never
NOT BLAME "whose fault was it?"; problem, not person
LEADER the leader speaks last on others' parts and
GOES FIRST first on their own, and owns their mistakes openly
SHORT a few minutes for a small task; long reviews
do not get held, and held is what matters
Hold it soon. The review works best while the event is fresh, ideally the same day, sometimes within minutes. Memory fades fast and unevenly: the awkward parts soften and the excuses firm up, so a review held a week later examines a story the section has already half-rewritten in its own favour. For a small action, hold a short hot debrief on the spot, standing where it happened, and save the fuller sit-down for what warrants it.
Get everyone there, and let everyone speak. The whole section attends, and this is the source of the review's value, not a courtesy. The person who saw what the commander could not is very often the most junior: the soldier at the back of the move who watched the blankets go to the wrong place while the commander was forward sorting the water. If only the leaders speak, that knowledge never reaches the room. Draw the quiet ones out, "you were at the back, what did it look like from there?", because the soldiers most worth hearing are often the least likely to volunteer.
Make it safe to speak honestly. Everything rests on this, and the next section is given over to it. The practical point for now: people tell you the truth only if telling it is safe, and they watch the leader closely in the first minute to find out whether it is.
Keep it on learning, and keep it short. The one question the review exists to answer is "what do we change?" Drag the conversation back when it wanders into war stories or grievance, and stop when you have what you need. A few honest minutes that produce one real change beat an hour that produces a fine feeling and nothing else. Brevity also keeps the habit alive: a short review gets held after every task, while one that drags gets held only after disasters, by which time the small lessons that would have prevented the disaster were all missed.
Honest, blame-free, and accountable
Here is the discipline that makes or breaks the review, and it pulls two ways at once. The review must be blame-free, or people stop telling the truth; and it must be accountable, or it becomes a comfortable session of explaining every fault away. Hold only the first and you get honesty without improvement; hold only the second and you get a blame-hunt that kills honesty. The way to hold both is one rule: attack the problem, not the person.
The difference is exact, and worth seeing side by side:
ATTACK THE PROBLEM, NOT THE PERSON
PERSON (blame; people go quiet) PROBLEM (learning; people open up)
"You blocked the exit." "The exits weren't briefed, so the
stack went to a bad place."
"Why were you so slow?" "We ran out of time. Where did the
time go, and what would buy it back?"
"Whose fault was the mix-up?" "Where did the message break down,
and how do we make it clearer?"
Same facts, both honest. The left shuts the section down and
teaches people to hide. The right keeps it open and finds the fix.
Blame-free is not consequence-free: it means we fix the cause
together, and each of us still owns our own part of it.
The problem-focused version is not softer than the blame-focused one. It is more demanding, because it goes after the real cause instead of stopping at a convenient name. Blame is the lazy option: it points at a person, feels like progress, and changes nothing, because the cause is still there waiting to trip the next soldier who carries the last load.
Blame-free does not mean consequence-free, or it curdles into "nobody is responsible for anything." Genuine negligence, dishonesty, or a refusal to meet a known standard are matters of discipline and conduct, dealt with properly and usually in private, as Military Customs, Discipline, and Conduct teaches and as the Foundations warning against a "zero defects" culture assumes. The review is not the place those are settled, and it must not become a court. What it handles is the ordinary, honest gap between intent and execution: the rushed stack, the missed brief, the message that did not land, the decision that looked right at the time and turned out wrong. Almost all of what a section needs to learn lives in that gap, and almost none of it is anyone's fault in a way that blame would help.
Above all, the tone is set by what the leader does first, not by what the leader says, and a section will be exactly as honest as its leader and not one degree more. Open by owning your own mistake plainly, "I gave you the task without breaking it into timings or telling you where the exits were, and that is what put us under pressure at the end," and you have shown the section that this is a place where people tell the truth about themselves. Open instead by asking who blocked the exit and you have taught them, in one sentence, that this is a place where faults are found and named, and from that moment everyone is defending themselves instead of helping you learn. So the rule is firm: speak last about everyone else's part and first about your own. The team watches that opening moment more closely than anything else, and from it decides whether the review is real or a ritual.
Capturing the lesson so it changes behaviour
A review that ends in a good conversation and a shared nod, then nothing, has failed, however honest it was. The point is not insight; it is change. A lesson is not something you noticed but something you altered because of it, and the test of learning is simply whether the section does the thing differently next time. By that test, most "lessons" in most organisations are never learned: they are observed, agreed, and quietly forgotten, and the same problem returns on the next task to be agreed and forgotten again. A junior leader guards fiercely against this, because it is the commonest way the whole effort of reviewing is wasted.
The discipline that prevents it is to close the loop: name the change, give it an owner, record it, and check it next time.
FROM REVIEW TO CHANGE (close the loop, or the lesson leaks away)
1. NAME state the change in plain, specific words
"brief the exits and hazards before we move anything"
2. OWN give it to someone, even if that someone is you
"I'll add it to the orders format as a standing line"
3. RECORD write it down somewhere it will be seen again
a section notebook; a line passed up the chain
4. CHECK look for it next time, and review whether it held
"last time we said we'd brief exits; did we? did it work?"
A lesson observed but not acted on is not learned, only noticed.
The loop is closed only when the next task is done differently.
Naming and owning a change keeps it from evaporating in the moment; recording it keeps it from fading between tasks, and need be no more than a line in a section notebook. Checking it next time turns a one-off resolution into a real change of behaviour, and it has a second effect: when the section sees that last review's lessons are genuinely acted on, it takes the next review seriously.
Some lessons are bigger than the section and must be fed back rather than merely kept. If a review keeps surfacing the same problem, or one that other sections will meet too, a gap in a drill, a weakness in the standard kit, a briefing format that keeps failing, the lesson belongs up the chain of command, so the whole Army learns it once instead of every section learning it the hard way. This is the staff discipline of honest review that Emergency Preparedness and Civil Resilience describes the Army lending to the wider national effort, and it begins here, with a junior leader willing to pass a hard lesson upward.
The most important place a lesson goes, though, is back into the section's own training and standards. Lesson 03 taught you to set and hold the standard; the review is one of the chief ways the standard improves over time, because a lesson learned becomes the new standard the section trains to. The blanket-stack lesson does not stay a story about one morning; it becomes a standing line in how the section briefs every task, drilled until automatic, exactly as Module 02 of the Basic Training Manual taught that standards become reliable only when rehearsed under friction until they need no thought. A lesson fed back into training is a lesson made permanent.
Doing it routinely
The last discipline matters most over a career: hold the review routinely, after the small things as well as the big, until it is a habit and not an event. There is a strong temptation to reserve it for the major exercise or the thing that went badly wrong, and to skip the ordinary daily serials that make up almost all of a section's life. That is backwards, for two reasons.
First, the small routine reviews are where the cheap lessons live, caught while they are still small mistakes and not yet expensive ones. A section that reviews only its disasters learns only from disasters, at the highest possible price, after the failure has already cost something. The ninety-second review after a routine task, the kind Foundations described a good second-in-command holding after every serial, is the cheapest training a section ever gets. Second, a review held only after failures is always associated with failure, so a section comes to dread it and grow defensive. Held after everything, win or lose, it loses that sting and becomes simply what the section does at the end of a task, as ordinary as cleaning weapons, and a routine review is one the section relaxes into and is honest in. Routine is what makes the review safe, and safe is what makes it work. Review what went well, not only what went badly: the section needs to know what to keep as much as what to change, and a review that only ever finds problems wears it down and teaches it that the review is a punishment.
The leader's humility
The review asks one more thing of a junior leader, and it is the hardest, because it runs against how a new leader often thinks they must appear. It asks the leader to be corrected by their own soldiers, openly, in front of the section, and to treat that as a good thing. This feels at first like a threat to authority. A new leader, unsure of their standing, can fear that admitting a mistake, or letting a private point out a flaw in the orders, will cost them respect, and the instinct is to defend the plan and protect the appearance of always being right. That instinct is exactly wrong, and learning why is part of growing from a soldier into a leader.
It is wrong because soldiers do not respect a leader who is never wrong; they have never met one, and a leader who pretends to be one they quietly stop believing. What they respect, and will follow into real difficulty, is a leader who is honest about their own mistakes and plainly more interested in getting it right next time than in having been right last time. When you own your error and change because a soldier told you, you do not lose authority. You demonstrate the self-awareness and honesty Foundations named as foundations of character, and you show that the standard of honesty applies to you first. That builds more authority than being right ever could, because it rests on trust rather than rank. The willingness to be corrected by those you lead is a strength, and a particular mark of the leadership a humanitarian force in the service of The Prince ought to grow. A leader who can be told by their youngest soldier "the brief did not tell us where the exits were," and answer "you are right, that is on me, and we will fix it," is a leader a section will trust with far more than the laying-out of a hall. Humility in the review is not the absence of authority. It is authority of the deepest kind.
In Practice: The Hot Debrief at the Pumping Station
A small RKA section has spent a hard afternoon alongside the civil authorities during a flood, filling and placing sandbags around a pumping station to keep the water out and the pumps running. The task was finished and the station held, which is the outcome that matters. But the section commander, a junior non-commissioned officer not long in the appointment, knows that "it worked out" is not the same as "we did it well." So before the section breaks for the rest it has earned, the commander gathers everyone by the wall of bags they have just built and runs a short hot debrief while it is fresh.
The commander goes first, and goes first on their own part. "What we were meant to do was get a bag wall up around the vulnerable side before the water reached it, tied in at the ends, and we did. But I want us to learn from it, so I will start with mine. I set us all filling at one point, and we nearly ran out of filled bags at the wall while everyone was still at the pile. That bottleneck was my call, and it cost us time we did not have to spare." Having opened by owning a mistake, the commander has told the section, without a word of instruction, that this is a place where people tell the truth about themselves, and the section follows. They build the account together, draw out the quietest soldier (who was on the low corner and saw it was the weak point all along), and push the why past the easy answer to the work not being split into fillers, carriers, and placers, and the tie-in never being shown before they started.
THE PUMPING-STATION HOT DEBRIEF, IN FOUR QUESTIONS
1. MEANT bag wall up around the vulnerable side in time,
high enough, tied in at the ends -> achieved
2. ACTUAL wall held; but a bottleneck left placers waiting,
and the end bags were not tied in and had to be redone
3. WHY work not split into fillers/carriers/placers with the
right numbers; tie-in never shown before we started
4. CHANGE 1) split a bag wall into balanced fillers/carriers/
placers from the outset (commander owns this)
2) show and check the tie-in before we begin (2ic)
-> recorded in section notebook; both passed up the chain
Then the change, specific and owned. Next time a bag wall will be split from the start into fillers, carriers, and placers in the right proportion, and the commander takes that one; the tie-in at the ends and corners will be shown and checked before anyone starts, and the second-in-command takes that one. Both go into the section notebook that evening, and because the section keeps meeting tasks like this alongside the civil authorities, the commander passes both lessons up the chain, so other sections do not have to find the same gaps in the same cold water. None of it took more than a few minutes, none of it named a culprit, and all of it will make the section quicker and surer the next time the water rises. The same honest reflection runs through the Army's other practical courses: it is how Combat First Aid asks a carer to weigh their own conduct after treating a casualty, and how Emergency Preparedness and Civil Resilience expects a crisis to be reviewed once it has passed.
Check Your Understanding
- State the four questions of the after-action review in order, and explain what each is for. Why is "what was meant to happen" worth agreeing out loud first, and why does the method split "why" into naming the difference and then explaining it?
- The review must be both blame-free and accountable, held together by "attack the problem, not the person." Take the soldier who blocked a fire exit with a badly placed stack, and show the difference between a person-focused handling and a problem-focused one. Why is the problem-focused version not the softer of the two, and what does "blame-free does not mean consequence-free" mean in practice?
- A lesson observed but not acted on is not learned, only noticed. Describe the loop a junior leader closes to turn a finding into a real change of behaviour, and explain why the review should be held routinely after small tasks as well as big ones, rather than reserved for things that went badly wrong.
Reflection (write a short paragraph): This lesson argues that a section improves at the speed it learns, that the review is how it learns, and that it works only if it is honest, which means the leader must go first and own their own mistakes. Think of a real situation, in the Army or out of it, where a group either learned honestly from what it did or failed to. Using the four questions, work through what was meant to happen, what actually happened, why there was a difference, and what should have changed. Then ask the harder question of yourself: when you are corrected by someone you lead or someone junior to you, what is your honest first reaction, and what would it take to treat that correction as the strength this lesson says it is rather than the threat it can feel like?
Summary
- A section improves at the speed it learns, and the after-action review is how it learns. Experience alone teaches nothing; honestly reviewed experience compounds. This makes the review essential to a young force with little history of its own.
- The method is four questions, asked of the whole section in order: what was meant, what happened, why the difference, what we change. Agree the intent first, get the facts before the causes, push "why" past the first easy answer, and make the change specific, owned, and doable.
- Run it soon while it is fresh (a hot debrief on the spot for small actions), with everyone present and free to speak regardless of rank, focused on learning not blame, and short enough that it actually gets held.
- It must be blame-free yet accountable, held together by attacking the problem and not the person. Blame-free is not consequence-free, and the tone is set by the leader, who goes first and owns their own mistakes.
- Capture the lesson or lose it. Name the change, give it an owner, record it, and check it next time, feeding bigger lessons up the chain and back into the section's training and standards (Lesson 03) so they become permanent.
- Hold the review routinely, after small things as well as big, and review what went well as well as what went badly. Accept correction from your own soldiers as a strength: it builds more authority than being right ever could. This builds on the Evaluate action of Foundations of Military Leadership and on the honest review used in Emergency Preparedness and Civil Resilience and Combat First Aid.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia