Home Creators Posts Import Register Favorites Logout

Content

We have repeatedly talked about the fact that good instructors don’t interrupt exercises whenever there is a slight nuance to be fixed. Scenario training is a discovery based process and not a choreography. Just stopping the exercise at slightest deviation and correcting a supposed mistake is not only hindering this discovery process, but its also a sign of entirely bad and lazy instruction methods.

The instructor has to carry various burdens and one of his primary burdens is to document and memorize what happens during an exercise. This is a lot of work and requires a lot of capacity. A big part of the actual learning process happens during the AAR (After Action Review) and today we want to address how to conduct a good AAR.

The general architecture of an AAR is simple but important. We don’t change that architecture under any circumstances, there is a reason why the order of topic is what it is. Lets have a short look:

 Baseline: What was supposed to happen.

 Development: What did actually happen.

 Sustainment And Improvement: How did things go?

 Takeaways: How can we improve the next time?

Lets have a closer look at how to execute those paragraphs:

Baseline: The Baseline of an AAR should be executed like a FRAGORD. Meaning, you will list Situation, Mission and supposed Execution. Its important to clearly communicate the commanders intent in two ways here. First of there is the commanders intent of the scenarios mission, but on the other hand there is the commanders intent of the training itself, what was this training supposed to do? Only if we are talking the very same language we can actually discuss things. Getting this one ahead also eliminates mistakes that could also be instructor issues, like for example the target audience not getting the training or intent of the training.

Development: Now we go from start to end and discuss the full execution. Remember that this is a shared reality, you will first off ask the element leader for what happened. After that you will ask subordinate leaders, keep in mind that the actual experience will be very different from a support or an assault perspective. Last but not least you present your impression, which is more of a birds eye perspective. Start to further add deviations to you notes. Keep in mind to stay totally neutral. Remind everyone to keep rank and perceived importance out of the game.

Sustainment and Improvement requires us to compare baseline and mission development. Sustainment is about keeping the good things and what went well, address those first, if you throw the bad things at people first, they might start to feel offended and wont be open for critique. Improvement is essentially about what went wrong and what could be improved. Ask the team leaders about deviations from the original plan and the reason for them. Again, ask subordinate leaders too, maybe supporting fires hadn’t been in place because there was a whole assault element running through a field of fire.

Takeaways: Now its not your turn to tell “How things are done”, its your turn to ask “What should we do better the next time”. This finishes the exploration process. Of course, you have the last word and you can clearly demand things to be done in a certain way, but you need to explain the “why” behind all that. Provide the opportunity for another run and another AAR.

If you structure you AAR like that, you will get the best out of training with as little interruption and as much “flow” as possible. Keep in mind that tactics training is a collective learning exercise and not a drill.

As always, thanks for your attention.

Files

Comments

Thomas Blau

I like that you emphasized that a key part of training is that the cadre need to let the students complete the exercise and then provide the AAR and sustains and improves afterwards. Otherwise you’re not truly able to see how your students are behaving during a given task or context.