After Action Reviews and Peak OS: Why Organizational Learning Has to Be Built Into the Operating Rhythm

Experience does not automatically make an organization better.

A company can launch ten products and make the same planning mistakes each time.

A leadership team can miss four quarters in a row and develop four different explanations for what happened.

A team can solve a major customer problem without ever asking what it learned from the experience.

A company can survive a difficult period, celebrate getting through it, and then recreate the exact conditions that caused the problem.

Activity creates experience.

Reflection turns experience into learning.

The U.S. Army has spent decades institutionalizing this distinction through the After Action Review, or AAR.

In February 2025, the Army published TC 7-0.1, After Action Reviews, a dedicated training circular describing how leaders should plan, prepare, conduct, and follow up on AARs. The Army describes the AAR as a primary tool for evaluating performance and guiding participants through self-discovery about how to perform better.

The Army's framework is especially interesting when compared with Peak OS because Learning is already one of Peak's five core SCALE behaviors.

Peak OS was developed through more than two decades of working with hundreds of founders, CEOs, leadership teams, and investors. One of the recurring patterns I found was that high-performing teams did more than plan and execute well. They developed the ability to learn from themselves. In Peak Teams, Learning is described as a team-level capability built through repetition, review, reflection, Team Surveys, and recurring operating cadence.

That creates a powerful parallel:

High-performing organizations do not leave learning to memory, personality, or good intentions. They build learning into the way the organization operates.

For military and former-military leaders now building companies—particularly in aerospace, defense, robotics, advanced manufacturing, autonomy, AI, and other frontier technologies—the After Action Review provides another familiar lens for understanding why Peak's operating rhythm works the way it does.

The After Action Review Is Designed to Improve Future Performance

An AAR is not simply a meeting held after something happens.

Current Army guidance describes it as a deliberate process for evaluating task performance, identifying strengths and weaknesses, and determining how future performance can improve. TC 7-0.1 covers both formal and informal AARs, immediate feedback during training, and follow-up actions that can include retraining, revising procedures, and sharing lessons learned.

That last part matters.

The purpose of reflection is not reflection.

The purpose is better future execution.

The Army's AAR agenda returns participants to several fundamental questions. What was supposed to happen? What actually happened? What do the events tell us? What should be sustained, and what needs to improve? The current circular emphasizes reviewing objectives and intent, reconstructing what happened, discussing important issues from multiple perspectives, and identifying performance to sustain or improve.

That creates a learning loop:

Intent → Execution → Observation → Understanding → Change

Peak creates a similar loop across different time horizons.

The team establishes a One-Year Plan and OKRs.

It executes.

Weekly Camp reveals what is On-Course and Off-Course.

Quarterly or Semiannual Sessions create a deeper review of what has happened.

Team Surveys expose how the team experienced execution.

Annual Sessions widen the lens further, reviewing an entire year of wins, misses, behavior, and organizational learning before the next plan is created.

The underlying principle is the same:

The organization should not simply move from one execution cycle into the next. It should carry learning forward with it.

What Was Supposed to Happen?

One reason AARs are effective is that the review starts with intent.

Before debating performance, the team has to reconstruct what it was actually trying to accomplish.

TC 7-0.1 explicitly includes review of objectives, commander's mission and intent, task standards, and the expected performance before turning to what actually occurred.

That sounds obvious.

In companies, it often is not.

Imagine a leadership team reviewing a failed product launch.

Marketing believes the objective was awareness.

Sales believes the objective was pipeline.

Product believes the objective was customer adoption.

Engineering believes success meant shipping the planned functionality on time.

Finance expected a certain revenue contribution.

The CEO believed the launch was primarily strategic and would position the company for the next fundraise.

What exactly failed?

Before the organization can learn from execution, it needs agreement on what execution was intended to produce.

This is one reason Peak connects reflection to the existing planning architecture.

The Mission establishes why the company exists.

The Three-Year Vision establishes longer-term direction.

The One-Year Plan defines nearer-term success.

OKRs define the important outcomes being pursued in the current execution period.

KPIs provide additional measures of business performance.

Because those expectations are visible before execution, the team has something concrete to review afterward.

Without that clarity, retrospection can become storytelling.

Everyone explains what happened through their own perspective.

With clarity, the team can compare reality against a shared expectation.

What Actually Happened?

The next challenge sounds equally simple:

Establish what happened.

Army AAR guidance emphasizes developing a common understanding of events rather than relying on one person's version. The facilitator draws out different perspectives, because no single participant necessarily possesses the complete picture. TC 7-0.1 explicitly states that an AAR is not a critique, that nobody regardless of rank or position has all the information, and that participants should learn from one another.

That is an important organizational-learning principle.

A CEO sees one reality.

The Head of Sales sees another.

Engineering sees another.

The customer-facing team sees another.

The people who performed the work may understand something the executive team never saw.

The board may see the outcome differently again.

This connects directly to the team-of-teams planning principles we have discussed elsewhere, but the direction is reversed.

During planning, information moves through the organization to create a better picture of the future.

During learning, information moves through the organization to create a better picture of the past.

Both require multiple perspectives.

A leadership team that asks, "Why did we miss the quarter?" and then allows the CEO or CFO to provide the answer has not necessarily learned anything.

It has heard one interpretation.

Organizational learning requires enough perspectives to develop a credible shared understanding of what actually occurred.

The Team Survey Creates Another Perspective on Reality

Peak's Team Survey is particularly important here.

Business reviews naturally gravitate toward outcomes:

Did we hit revenue?

Did we launch?

Did we hire?

Did the OKR finish?

Did the KPI hit its target?

Those questions matter.

But performance data does not tell leaders everything about how the organization produced the result.

A company may hit the quarter while destroying trust between teams.

It may launch the product through heroic effort that cannot be repeated.

It may achieve revenue while Sales makes commitments Engineering cannot sustain.

It may complete every leadership-team objective while the rest of the organization is unclear about the strategy.

Those are execution facts too.

Peak's Team Surveys create a structured way for teams to examine how effectively the organization itself is operating. In Peak Teams, Team Surveys are described as one of the primary mechanisms for building a learning team: people look back at where they have been, evaluate where they stand now, and use that information to strengthen future performance.

This gives Peak a particularly useful learning distinction:

We review what happened to the business, and we review what happened to the team.

The first tells us something about performance.

The second tells us something about execution capability.

High-performing organizations need both.

Learning Requires an Environment Where People Can Say What Happened

AARs depend on candor.

The current Army circular explicitly describes the AAR as a dynamic, candid, professional discussion. It says no one should dominate, different observations should be encouraged, and participants should focus on learning rather than assigning a simple grade of success or failure.

That is not a soft cultural preference.

It affects the quality of the information the organization receives.

If people believe that admitting a mistake will harm them, mistakes disappear from the review.

If a junior team member cannot challenge a senior leader's interpretation, relevant information disappears.

If every miss has to be assigned to one guilty person, teams learn to defend themselves rather than examine the system.

If the CEO already knows the answer before the discussion starts, the review becomes confirmation rather than discovery.

A company may still conduct the meeting.

But the learning loop is broken.

Peak's approach to Team Surveys and sessions is intended to create a similar environment of open discussion. The team reviews the survey together rather than having the CEO privately interpret the results and tell everyone what they mean. Different views become part of the conversation.

That distinction is important.

Organizational learning requires truth to move through hierarchy.

Without that, senior leaders become increasingly confident in an increasingly incomplete picture.

A Miss Is More Valuable When the Team Understands Why

Many companies review results primarily as red or green.

Hit.

Miss.

On target.

Off target.

That creates visibility.

It does not automatically create learning.

Suppose an OKR misses.

Why?

The objective was unrealistic.

A key assumption proved false.

A dependency from another function slipped.

The team lacked the necessary capability.

The market changed.

Ownership was unclear.

The plan changed halfway through the quarter.

A decision came too late.

The metric itself was wrong.

A competitor moved unexpectedly.

The organization executed poorly.

All produce the same visible outcome:

Missed OKR.

But the lesson is completely different in each case.

This is why AARs go beyond what happened to explore why it happened and what should change.

Peak's Triage process creates a similar habit during execution.

When something is Off-Course, the objective is not merely to record the fact. The team uses ACT to Assess the situation, Consider alternatives, and Take action.

That means some organizational learning happens before the quarter is over.

The company does not need to wait for a formal retrospective to ask why reality is diverging from the plan.

Weekly Camp detects the variance.

Triage investigates it.

Action changes the next part of execution.

Then the next Quarterly or Semiannual Session allows the team to examine the pattern from a higher altitude.

Learning therefore occurs at multiple speeds.

High-Performing Teams Learn During Execution, Not Only After It

This is one of the most useful parallels between the Army AAR framework and Peak.

AARs are not limited to giant reviews conducted months after an event.

Army guidance distinguishes formal and informal AARs and describes using them during training to provide immediate feedback and allow performance to improve during later iterations. It also describes applying AAR learning in operational settings.

The principle is:

Shorten the distance between experience and learning.

Peak does this through nested cadence.

Weekly Camp creates a short learning loop.

Quarterly or Semiannual Sessions create a medium learning loop.

Annual Sessions create a long learning loop.

The same organization therefore gets multiple opportunities to ask:

What are we seeing?

What is working?

What is not?

Why?

What does that tell us?

What should we change?

In Peak Teams, the Peak cadence is explicitly described as a system of repetition, review, and reflection that reinforces the five core team behaviors over time.

This is a major difference between an annual planning process and an operating system.

Annual planning tells the organization where to go.

An operating system repeatedly asks whether the organization is becoming better at getting there.

Weekly Camp Contains a Micro-Learning Loop

Peak even embeds learning into the smallest recurring meeting.

Weekly Camp ends with the team rating the meeting.

If someone rates it below the expected level, they explain why.

That may appear minor compared with strategy, OKRs, KPIs, and major business decisions.

But it embodies the entire philosophy.

The team does not simply have the meeting.

It evaluates how effectively it had the meeting.

It learns from its own operating behavior and uses that information to improve the next repetition. Peak Teams specifically calls this rating step critical to making Weekly Camp more effective over time.

This creates a small but important loop:

Perform → Reflect → Improve → Repeat

Now imagine that same principle operating across an entire company.

How effective was the planning session?

How well did the OKRs work?

Were the KPIs useful?

Did Weekly Camp create visibility?

Did Triage solve meaningful problems?

Did teams collaborate?

Did ownership remain clear?

Did the company learn?

The system itself becomes something the organization continuously improves.

That is organizational learning at a deeper level.

A Quarterly or Semiannual Session Should Not Begin With a Blank Page

Companies sometimes treat quarterly planning as:

"What should we do next?"

That skips the most valuable question:

"What did the last execution period teach us?"

Peak's cadence deliberately brings the team back to the existing One-Year Plan from a new vantage point.

In Peak Teams, the Quarterly Session reviews the previous period, examines surveys, reviews the One-Year Plan in its entirety, makes course corrections where necessary, and then creates the next set of OKRs.

In organizations running a semiannual cadence, the time interval is different but the principle remains.

The next planning horizon should be informed by the organization's accumulated learning.

This is analogous to the follow-up requirement in current Army AAR guidance. The AAR is not complete when the discussion ends. Follow-up can include retraining, changes to standard operating procedures, and integration or dissemination of lessons learned.

A business review should operate the same way conceptually.

If the team learned that a dependency repeatedly surprises Engineering, something should change.

If a KPI failed to provide useful information, the measurement should change.

If every cross-functional OKR suffered from unclear ownership, the next planning process should change.

If Team Survey results show that the organization understands the strategy but does not understand decision rights, the team should address the gap.

A lesson that does not influence future behavior is merely an observation.

Learning Means Sustaining What Worked Too

There is another subtle part of the AAR philosophy that business teams often miss.

Reviews tend to focus on failure.

What went wrong?

What was late?

What did we miss?

Who dropped the ball?

Army AAR guidance explicitly includes identifying strengths to sustain, not merely deficiencies to fix.

That is essential.

High-performing organizations need to understand why they won, not only why they lost.

A major launch succeeds ahead of schedule.

Why?

A cross-functional team worked unusually well.

Why?

A difficult hire closes quickly.

Why?

A customer implementation that normally takes three months takes six weeks.

Why?

One business unit consistently predicts its KPIs more accurately than everyone else.

Why?

If an organization only investigates failures, it leaves half of its learning on the table.

Peak's review cadence creates room for both.

Annual and Quarterly/Semiannual reviews look at progress, results, successes, misses, and Team Survey feedback. The Annual Session explicitly creates room to celebrate wins and take in lessons before planning forward.

The learning question becomes:

What should we stop?

What should we change?

What should we repeat?

All three matter.

Teams Can Succeed and Still Learn

Current Army guidance makes another important point: an AAR is not simply a pass/fail critique. Even when performance was strong, there can be strengths to sustain and weaknesses to improve.

That is an important mindset for successful companies.

Success can conceal organizational weakness.

The quarter was achieved because the CEO personally rescued three deals.

The launch succeeded because Engineering worked nights for six weeks.

Customer churn stayed low because one exceptional leader managed every difficult account personally.

The financing closed because the founder had existing investor relationships.

The outcome says:

Success.

The execution system may say:

Not repeatable.

This is one reason Peak separates business outcomes from the way the team operates.

A company should not wait for failure before examining whether its system is healthy.

Learning asks whether the organization can reproduce good performance under future conditions.

That is a much more demanding question.

Repeated Learning Creates Organizational Memory

There is an important difference between an individual learning something and the organization learning something.

A VP discovers that a particular customer segment is more difficult to implement.

That is individual knowledge.

If that insight changes the ICP, sales qualification, implementation staffing, and next One-Year Plan, it becomes organizational learning.

An engineer understands why a launch slipped.

Individual learning.

If that insight changes planning assumptions across Product and Engineering, it becomes organizational learning.

A CEO learns that a particular board-reporting approach creates better strategic discussion.

Individual learning.

If the reporting cadence changes and survives beyond the individual, it becomes organizational learning.

The Army's current AAR guidance emphasizes integrating and sharing lessons rather than allowing them to remain isolated in a single review.

Peak creates similar persistence through the One-Year Plan, OKRs, KPIs, Team Surveys, Triage, operating cadence, and documented organizational decisions.

Learning moves into the system.

That is what allows an organization to get smarter rather than simply employ smart individuals.

Team of Teams Creates a Learning Challenge

This becomes harder as organizations scale.

A 20-person company can learn informally.

Someone makes a mistake.

Everyone hears about it.

A process changes.

The learning travels through proximity.

At 200 people, that no longer works.

Engineering learns something Product does not hear.

Customer Success identifies a pattern that never reaches Sales.

One business unit solves a problem another business unit later recreates.

The executive team discovers an execution issue but the lesson never reaches the teams whose behavior actually needs to change.

Now organizational learning becomes a team-of-teams problem.

Peak's nested operating rhythm helps address this.

Teams have their own operating cadence.

Leadership has its cadence.

Information and decisions can move up, down, and across.

Quarterly/Semiannual and Annual reviews provide higher-level opportunities to identify patterns that matter beyond one team.

The principle is similar to the broader purpose of recording and sharing lessons in the Army AAR process: what one group learns can improve performance beyond the original event.

Learning has to travel.

Otherwise organizations simply become collections of teams individually rediscovering the same lessons.

Frontier-Tech Companies Cannot Afford Slow Organizational Learning

This becomes particularly important in frontier technology.

A software company may be able to learn from a mistake and deploy a correction tomorrow.

Physical and mission-critical systems can have much longer learning cycles.

A hardware decision can affect manufacturing months later.

A supplier assumption can affect a program milestone.

A test failure can reveal something important about design, operations, quality, or process.

A customer requirement can expose a hidden dependency across software and hardware.

A manufacturing defect can reveal a planning problem upstream.

A regulatory or program-management issue can change what the company needs to build.

In environments like aerospace, defense, autonomy, advanced manufacturing, robotics, and other mission-critical technologies, mistakes can be expensive and feedback cycles can be long.

That increases the value of extracting as much learning as possible from each execution cycle.

The organization should be asking:

What did this program teach us?

What did this test teach us?

What did this launch teach us?

What did this customer deployment teach us?

What did this miss teach us?

What did this win teach us?

And most importantly:

Where does that learning show up in how we operate next?

That last question separates a learning culture from a learning system.

A Learning Culture Is Not Enough

Many companies say that learning is part of their culture.

People are curious.

Leaders are open-minded.

Teams are encouraged to experiment.

Mistakes are discussed.

All of that is valuable.

But culture alone does not guarantee organizational learning.

In Peak Teams, Learning is described as an active process. Teams have to repeatedly review and reflect; without commitment to that process, learning remains an intention instead of a behavior.

This may be one of the strongest parallels with the military AAR.

The Army does not simply tell units:

"Be a learning organization."

It establishes a repeatable mechanism through which people examine performance.

Peak takes the same broad approach.

Do not simply tell teams to learn.

Give learning a place in the operating rhythm.

Team Surveys.

Weekly meeting ratings.

Triage.

Quarterly or Semiannual review.

Annual review.

Reflection before the next plan.

The result is a system that repeatedly forces the organization to confront what reality is teaching it.

The Learning Loop Should Change the Next Plan

The most important output of an AAR is not a document describing the past.

It is improved future performance.

Army guidance makes follow-up part of the AAR process, including retraining, procedural changes, and integration of lessons learned.

Peak's learning loop ultimately returns to planning.

The team executes the One-Year Plan.

It learns.

The plan is reviewed.

The team makes adjustments where needed.

New OKRs are established.

Execution begins again.

At Annual Planning, a year's worth of organizational learning informs the next Three-Year Vision, One-Year Plan, Roles and Responsibilities, organizational priorities, and execution horizon.

That creates a complete cycle:

Plan → Execute → Observe → Reflect → Learn → Adapt → Replan

And then repeat.

This is why Peak is not simply a planning methodology.

It is an operating system.

Planning and learning are connected.

Learning May Be the Behavior That Makes the Others Durable

Peak's five SCALE behaviors are:

Symbiosis

Communication

Alignment

Learning

Empowerment

Learning occupies a unique place among them.

An organization can become more aligned.

But how does it remain aligned as circumstances change?

It learns.

Teams can build Symbiosis.

But how do they improve collaboration when new dependencies emerge?

They learn.

Communication can become stronger.

How do meetings and information flows continue improving?

The team learns.

People can become empowered.

How do leaders discover when ownership or decision rights no longer fit the organization?

They learn.

Learning is therefore not simply another desirable behavior.

It is part of what allows the other behaviors to evolve with the organization.

Peak's cadence creates the repetition, review, and reflection through which that learning becomes habitual.

That is particularly important for growth companies because the organization itself keeps changing.

The company that worked at 40 people cannot assume the same operating patterns will work at 100.

The team that worked before a major fundraise may need different capabilities after it.

The leadership structure that worked for one product may not work for three.

The operating system has to help the organization learn faster than complexity accumulates.

Different Environments, Similar Learning Principle

The Army's After Action Review was developed for military training and operations.

Peak OS was developed through a very different body of experience working with growth-company leadership teams.

They are not the same process.

A Peak Quarterly Session is not an Army AAR.

A Team Survey is not a military evaluation.

Weekly Camp is not military training doctrine.

But the underlying organizational principle is remarkably similar:

Performance improves when teams systematically compare intent with reality, examine why the difference occurred, hear multiple perspectives, identify what should be sustained or changed, and carry those lessons into the next cycle of execution.

The Army formalized that principle through the AAR.

Peak embeds it throughout the operating rhythm.

That convergence matters.

It suggests that learning is not something high-performing organizations should hope occurs naturally after enough experience.

It should be designed.

Experience Is Only Valuable If the Organization Keeps the Lesson

Over more than two decades of working with leadership teams, I have watched companies encounter many of the same organizational problems.

Misalignment.

Unclear ownership.

Cross-functional friction.

Poor meetings.

Weak metrics.

Unrealistic planning.

Decision bottlenecks.

Execution drift.

The most successful teams are not the teams that never encounter those problems.

They are the teams that become increasingly capable of recognizing them, understanding them, and adjusting the way they operate.

That is why Learning became one of Peak's core behaviors.

Peak Teams describes a learning team as one that continuously reviews and iterates rather than assuming that past success or experience will automatically produce future performance.

The After Action Review offers a powerful military parallel.

What were we trying to accomplish?

What actually happened?

Why?

What should we sustain?

What needs to improve?

What will we do differently next time?

Those are simple questions.

But asked consistently, candidly, and at the right operating cadence, they can produce something much larger:

an organization that becomes better because it has executed before.

That is organizational learning.

And for mission-critical and frontier-tech companies operating in environments where the cost of relearning the same lesson can be enormous, it may become one of the most important execution capabilities they can build.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?