Robert Coram’s *Boyd*: Why John Boyd’s Organizational Philosophy Mirrors the Five Behaviors I Found in High-Performing Teams

A CEO of one of our Peak Teams gave me Robert Coram’s Boyd: The Fighter Pilot Who Changed the Art of War because he kept seeing something familiar in the book.

He saw Peak.

Not literally. Peak OS was not derived from John Boyd’s work, and Boyd was not writing about business operating systems.

But this CEO saw parallels between the way Boyd thought about people, organizations, trust, direction, adaptability, initiative, and execution—and what his own team had been practicing through Peak.

That made me curious.

I had spent more than two decades working with hundreds of founders, CEOs, leadership teams, and investors trying to answer a question that had fascinated me since early in my career:

Why do some teams consistently perform at an extraordinary level while other teams with equally talented people struggle?

I did not begin with a management theory and look for evidence to support it.

I began with teams.

I watched them operate.

I watched what happened when they succeeded, when they failed, when they grew, when they became misaligned, when leadership changed, when capital arrived, when strategies changed, and when pressure exposed weaknesses that had previously been invisible.

Eventually patterns became difficult to ignore.

Across hundreds of teams, I repeatedly found five behaviors in the strongest ones: Symbiosis, Communication, Alignment, Learning, and Empowerment.

Those became SCALE and one of the foundations of Peak OS.

Then I read Boyd.

Coram’s biography follows John Boyd from fighter aviation and Energy-Maneuverability Theory into a much broader body of thinking about conflict, organizations, adaptation, and decision-making. Boyd eventually developed ideas that extended far beyond air combat, including the OODA Loop and his briefings on organizational design and command.

The more I read Boyd’s later thinking, the more I understood why that Peak CEO had handed me the book.

Boyd had arrived through the study of conflict at many principles I had arrived at through the study of teams.

The terminology was different.

The environment was radically different.

But the underlying human dynamics were remarkably familiar.

Boyd Was Ultimately Studying How Groups Perform Under Complexity

Boyd is best known for the OODA Loop: Observe, Orient, Decide, Act.

But limiting Boyd to OODA misses a great deal of his organizational thinking.

His Organic Design for Command and Control briefing asks what organizations require to cope with uncertain and continually changing environments. Boyd emphasized several conditions: insight and vision, focus and direction, adaptability, and the development of implicit communication and trust. He argued that focus and direction are necessary for both harmony of effort and individual initiative, and that shared experiences can build the implicit bonds that allow a group to coordinate with less friction.

That caught my attention.

Because when I stripped away the military terminology, I recognized the same tension I had seen inside hundreds of companies.

High-performing organizations need people moving together.

But they also need people capable of acting independently.

They need structure.

But not so much structure that the organization becomes slow.

They need communication.

But not endless communication.

They need leadership direction.

But not leadership intervention in every decision.

They need consistency.

But they also need adaptability.

This is the same paradox Peak OS is designed to solve.

How do you create enough shared direction and connection that people can execute with more autonomy rather than less?

The Five Behaviors Were Found in the Work, Not Invented in a Conference Room

This distinction matters to me.

I did not create SCALE because five words sounded good together.

The five behaviors emerged through years of working with teams.

In Peak Teams, I describe how the strongest teams I worked with repeatedly demonstrated Alignment, Symbiosis, Communication, Empowerment, and Learning. I later organized those behaviors under the SCALE acronym: Symbiosis, Communication, Alignment, Learning, Empowerment.

Each behavior addressed something I had repeatedly seen break inside companies.

Teams failed without alignment because people worked hard in different directions.

They struggled without symbiosis because trust deteriorated and silos emerged.

They slowed without communication because issues remained unresolved and important information failed to move.

They became CEO-dependent without empowerment because people did not understand what they owned.

They stagnated without learning because the organization repeatedly experienced events without converting those experiences into better future behavior.

Reading Boyd later gave me a new perspective on why those same five behaviors may be so fundamental.

He was wrestling with many of the same organizational requirements from an entirely different direction.

Symbiosis: Boyd’s Trust and Implicit Bonds

The first SCALE behavior is Symbiosis.

In Peak, Symbiosis describes a team operating with trust, respect, unity, and interdependence.

People understand that their success is connected to the success of others.

They trust teammates to execute their responsibilities.

They do not think only in terms of optimizing their individual function.

They operate for the success of the whole.

In Peak Teams, I describe Symbiosis as an environment where everyone is trusted to execute their unique role and achieve agreed-upon results while believing their teammates will do the same.

Boyd’s organizational thinking places enormous importance on a similar connective force.

In Organic Design, he argues that people exposed to varied situations together can develop bonds of implicit communication and trust. Those connections help create harmony and direction while reducing the friction that would otherwise slow a group. Boyd goes further: without these implicit bonds, a collective entity struggles to maintain both harmony and individual initiative under changing conditions.

That is very close to what I have observed inside companies.

Trust is not organizational decoration.

It is execution infrastructure.

When trust is high, people do not need to verify every commitment.

Teams do not build defensive processes around one another.

Information moves more freely.

People ask for help earlier.

Problems can be discussed without immediately becoming political.

Individuals can operate with greater autonomy because they trust the surrounding organization.

Without that connective tissue, organizations become collections of individuals protecting their own positions.

That is why I called this behavior Symbiosis.

The people do not merely coexist.

Their performance becomes interconnected.

Communication: The Goal Is Not More Communication

This was another Boyd connection I found especially interesting.

Most organizations respond to communication problems by adding communication.

Another meeting.

Another update.

Another report.

Another dashboard.

Another Slack channel.

Another coordination layer.

Boyd was skeptical of the instinct to solve organizational complexity simply by increasing explicit information systems and formal control. His Organic Design work emphasizes the value of implicit communication developed through shared experience because it can reduce friction, compress time, and support initiative.

That does not mean people should communicate less thoughtfully.

It means the goal of organizational communication should not be maximum communication.

It should be effective shared understanding.

I have seen this repeatedly.

A new team often needs more explicit conversation because people do not yet understand how one another thinks.

They need to clarify priorities.

They need to discuss roles.

They need to understand the strategy.

They need to solve disagreements.

But over time, high-performing teams develop a shared language.

A phrase means something to everyone.

A metric carries context.

People know what “off course” means.

They understand who owns a decision.

They know where issues should go.

They anticipate how another functional leader will think about a problem.

This is one reason consistent operating habits matter.

The Weekly Camp is communication.

Triage is communication.

Planning is communication.

Reviewing outcomes is communication.

But the deeper value is what repeated use of those habits creates between meetings.

The organization becomes easier to understand.

People spend less time explaining how the organization works because the system itself has become familiar.

In Peak Teams, I describe communication as what brings teams together and keeps them together. Strong communication creates clarity around objectives, roles, responsibilities, and commitments so that things actually get done.

The goal is not to talk more.

The goal is to create enough shared understanding that the team can operate with less friction.

That feels very Boyd.

Alignment: Boyd’s Focus and Direction

The strongest parallel may be Alignment.

Boyd’s Organic Design briefing argues that focus and direction are necessary because without them there can be neither harmony of effort nor meaningful individual initiative.

That might initially sound contradictory.

Wouldn’t more direction reduce initiative?

In my experience, the opposite is often true.

People are able to exercise more initiative when they understand the larger direction.

That is one of the foundational ideas behind Peak Alignment.

I describe alignment as agreement around six questions:

Why are we doing this?

Where are we going?

When do we intend to get there?

What do we need to accomplish?

How will we do it?

Who are we, and who needs to own what?

When people understand those answers, the organization does not need to prescribe every smaller decision. Shared direction guides the hundreds of micro-decisions people make every day.

This is the paradox:

Clearer direction can create greater autonomy.

Without alignment, autonomy produces fragmentation.

Sales goes one way.

Product goes another.

Engineering optimizes another priority.

Marketing builds around another assumption.

Everyone is empowered.

And the company goes nowhere.

With alignment, people can move independently while still moving toward the same outcome.

That is why Peak connects the Mission, Three-Year Vision, One-Year Plan, company priorities, team outcomes, OKRs, and KPIs.

Not because companies need more planning documents.

Because people need enough shared orientation to act without continuously asking leadership what to do.

Boyd called for focus and direction.

Peak operationalizes that requirement as Alignment.

Learning: Boyd’s Adaptability

Boyd viewed adaptability as fundamental to operating in uncertain and changing environments. In Organic Design, he explicitly connects adaptability with the ability to cope with changing circumstances and argues for organizational arrangements that allow people to continue interacting with the external world rather than becoming trapped inside increasingly rigid internal systems.

This connects directly to Learning, the fourth SCALE behavior.

One of the patterns I saw across hundreds of teams was that the best teams learned from themselves.

They did not merely experience something.

They reflected on it.

What worked?

What did not?

What assumption was wrong?

Why did we miss the target?

What did the customer teach us?

What changed?

What should we do differently next time?

That sounds simple.

It is surprisingly uncommon.

Organizations often move from quarter to quarter so quickly that there is almost no time devoted to converting experience into organizational knowledge.

A target is missed.

Everyone moves on.

A project succeeds.

Nobody determines why.

A decision turns out badly.

The organization quietly changes direction without identifying the flawed assumption.

Then six months later, a similar problem appears.

This is why Peak builds learning into cadence.

Team Surveys.

Weekly reviews.

Quarterly reflection.

Annual reflection.

Metrics.

OKRs.

Meeting ratings.

Triage.

All create opportunities for the organization to compare intention with reality and improve how it operates.

Peak Teams learn through repetition, review, and reflection. The recurring cadence makes adaptation a habit rather than something reserved for a crisis.

Boyd approached the same necessity through uncertainty and conflict.

Reality keeps changing.

Therefore your understanding must keep changing.

A system that cannot learn eventually becomes a system optimized for a world that no longer exists.

Empowerment: Boyd’s Initiative at Every Level

The fifth SCALE behavior is Empowerment.

Boyd's organizational model repeatedly returns to initiative.

He wanted organizations capable of maintaining broad harmony while allowing people throughout the system to act quickly. His argument was not that leaders should disappear. It was that an organization with strong shared orientation and trust could reduce the friction of excessive explicit control and exploit initiative throughout the system.

That is remarkably consistent with what I learned from CEOs.

Almost every CEO wants an empowered leadership team.

Yet many unintentionally build organizations where meaningful decisions still require CEO involvement.

People are unsure what they own.

Roles overlap.

Priorities are unclear.

The strategic context lives in the CEO’s head.

A leader makes an independent decision, the CEO overrides it, and soon everyone learns to wait.

Then the CEO says:

“Why won't anyone take ownership?”

In Peak OS, empowerment starts with clarity.

What is your role?

What are you responsible for?

What outcome do you own?

How will success be measured?

What does another person own?

Where are the boundaries?

What decisions can you make?

What context do you need?

In Peak Teams, I describe empowerment as giving people the clarity and autonomy required to make decisions and act without constantly seeking approval from leadership.

Again we return to the same paradox.

More autonomy does not require less structure.

It requires the right structure.

Direction.

Context.

Ownership.

Trust.

Then freedom to execute.

That is what turns initiative into coordinated execution rather than chaos.

The Five Behaviors Work as a System

The deeper connection between Boyd and Peak is not any single behavior.

It is how the behaviors reinforce one another.

Symbiosis creates trust.

Communication creates shared understanding.

Alignment creates direction.

Learning creates adaptability.

Empowerment creates initiative.

Take one away and the others become weaker.

Empowerment without Alignment can produce teams moving quickly in conflicting directions.

Alignment without Empowerment creates people who understand the strategy but still wait for permission.

Communication without Symbiosis can become defensive, political, or superficial.

Learning without Communication traps insight inside individuals and functions.

Symbiosis without accountability can create a team that likes one another but does not execute.

This is why I came to see the five behaviors as a system.

In Peak Teams, I describe them as deal-breaker behaviors: each has to be intentionally built and reinforced. The Peak methodology then uses habits and recurring operating practices to turn those desired behaviors into something a team repeatedly practices.

That is one of the strongest connections I see with Boyd.

He was not describing isolated management techniques either.

He was thinking systemically.

Peak OS Was Not Built From Boyd—and That Is What Makes the Parallels Interesting

I want to be precise about this.

I did not read Boyd and turn his philosophy into Peak OS.

The sequence ran in the opposite direction.

I spent years working with companies.

I saw behaviors that consistently differentiated stronger teams.

I tested approaches.

I learned from CEOs.

I learned from investors.

I watched teams improve.

I watched them drift.

I saw how systems created habits and how habits created behavior.

Those lessons eventually became Peak OS and Peak Teams.

Then a CEO using Peak handed me Coram's Boyd and said, essentially:

You need to read this. There is something here.

That is why the similarities are meaningful to me.

Boyd was studying what allows organizations to remain coherent, adaptive, and capable of initiative under intense complexity.

I was studying what allowed companies and leadership teams to remain aligned, healthy, accountable, adaptable, and capable of executing as they scaled.

Two very different environments.

Many of the same human requirements.

Habits Are How Philosophy Becomes Performance

There is another important difference between understanding these concepts and actually experiencing them.

Leaders generally agree that trust is good.

Communication is good.

Alignment is good.

Learning is good.

Empowerment is good.

The problem is not intellectual agreement.

The problem is operationalization.

How does a company become more aligned on Monday morning?

How does trust get stronger quarter after quarter?

How does communication improve without filling everyone's calendar?

How does the organization systematically learn?

How does empowerment become more than a leadership slogan?

My answer became habits.

Peak OS connects the behaviors to repeatable operating practices.

Alignment is reinforced through Mission, Three-Year Vision, One-Year Plan, and connected outcomes.

Symbiosis grows through shared planning, commitments, transparency, and cross-functional work.

Communication is reinforced through structured Weekly Camps and Triage.

Empowerment becomes concrete through Roles and Responsibilities, ownership, clear outcomes, and decision clarity.

Learning is reinforced through metrics, surveys, reviews, quarterly reflection, and consistent cadence.

Over time, the practices create predictable behavior.

In Peak Teams, I describe Peak as a system designed to reinforce these fundamentals until they become increasingly instinctive—the organization's way of working rather than an additional layer of work.

The methodology is useful only if the behaviors eventually live beyond the methodology.

The Best Operating System Creates Harmony and Initiative

One of Boyd's most interesting organizational tensions is the need to combine harmony with initiative.

That is exactly what I believe a modern organizational operating system should accomplish.

It should not make everyone do the same thing.

It should not centralize every decision.

It should not turn talented people into process followers.

It should not add management overhead simply because someone decided more process equals more control.

It should create enough common understanding that different people can act intelligently without continually coordinating every action.

That means:

People understand the destination.

They understand what matters now.

They know what they own.

They understand how their work connects to others.

They have visibility into relevant performance.

They know how to surface problems.

They have a rhythm for reconnecting with the organization.

And inside those boundaries, they have room to operate.

That is aligned autonomy.

It may be one of the most important capabilities a growing organization can build.

Complexity Makes These Behaviors More Important

These ideas become more important as organizations scale.

At ten people, a founder can personally connect much of the organization.

At greater scale, functions form.

Expertise deepens.

Information becomes distributed.

Cross-functional dependencies multiply.

Decisions increase.

The organization cannot solve that complexity simply by adding more control.

Too much control slows decision-making and pushes more responsibility upward.

Too little coordination creates fragmentation.

The answer is stronger organizational capability.

Trust.

Shared direction.

Communication.

Learning.

Empowered ownership.

In other words, the same behaviors.

AI Will Increase the Value of These Human Behaviors

These parallels also matter because organizations are entering another period of rapidly increasing capability.

Artificial intelligence will enable individuals and teams to move faster.

People will generate more work.

Analyze more data.

Explore more options.

Automate more processes.

Make more decisions.

That does not reduce the importance of organizational behavior.

It increases it.

If every team becomes more capable while Alignment remains weak, organizational drift accelerates.

If AI produces more information while Communication remains weak, fragmentation increases.

If teams gain more autonomy without Symbiosis, functions can optimize against one another faster.

If organizations accelerate output without Learning, they can repeatedly make mistakes at greater speed.

If leaders centralize every AI-enabled decision rather than building Empowerment, the CEO becomes an even larger bottleneck.

The more capable the organization becomes technologically, the more important its human operating fundamentals become.

Boyd's concern with adaptability, orientation, trust, initiative, and friction feels remarkably current.

What Boyd Helped Me See About Peak

Sometimes another framework gives you a new way to understand your own work.

That is what Robert Coram's Boyd did for me.

I already knew the five SCALE behaviors because I had seen them repeatedly in teams.

But Boyd gave me another lens.

Symbiosis is not simply about having a healthy culture.

Trust reduces organizational friction.

Communication is not about maximizing information.

Shared understanding reduces the need for endless explicit coordination.

Alignment is not restrictive.

Clear direction makes meaningful initiative possible.

Learning is not a soft capability.

Adaptability determines whether the organization can keep up with changing reality.

Empowerment is not giving up leadership control.

It is creating the context and trust through which initiative can exist throughout the organization.

These are not separate team-development ideas.

They are an architecture for execution.

Two Different Paths Toward the Same Human Fundamentals

John Boyd spent his career studying performance in environments where uncertainty, speed, friction, adaptation, and decision-making could determine outcomes.

I spent my career working with founders and leadership teams where the consequences were obviously different, but where uncertainty, speed, friction, adaptation, and decision-making were present every day.

Boyd's path led him toward ideas about trust, implicit communication, focus and direction, adaptability, and initiative.

My path led me toward Symbiosis, Communication, Alignment, Learning, and Empowerment.

I do not think those similarities are accidental.

They point toward something deeper about how humans operate together under complexity.

High-performing organizations need enough trust to stay connected.

Enough communication to understand one another.

Enough alignment to move in the same direction.

Enough learning to adapt.

And enough empowerment to act.

Those are the behaviors I saw repeatedly across hundreds of successful teams.

And after reading Coram’s Boyd, I understood why one of our CEOs saw John Boyd in Peak OS before I did.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?