team development

That After Action Review (AAR) Lasted Forever - Rethinking AARs

My back was on fire, I was nodding in and out. My neck was killing me from the night vision goggles pulling my head down. It was 12:45 AM and I was listening to my Company Commander and First Sergeant drone on during their 30+ minute after action review. They were talking to one of my Squads who had just completed their night run during a live fire training exercise. It was brutal. By this point, the guys were completely zoned out. This was their final rep, having trained for 14+ hours that day…they just wanted to go to sleep.

The Commander and First Sergeant just wanted to impart their years of experience and help the Squad become the most lethal they could be. We were on alert and could deploy at any minute to the far reaches of the earth. The team had to be ready to get into a firefight tomorrow, and win… big.

However, I, nor any of the team remember hardly anything that was said. Lack of focus and length killed the message.

The Endless AAR

Anyone in the military reading this has sat through the ungodly long AAR. Laundry lists of action items are taken down to revisit or fix. In some cases a lengthy AAR is required. However, if we want a team to improve, providing a laundry list of fixes is counterproductive…especially in iterative training.

A team at most can take a few things, work on them before the next run, and execute. Have you ever heard of the jack of all, master of none?…well that will happen when a team has a million things to work on in a short period of time. Lack of focus kills.

As the evaluator, it is in our nature to want to nitpick and list everything that went right/wrong. We want to help our teams be the best. But from a human psychology standpoint, we are failing them.

Changing Your Approach - Keep it Simple

My favorite rule for AARs is the same for briefing…be brief, be brilliant, be gone. Let the team go to work, then track performance based on previous feedback.

I had seen a Ranger Battalion Commander ruthlessly grill his team on how to run AARs during iterative training. He would force the team to come together, go through everything, then pick the top 3 things the team needed to work on. He also kept these feedback notes for each Platoon on a 3x5 card in his pocket. This was one of the tools he used to rack and stack his Platoon Leaders on their annual evaluation.

The group would come together and give 3 sustains and 3 improves. Now you may be thinking…oh goodness, the horrible 3/3…I’ve seen this so many times. But in this scenario, it makes sense!

Three focused things that went well..build them up, and three areas of improvement.

One More Trick…Track Their Progress

But wait it gets better. Keep track of what they were supposed to work on and bring it back out to check during the next run.

Feedback was written on a notecard and the Battalion Commander kept them in his pocket. On the next run, this was brought up in the group discussion. Ok, last time this Platoon did X, Y, and Z. We told them to work on 1, 2, 3. What did they improve on and what else do they need to work on? The process with the evaluators would go again. In private cover all the pros/cons then bring the focused list to the Platoon. 5-10 minute AAR and keep them moving. Give them a focused list to work on. An individual would be selected prior to coming together to cover each of the sustains/improves with the team (usually the subject matter expert or the person who had the best vantage point).

This method worked wonders. It forced the AAR to only focus on the important points and allowed the team to be able to stay engaged.

If there was something that needed to be addressed further or specific questions that didn’t pertain to the group, the evaluator would pull aside that individual and cover them.

Watch for Outliers Giving a Second AAR

The danger with follow up conversations is that sometimes became the AAR we were trying to avoid. As the senior leader, you have to keep an eye on this because it defeats the point. We spent all this energy to focus the team then someone else pulls them aside afterwords to give them the 20-30 minute AAR. They can’t comprehend it…it’s just too much.

Implementing as a Company Commander

I never forgot this night on the Squad Live Fire lane. As a Company Commander, I vowed to change our approach. I took this focused AAR approach during our training.

Ahead of time, I explained the method to our team, appointed someone to keep a running list of items that they would hand to the team. We also kept this list and compiled everything that we gave to the Platoons after the event. This also helped us see trends.

I kept my notecards to track each iteration. This also helps you keep straight 16+ teams. It can be difficult to keep track of in your head by the afternoon, let alone compare day 2 or 3 to teams in day 1. It is really handy for trying to compare apples/apples later or after the event.

Sometimes we would regress and we’d have to add back a point that had been drilled earlier in the day. No problem, this is training. Make sure it becomes one of the three, share with the team, and document to check in the next run.

It’s a mindset shift for sure. I had to be ruthless with my team on staying focused and to the point. I also had to watch those “side-bars.” Leaders are going to emulate what they know. For years they have been in the lengthy AARs so they just can’t help themselves. They think they are being helpful by sharing their wisdom. But you have to avoid information overload.

The focused approach worked well for our teams to grow. The team appreciated it that it was focused and to the point. No one wants to stand around for 20 minutes after they just worked their tails off running and gunning…especially if it’s in the middle of the summer. They’re about to pass out, let alone focus on what you’re saying.

Key Takeaways

Long AARs are useless during iterative training. They overwhelm and confuse. Short focused sessions with follow-up significantly improve training quality and the overall training environment.

  • Set expectations with your team ahead of training on how AARs will be ran.
  • Bring the team together to have the long conversation, then vote on the top three sustains/improves. Argue in private…solidarity in public in front of your team.
  • Select who will cover each of the sustains/improves.
  • Write them down on a notecard to give them team. Keep a copy for yourself to annotate progress.
  • Give the focused AAR - keep it to ~5-7 minutes.
  • Police “sidebars” - those who give another AAR at the end. It is counterproductive.
  • Do it again, bringing out notes from previous iterations.