John Boyd’s OODA Loop: What Robert Coram’s *Boyd* and Hundreds of Teams Taught Me About Operating Rhythm

A CEO of one of our Peak Teams once gave me a copy of Robert Coram’s Boyd: The Fighter Pilot Who Changed the Art of War.

He explained that as he read the book, he kept seeing parallels between John Boyd’s thinking and the methodology and philosophy behind Peak OS.

That got my attention.

I had spent more than two decades working with hundreds of founders, CEOs, leadership teams, and growth companies trying to understand a different question: Why do some teams consistently execute at a high level while other equally talented teams struggle?

That work led me to identify five behaviors I repeatedly saw in the strongest teams: Symbiosis, Communication, Alignment, Learning, and Empowerment—SCALE. It also led me to an equally important conclusion: those behaviors cannot simply be understood intellectually. Organizations need systems and recurring habits that continually reinforce them.

When I read Coram’s biography of Boyd, I began seeing what that CEO had seen.

Boyd had arrived at many related ideas through an entirely different environment.

He was studying fighter combat, military strategy, organizational design, uncertainty, competition, adaptation, and the speed at which people and organizations could understand changing conditions and respond to them. Coram’s biography follows Boyd from fighter tactics and Energy-Maneuverability Theory into the broader strategic thinking for which he became famous.

The best-known expression of that thinking is Boyd’s OODA Loop:

Observe. Orient. Decide. Act.

At first glance, it looks like a decision-making framework.

The deeper I went, the more I saw something else.

OODA is a learning system.

And that is where the connection to Peak OS became much more interesting.

The strongest organizations I have worked with do not simply plan better. They repeatedly observe what is actually happening, understand what it means, make decisions, act, learn from the result, and adjust.

Their advantage is not that they are always right.

Their advantage is that they continually get smarter.

That is what a strong operating rhythm is designed to do.

John Boyd’s OODA Loop Is More Than a Four-Step Decision Process

OODA is often presented as four boxes arranged in a circle:

Observe → Orient → Decide → Act → Repeat.

That is useful shorthand, but it can also obscure the power of Boyd’s idea.

Marine Corps command-and-control doctrine specifically cautions that the OODA Loop is a conceptual simplification rather than a complete description of decision-making. The real process contains feedback, interactions, and movement among the stages rather than a perfectly neat sequential progression.

Boyd’s own later representation of OODA similarly contains multiple feedback loops. Action affects future observation. New information can alter orientation before a planned decision is completed. Orientation continuously shapes what people notice, how they interpret what they notice, and which actions appear possible.

That distinction matters enormously for organizations.

A company is not operating in a world where leaders can:

Gather all the information.

Develop a perfect strategy.

Execute it.

Then come back a year later to see whether it worked.

Reality continues moving while the company is executing.

Customers react.

Competitors move.

Employees learn.

Markets change.

Technology changes.

Assumptions prove wrong.

New opportunities emerge.

Metrics reveal something unexpected.

Every action changes the environment the organization will observe next.

The organization is therefore always inside a loop.

The question is whether it has designed that loop intentionally.

The Real Advantage Is the Speed of Learning

Boyd is frequently associated with speed because one objective in conflict is to operate effectively while an opponent struggles to keep up with changing circumstances. Air University describes OODA as a continuous decision process and emphasizes that each action feeds future observation, orientation, decisions, and actions.

But I think applying Boyd to business only as “make decisions faster” misses much of the value.

Fast bad decisions are still bad decisions.

A company can move incredibly quickly in the wrong direction.

I have seen organizations do exactly that.

Teams are moving.

People are shipping.

Meetings are happening.

Decisions are being made.

Everyone appears busy.

But the organization is not learning fast enough to recognize that its assumptions have changed.

The more useful concept is decision velocity.

Decision velocity is not merely how quickly a decision occurs.

It is how efficiently an organization can move through:

Reality → Understanding → Decision → Action → Learning

and then begin the cycle again with better information.

The best teams I have worked with become faster over time because they become better at that entire loop.

They are not merely making faster decisions.

They are becoming faster learners.

Observe: The Organization Needs to See Reality

The first part of OODA is Observe.

For an organization, observation begins with visibility.

What is actually happening?

Are our objectives on course?

Are our metrics moving?

What are customers telling us?

What changed this week?

Where are projects slipping?

Where are teams becoming constrained?

What assumptions are no longer holding?

What risks are appearing?

What opportunities are emerging?

Organizations routinely struggle here because there is an enormous difference between having data and seeing reality.

A company may have dozens of dashboards and still lack organizational visibility.

Sales sees one reality.

Product sees another.

Engineering sees another.

Finance sees another.

The CEO sees pieces of all of them.

Everyone is looking at something true, but no one is looking at enough of the whole.

That is one reason Peak OS connects KPIs, OKRs, team outcomes, issues, and organizational priorities.

The objective is not more reporting.

It is better observation.

A leadership team needs enough visibility to recognize what has meaningfully changed before that change becomes a major execution problem.

Orient: This May Be the Most Important Part of the Loop

Observation alone is insufficient.

Two people can observe exactly the same information and reach completely different conclusions about what it means.

That is orientation.

Air University’s discussion of Boyd notes that he considered orientation the most important part of OODA because it shapes how people observe, decide, and act. Orientation is influenced by previous experience, culture, knowledge, and the mental models through which people interpret reality.

This has enormous implications for organizational execution.

Imagine a company misses its revenue target.

Sales may interpret that as a pipeline problem.

Marketing sees an ideal-customer-profile problem.

Product believes the product is missing a critical capability.

Finance sees a pricing problem.

The CEO believes the market has changed.

They all observed the same result.

They are oriented differently.

The leadership challenge is therefore not merely surfacing information.

It is creating enough shared context that the team can collectively understand what the information means.

That is why alignment comes before execution in Peak OS.

Mission establishes the larger purpose.

A Three-Year Vision establishes where the organization is heading.

The One-Year Plan defines what success should look like closer in.

OKRs identify what must be accomplished or built now.

KPIs provide signals from the business.

Roles clarify who owns what.

When new information arrives, those elements provide context for interpreting it.

The question changes from:

“What happened?”

to:

“What does what happened mean relative to where we are trying to go?”

That is orientation.

And it may be the most underdeveloped capability in many leadership teams.

Decide: Great Teams Know What Requires a Decision

Once the organization has observed and oriented, something still has to happen.

A decision has to be made.

This sounds obvious.

Yet I have spent an extraordinary amount of time inside organizations where everyone is talking about the problem and nobody is actually deciding anything.

The same topic comes back next week.

And the week after that.

Another meeting gets scheduled.

More information gets collected.

Another presentation gets prepared.

Eventually a decision happens because the company runs out of time.

This is one reason Triage became an important part of Peak OS.

Triage creates a structured place for teams to identify the most important issues requiring discussion and move them toward action.

The goal is not simply to communicate.

The goal is to determine what matters enough to require a decision.

In Peak Teams, I describe the ACT process within Triage:

Assess the situation.

Consider alternatives.

Take action.

The value is not the acronym itself. The value is forcing movement from understanding into a decision and then into a defined action with ownership.

Without that transition, organizations can create tremendous amounts of intelligence and very little execution.

Act: Decisions Only Become Learning When Something Happens

This is where Boyd’s loop becomes especially powerful.

You eventually have to act.

Until you act, many of your beliefs remain assumptions.

You think the new pricing strategy will work.

You think customers want the feature.

You think the revised sales motion will improve conversion.

You think the new organizational design will remove a bottleneck.

Then you act.

Reality responds.

Now you know something you did not know before.

Air University describes the action phase as the point at which decisions are carried into the real environment, while the consequences of those actions become inputs to future observation and orientation.

That is why action and learning are inseparable.

An organization that spends too long seeking certainty delays learning.

This does not mean acting recklessly.

It means recognizing that in uncertain environments, action is often part of how knowledge is created.

You decide.

You act.

You observe what happened.

You update your understanding.

Then you decide again.

This Is Exactly Why Peak OS Has an Operating Rhythm

This was the connection that stood out to me most while reading Boyd.

Peak OS is not fundamentally a collection of planning tools.

It is a recurring operating cycle.

The Weekly Camp.

The Quarterly Session.

The Annual Session.

Objectives.

Metrics.

Triage.

Actions.

Team feedback.

Review.

Reflection.

Adaptation.

Each exists within a rhythm because the organization is never finished learning.

In Peak Teams, I describe the importance of repetition, review, and reflection. Teams develop learning as a behavior by repeatedly looking at where they are, what happened, what worked, what did not, and what should change next. The cadence creates the environment in which this learning becomes habitual.

Reading Boyd helped me see that operating rhythm another way.

A high-performing organization’s operating rhythm is its organizational OODA loop.

The company continually observes.

It continually orients.

It continually decides.

It continually acts.

And every action generates new information that begins the next cycle.

Weekly Camp Is a Short Organizational Learning Loop

Consider the Weekly Camp through this lens.

During a week of execution, teams generate new information.

Customers respond.

Metrics change.

Objectives progress or slip.

Problems appear.

Dependencies emerge.

New opportunities surface.

The next Weekly Camp creates a structured opportunity to reconnect around those signals.

The team reviews OKRs.

It reviews KPIs.

Anything meaningfully off course becomes visible.

Relevant changes are shared.

Important issues move into Triage.

The team decides what requires action.

Owners leave with clear next steps.

Then everyone returns to execution.

One week later, the organization has another set of observations.

What happened because of what we decided last week?

Did the KPI move?

Did the solution work?

Did the risk disappear?

Did the assumption prove correct?

What do we know now?

That is a learning loop.

A good Weekly Camp is therefore not a status meeting.

It is a recurring mechanism for updating the organization’s understanding of reality.

Quarterly Sessions Create a Larger OODA Loop

Some learning cannot be seen clearly in seven days.

That is why organizations also need a longer loop.

Every quarter, the team has accumulated approximately 90 days of execution.

Now different questions become possible.

Were our objectives actually the right ones?

What did we accomplish?

Where did we miss?

Why?

What patterns appeared in our KPIs?

Did our assumptions about the business hold?

What has changed in our market?

Are our priorities still correct?

What capabilities do we need to build next?

Does the One-Year Plan still reflect reality?

Then the organization reorients.

It establishes the next set of objectives.

It reallocates focus.

It adjusts plans.

And it acts again.

The quarterly rhythm is not separate from weekly execution.

It is a larger learning loop built around it.

Annual Planning Creates an Even Larger Loop

The same process exists at the annual level.

After a year, the organization has significantly more evidence.

The team can examine its strategy.

Its organizational design.

Its people.

Its roles.

Its metrics.

Its capabilities.

Its market assumptions.

Its Three-Year Vision.

Its definition of success.

Then it makes larger adjustments based on what it has learned.

This is why I have always believed planning and execution should not be treated as separate organizational activities.

Planning creates hypotheses about the future.

Execution tests those hypotheses.

Measurement generates information.

Reflection creates learning.

Learning changes the next plan.

That is one system.

Seen through Boyd’s framework, Peak’s weekly, quarterly, and annual cadences are nested OODA loops operating at different time horizons.

The company is continually learning at multiple levels.

Learning Was One of the Five Behaviors I Kept Finding

This connection was particularly interesting to me because Learning was one of the five behaviors I had already identified from working with hundreds of teams.

I did not begin with Boyd.

I did not begin by trying to create a business version of OODA.

I started by watching teams.

Over years of working with organizations at different stages, I kept seeing the same behaviors in the teams that consistently performed.

Symbiosis.

Communication.

Alignment.

Learning.

Empowerment.

Learning was not simply employee development.

It was the ability of the team to learn from itself.

Great teams reviewed what happened.

They discussed misses.

They reflected on decisions.

They surfaced uncomfortable information.

They adjusted.

They did not repeatedly make the same mistakes because they built mechanisms that converted experience into improved execution.

Eventually those observations became SCALE and part of the foundation of Peak OS.

Reading Boyd gave me another way to understand why Learning had shown up so consistently.

In uncertain environments, learning is not an HR capability.

Learning is an execution capability.

The Other SCALE Behaviors Make the Loop Work

The OODA connection also helped me think differently about the other Peak behaviors.

Alignment improves orientation. People interpret new information through a shared understanding of the mission, direction, priorities, and outcomes.

Communication improves observation. Information has to move between people and teams if the organization is going to see enough of reality.

Symbiosis creates trust. People must believe others will surface accurate information, keep commitments, and work for the larger organization rather than protecting their own functional interests.

Empowerment accelerates decision and action. People closest to the work need enough context and ownership to respond without waiting for every issue to move upward.

Learning closes the loop. Results become inputs into the organization's next observations and decisions.

The behaviors reinforce the system.

The system reinforces the behaviors.

That relationship is fundamental to Peak OS.

The tools themselves are not the destination.

The objective is to build organizational habits so deeply that strong execution becomes how the organization naturally operates.

Decision Velocity Is an Organizational Capability

This is why I increasingly think about decision velocity rather than simply decision speed.

Decision velocity asks:

How quickly can relevant information become visible?

How quickly can the organization understand what that information means?

How quickly can the right people make a decision?

How quickly can someone own the action?

How quickly can the organization see whether the action worked?

How quickly can that learning influence the next decision?

A weakness anywhere in that chain reduces the organization's velocity.

You can have tremendous data and weak orientation.

You can have brilliant analysis and slow decisions.

You can make fast decisions and have weak ownership.

You can execute quickly and never review the outcome.

Every one of those organizations has a slow learning loop.

The strongest teams create flow across the entire cycle.

The CEO Should Improve the Loop, Not Sit in the Middle of It

This has important implications for leadership.

As companies grow, CEOs often become the connection point between observation, orientation, decision, and action.

Information comes to the CEO.

The CEO interprets it.

The CEO makes the decision.

The CEO tells someone what to do.

Then people report the result back to the CEO.

That can work in a small organization.

At scale, it creates a major constraint.

The organization can only learn as quickly as information moves through one person.

The more scalable alternative is to build the loop into the organization.

Make priorities visible.

Create common metrics.

Give teams shared context.

Clarify ownership.

Create a reliable problem-solving process.

Establish decision rights.

Build recurring coordination and learning rhythms.

Then the CEO does not disappear.

The CEO creates the conditions in which other people can observe, orient, decide, and act without continuously waiting for the top.

This is the transition from founder-connected execution to system-connected execution.

Organizational Intelligence Is What the Loop Produces

The connection between Boyd and Peak also helps clarify what I mean by organizational intelligence.

Organizational intelligence is not the amount of information a company possesses.

It is the organization’s ability to create shared understanding from information and turn that understanding into coordinated action and learning.

OODA provides a useful way to see that process.

Observation creates signals.

Orientation creates understanding.

Decision creates direction.

Action creates results.

Results create new information.

The organization becomes smarter when those loops operate effectively.

It becomes less intelligent when information is trapped, orientation is fragmented, decisions stall, actions lack ownership, or results are never meaningfully reviewed.

Organizational intelligence is therefore dynamic.

It is continuously created through execution.

AI Will Make Organizational OODA Loops Even More Important

Artificial intelligence is going to dramatically increase organizations' ability to observe.

Companies will be able to analyze more information, summarize more conversations, identify patterns faster, monitor more metrics, and surface more signals than any leadership team could manually process.

That creates tremendous potential.

It also creates a new problem.

More observation does not automatically create better orientation.

If an organization generates ten times more signals without becoming better at understanding which ones matter, decision-making can actually become harder.

AI can accelerate parts of the loop.

The organization still needs shared direction.

Judgment.

Context.

Ownership.

Decision-making.

Action.

Reflection.

Learning.

The companies that benefit most from AI may therefore be the companies with the strongest organizational learning loops already in place.

Technology can accelerate intelligence.

Operating rhythm turns that intelligence into execution.

What Robert Coram’s Boyd Helped Me See

When that Peak Team CEO handed me Robert Coram’s book, he saw connections that I had not explicitly drawn myself.

I am grateful he did.

I had spent decades arriving at Peak through observation.

Hundreds of teams.

Thousands of leadership conversations.

Successes.

Misses.

Growth.

Conflict.

Alignment.

Execution.

Learning.

Over time, patterns emerged.

The best teams shared certain behaviors.

The best organizations reinforced those behaviors through systems and habits.

Coram’s account of John Boyd gave me a completely different lens through which to examine many of those conclusions.

Boyd came to his ideas through fighter combat, engineering, military history, strategy, and the study of competition under uncertainty.

I came to mine through companies and teams.

Yet both paths lead toward a similar principle:

In a changing environment, the organization that learns and adapts effectively has an enormous advantage.

That is why operating rhythm matters.

It is not simply the schedule on which meetings occur.

It is the rhythm through which an organization observes reality, creates shared understanding, makes decisions, acts, and learns.

Your Operating Rhythm Is Your Organizational OODA Loop

The biggest lesson I took from connecting Boyd’s work to Peak OS is straightforward.

Strategy is not enough.

Planning is not enough.

Data is not enough.

Speed is not enough.

The organization has to repeatedly connect all of them.

Observe reality.

Orient around what it means.

Decide what matters.

Act with clear ownership.

Learn from the result.

Then repeat.

Weekly.

Quarterly.

Annually.

Again and again until it becomes how the organization naturally works.

The strongest teams I have worked with do this extraordinarily well, whether they use Boyd’s language or not.

They see.

They understand.

They decide.

They execute.

They learn.

And then they get better.

That is more than a decision-making loop.

It is an organizational capability.

And it is one of the clearest explanations I have found for why a strong operating rhythm can become such a powerful competitive advantage.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?