Why Technical Excellence Is Not Enough: What Aviation Crew Resource Management and Peak OS Reveal About High-Consequence Teams

A company can hire exceptional people and still have a team problem.

The engineer is exceptional.

The product leader is exceptional.

The program leader is exceptional.

The operations leader is exceptional.

The CEO has deep experience.

Everyone knows their discipline.

Yet when circumstances become uncertain, information does not move quickly enough. A junior expert sees something but hesitates to challenge a more senior leader. Two functions interpret the same situation differently. Everyone assumes someone else is monitoring an important dependency. The team has plenty of data but not enough shared understanding. A decision that should have happened close to the work escalates unnecessarily.

Then the organization discovers an uncomfortable truth:

Technical competence inside individual roles does not guarantee effective performance as a team.

Commercial aviation learned this lesson decades ago.

The modern concept of Crew Resource Management, or CRM, traces its U.S. origins to a 1979 NASA-sponsored workshop on resource management on the flight deck. NASA's research into aviation accidents had identified failures in interpersonal communication, decision-making, and leadership as important contributors to accidents attributed broadly to human error. The resulting approach was initially called Cockpit Resource Management and later evolved into Crew Resource Management as its scope expanded beyond pilots to include flight attendants, dispatchers, maintenance personnel, air traffic controllers, and others involved in safe flight operations.

The FAA defines CRM broadly as the effective use of available people, hardware, and information. Its guidance emphasizes situation awareness, communication, teamwork, workload and task allocation, decision-making, problem-solving, monitoring, and coordination.

That history makes CRM particularly relevant to the TeamSTEPPS article that preceded this one.

TeamSTEPPS inherited important ideas from military, aviation, human-factors, and medical-team research. CRM is one of the major upstream bodies of practice that helped establish a broader lesson now visible across high-consequence domains:

When technically capable people must work together under uncertainty, the quality of the relationships, information flows, decision behaviors, and team habits between them can be as consequential as their individual expertise.

Peak OS was developed independently through more than two decades of work with hundreds of founders, CEOs, investors, and leadership teams. But I encountered a remarkably similar organizational problem.

Growth companies rarely lack smart people.

They struggle when those smart people cannot reliably combine their expertise into coordinated execution.

That is why Peak's SCALE behaviors include Symbiosis, Communication, Alignment, Learning, and Empowerment—and why Peak reinforces them through a repeatable operating system rather than assuming talented leaders will naturally coordinate well.

CRM Started With a Human-Factors Problem, Not a Flying Problem

The origins of CRM are important because the original problem was not that pilots lacked technical proficiency.

FAA guidance describes aviation investigations in which many significant problems had relatively little to do with the technical mechanics of operating the aircraft. Instead, recurring issues included poor group decision-making, ineffective communication, inadequate leadership, and poor task or resource management. Traditional pilot training had historically focused heavily on individual technical performance and not enough on crew coordination.

That distinction should sound familiar to CEOs.

A company hires a strong CTO.

A strong CRO.

A strong CFO.

A strong Product leader.

Everyone has previously succeeded.

Leadership assumes that bringing strong people together will create a strong leadership team.

But individual executive proficiency is different from collective executive performance.

The CTO may be exceptional at building Engineering organizations.

That does not automatically mean the CTO knows how to coordinate Engineering priorities with a capital plan, customer commitments, Product sequencing, recruiting constraints, and Manufacturing dependencies.

The CRO may be exceptional at revenue.

That does not automatically mean every commercial commitment works for the broader system.

The CFO may be an exceptional financial leader.

That does not mean the financial optimum is always the organizational optimum.

The CEO may be brilliant.

That does not mean every important decision should eventually return to the CEO.

The team needs another set of capabilities.

Communication.

Shared context.

Decision discipline.

Cross-checking.

Constructive challenge.

Understanding roles.

Knowing when to lead and when to follow expertise elsewhere.

That is the territory CRM was built to address in aviation.

It is also central to organizational execution.

Technical Proficiency and Team Proficiency Are Different Capabilities

FAA CRM guidance makes this point unusually clearly.

A high level of technical proficiency is essential. CRM cannot compensate for inadequate technical competence.

But the reverse is also true: high technical proficiency does not guarantee safe and effective operations when crew coordination is poor. The FAA therefore recommends training people as functioning crews rather than merely as collections of individually competent specialists.

This is a powerful lens for a scaling company.

The question is not only:

Do we have strong executives?

It is:

Does this executive team know how to operate together?

Those are different questions.

Peak's five SCALE behaviors grew out of seeing this repeatedly across companies.

A leadership team needs Alignment so everyone understands why, where, what, how, and who.

It needs Symbiosis so highly specialized leaders can trust one another and optimize for the company rather than only their functions.

It needs Communication so relevant information moves.

It needs Empowerment so decisions do not continually bottleneck at the CEO.

And it needs Learning because the way the team operates has to continually improve as the company changes.

The implication is significant:

Hiring better individuals will not necessarily solve a system problem between individuals.

How Do Mission-Critical Teams Make Decisions Under Pressure?

This is one of the buyer questions CRM helps illuminate.

Pressure changes team behavior.

Time becomes scarce.

Information may be incomplete or contradictory.

Workload increases.

Attention narrows.

The consequences of communication failure increase.

FAA CRM guidance therefore includes explicit training around communication and decision behavior, seeking and evaluating information, cognitive bias, conflict resolution, and decision-making when information is incomplete or contradictory.

The relevant business problem is not identical, but it is real.

A major customer calls with an urgent requirement.

An aerospace test fails.

A production issue threatens delivery.

Revenue suddenly falls behind plan.

A key executive leaves.

A major program milestone slips.

Capital markets move unexpectedly.

A cybersecurity event emerges.

Under pressure, poorly designed organizations tend to centralize.

Everyone calls the CEO.

The CEO begins issuing instructions.

Functions stop communicating laterally because they are waiting for direction.

The team feels decisive because activity increases.

But the organization's full expertise may actually be contributing less to the decision.

A stronger operating system should help preserve access to distributed expertise when pressure rises.

Peak does this through clarity before the crisis.

The organization knows its Mission.

It has a One-Year Plan.

It has current OKRs.

Roles and Responsibilities establish ownership.

Weekly Camp creates recurring shared visibility.

Triage creates a known mechanism when an issue requires collective judgment.

The team does not have to invent its decision architecture after the problem appears.

Hierarchy Can Become an Information Barrier

One of CRM's most important contributions was its willingness to address authority and rank as potential communication barriers.

FAA guidance explicitly includes rank and organizational culture among factors that can interfere with communication. It also recommends teaching appropriate inquiry, advocacy, and assertion—giving crew members the ability to advocate for the course of action they believe is best even when doing so creates disagreement.

This is not about eliminating authority.

CRM guidance simultaneously emphasizes effective leadership, followership, and a balance between respecting authority and practicing appropriate assertiveness.

That balance is extremely relevant to executive teams.

A CEO says:

"I think we should launch in June."

The Head of Engineering believes June is unrealistic.

What happens next?

In a weak system, one of two things occurs.

The engineer quietly accepts the CEO's date despite believing it will fail.

Or the team enters an unstructured battle over who has authority.

Neither is healthy.

The stronger behavior is:

Challenge the assumption clearly. Make the relevant expertise visible. Understand the tradeoffs. Make the decision at the appropriate level. Then commit.

Peak's Communication behavior includes creating an environment in which people can speak and be heard, disagree, and still commit after a decision is made.

That is not consensus.

It is disciplined challenge followed by coordinated execution.

Strong CEOs Need People Who Can Challenge Them

This becomes particularly important in founder-led companies.

Founders often possess deep conviction.

That is one reason the company exists.

They know the market.

They may understand the product better than anyone.

They have usually taken risks other people would not.

Those characteristics are strengths.

But the organization changes as it gains specialized expertise.

The CEO hires people specifically because they know more about their domains.

Now leadership has to create an environment in which that expertise can meaningfully influence decisions.

FAA CRM implementation guidance says organizations should support a culture in which appropriate questioning is encouraged and people understand that there should not be negative repercussions simply for appropriately questioning another crew member's decision or action.

For a company, the lesson is not to copy aviation language.

The organizational principle is:

If leadership hires expertise but creates conditions in which expertise cannot challenge authority, the company has paid for knowledge it cannot fully use.

That is an Organizational Intelligence problem.

The information exists.

The system prevents it from improving the decision.

Empowerment Requires More Than Telling People to Speak Up

There is another side to this.

Leaders sometimes tell teams:

"Speak up."

"Take ownership."

"Challenge me."

"Be more empowered."

Then nothing changes.

Why?

Because empowerment requires structure.

Does the person know what they own?

Do other people know what they own?

Does the team know when the CEO retains the decision?

Does the individual have enough context to understand the larger plan?

Is there a known place for a cross-functional disagreement?

Will the issue be resolved, or simply discussed?

Peak's Roles and Responsibilities create clearer boundaries around ownership.

The Three-Year Vision, One-Year Plan, OKRs, and KPIs give people context.

Weekly Camp creates shared awareness.

Triage creates somewhere for issues requiring broader judgment to go.

That makes Empowerment more than a cultural statement.

It becomes part of the operating architecture.

People can challenge intelligently because they understand the system in which the decision sits.

Cross-Checking Is an Organizational Capability

FAA CRM guidance also emphasizes monitoring and cross-checking.

The FAA describes active monitoring by crew members as a critical line of defense because one person may detect an error or unsafe condition that another has missed.

This has a strong business parallel.

Cross-checking does not need to mean second-guessing everyone's work.

It means important outcomes have enough visibility that the organization is not dependent on one person noticing every problem.

A Head of Sales sees revenue.

Finance also sees the implications for cash.

Product sees customer demand.

Engineering sees technical feasibility.

Program Management sees the effect on delivery.

Leadership sees the connection to the One-Year Plan.

Each perspective can cross-check a different assumption.

This is one reason shared visibility matters.

If only the owner can see an objective, nobody else can recognize a dependency or inconsistency.

If everything is visible but nobody knows what matters, the opposite problem appears: information overload.

Peak tries to create a focused shared picture.

What are the company outcomes?

What is On-Course?

What is Off-Course?

What metrics matter?

Who owns them?

What requires discussion?

Where is another team affected?

That shared picture allows cross-checking without turning the organization into micromanagement.

Monitoring Is Not Micromanagement

This distinction deserves attention.

Monitoring can sound controlling.

But aviation CRM separates monitoring from doing another person's job.

A crew member can retain clear responsibilities while other members remain aware enough to notice when something relevant is changing.

The same principle can help companies.

Engineering owns Engineering.

But Product needs enough visibility to understand when a critical engineering dependency changes.

Finance owns Finance.

But the leadership team needs enough visibility to understand whether runway still supports the plan.

Sales owns Sales.

But Product and Operations may need visibility into commitments with material consequences elsewhere.

The purpose is not:

Everyone manages everyone.

It is:

People have enough shared context to identify when one part of the system may affect another.

Peak's Symbiosis behavior is built around exactly this interdependence. Teams maintain specialized ownership while understanding that their results contribute to the larger organizational system.

Situation Awareness Is More Than Having Data

Situation awareness is another core CRM concept.

FAA guidance describes it in terms of maintaining awareness of the operational environment, remaining vigilant, planning ahead, managing time and workload, prioritizing tasks, avoiding distractions, asking for new information, and anticipating contingencies.

This is closely related to Organizational Visibility, but not identical.

A dashboard can display data.

Situation awareness involves interpretation.

The company knows revenue is at $12 million.

What does that mean relative to the plan?

The organization knows Engineering is four weeks behind.

Which other outcomes does that affect?

The company knows a hiring plan is behind.

Which capability is at risk?

The team knows customer demand is stronger than expected.

Is that merely good news, or does it create a delivery constraint elsewhere?

Data becomes valuable when the organization can interpret it in context.

Peak's One-Year Plan, OKRs, KPIs, Weekly Camp, and Triage create that context.

A KPI is not reviewed because the number itself deserves attention.

It is reviewed because it tells the organization something about execution.

An Off-Course OKR is not a red badge.

It is a signal that reality may be diverging from the intended outcome.

The operating rhythm turns information into shared awareness.

Workload Management Is Also a Team Problem

CRM guidance goes beyond communication and decision-making into workload management.

FAA material emphasizes proper task allocation, recognizing overload in oneself and others, prioritizing during high workload, and preventing nonessential activity from distracting attention from critical work.

That applies remarkably well to scaling companies.

Organizations tend to treat workload as an individual-management issue.

Does this person have too much work?

But some overload is created at the organizational level.

The company has too many priorities.

Every initiative is "top priority."

Three different functions assume the same person has capacity.

The CEO introduces another initiative without removing one.

Cross-functional meetings consume execution time.

A key role remains vacant, so several people absorb parts of it.

One executive becomes the default decision-maker for too many issues.

Peak's planning process forces teams to prioritize.

OKRs narrow the organization's attention.

Roles and Responsibilities clarify who owns what.

Talent Mapping connects future plans with the capabilities the team actually needs.

Weekly Camp can reveal where execution repeatedly becomes Off-Course.

These mechanisms help leadership see workload not merely as:

Is everyone busy?

but:

Does the organization have the capacity and focus required for the commitments it has made?

How Do You Give Executives Autonomy and Still Hold Them Accountable?

This buyer question sits at the center of CRM's leadership/followership balance.

Too little authority creates hesitation.

Too much disconnected autonomy creates fragmentation.

FAA CRM guidance combines clear leadership with active participation from the rest of the crew. Effective crew behavior includes respecting authority while maintaining enough assertiveness, inquiry, and shared situation awareness for the team to function effectively.

The business version is:

clear ownership inside shared context.

Peak gives the executive ownership through Roles and Responsibilities.

The Mission, Vision, and One-Year Plan create strategic context.

OKRs establish current outcomes.

KPIs create visibility.

Weekly Camp maintains shared understanding.

Then the executive can run.

Accountability does not require the CEO to prescribe the method.

It requires clarity around the expected outcome, ownership, relevant constraints, and visibility into whether execution remains On-Course.

That is much closer to Empowerment than micromanagement.

Communication Needs a Standard Under Pressure

Another interesting lesson from CRM is the emphasis on clear and unambiguous communication.

FAA guidance treats communication as a trainable operational capability, not merely a personality trait. It addresses speaking, listening, conflict resolution, briefings, advocacy, assertion, and the effects of rank and culture on communication quality.

Companies often assume experienced executives already know how to communicate.

Individually, they probably do.

But team communication requires shared behaviors.

When someone says an objective is "Off-Course," does the team know what that means?

When something needs a decision, is there a known place for it?

When a team makes a decision, is ownership clear?

When a functional dependency changes, how does another team learn about it?

What information is an update?

What belongs in Triage?

Peak's operating language helps standardize these interfaces.

It does not script every conversation.

It makes important organizational conversations more predictable.

That becomes especially valuable under pressure because the team does not need to invent a communication pattern when time is already scarce.

Triage Turns Disagreement Into a Decision Process

CRM guidance explicitly addresses conflict resolution and the need to maintain communication when crew members interpret information differently or advocate different actions.

Cross-functional leadership teams live in this reality.

Sales and Engineering can look at the same customer request and reach different conclusions.

Finance and Growth can see a hiring decision differently.

Product and Manufacturing can interpret acceptable scope differently.

Disagreement is not evidence that the team is dysfunctional.

It may be evidence that the organization contains valuable specialized perspectives.

The question is whether the team has a way to convert disagreement into action.

Peak uses Triage.

Assess the situation.

Consider alternatives.

Take action.

The purpose is not to eliminate conflict.

It is to process conflict productively enough that the organization can make a decision and continue executing.

That is a major difference between healthy disagreement and organizational friction.

Great Team Behavior Has to Be Practiced Before the Pressure Arrives

This may be the most important CRM parallel of all.

FAA guidance argues that effective team behaviors need recurrent practice and reinforcement. CRM is not intended as a one-time classroom session. Its guidance calls for awareness, repeated practice, feedback, and continual reinforcement, and notes that gains can fade when CRM concepts are not reinforced over time.

The FAA makes an especially useful point: desirable behavior practiced during normal, lower-stress operations increases the likelihood crews will function effectively when workload and stress become high.

This mirrors one of the deepest ideas behind Peak.

Teams do not become excellent communicators during a crisis because they read a book about communication.

They fall back on habits.

Do they regularly surface problems?

Do they challenge assumptions?

Do they respect ownership?

Do they make decisions?

Do they communicate across teams?

Do they learn?

Does the CEO empower people?

Do team members trust Triage enough to use it?

Peak's cadence creates repeated practice.

Weekly Camp.

Triage.

Quarterly or Semiannual planning.

Annual planning.

Team Surveys.

Meeting ratings.

Over time, the operating behaviors can become more habitual.

That is why Peak Teams describes Peak as a system for building the fundamentals through repetition until the desired behaviors become increasingly natural.

Culture Is What the Team Repeatedly Does

CRM's history also offers a warning about one-time organizational interventions.

FAA guidance says classroom awareness by itself does not fundamentally change long-term behavior. Recurrent practice, feedback, and reinforcement are required, and CRM should eventually become embedded throughout training and operations rather than existing as a separate program.

Companies frequently make the opposite mistake.

They hold a leadership offsite about communication.

They introduce new values.

They conduct one team-building workshop.

Everyone feels energized.

Then the organization returns to its old operating system.

The old behaviors return.

That is because culture is not only what leadership says matters.

It is also what the organization's repeated routines teach people to do.

If meetings reward status reporting, people give status.

If bad news creates punishment, people delay bad news.

If every decision returns to the CEO, people stop making decisions.

If Triage consistently resolves important issues, people trust Triage.

If Weekly Camp consistently creates useful shared visibility, people prepare for Weekly Camp.

If leaders regularly ask for dissenting expertise and then make clear decisions, people learn how to challenge constructively.

Operating rhythm reinforces behavior.

Behavior becomes culture.

Debriefing Makes Team Performance Visible

CRM also relies heavily on feedback and debriefing.

FAA guidance recommends crew self-critique and careful debriefing around decisions, communication, teamwork, and leadership. It treats feedback as more effective when it addresses specific behaviors rather than vague impressions.

This parallels the Learning behavior inside Peak.

Peak teams review more than business outcomes.

They rate Weekly Camp.

They use Team Surveys.

They review wins and misses.

They examine what went Off-Course.

Quarterly, Semiannual, and Annual sessions create moments for reflection and course correction.

The point is not retrospection for its own sake.

It is to make the team's way of operating visible enough to improve it.

The question is not only:

Did we hit the target?

It is:

What did the way we worked teach us about how we should operate next time?

CRM Became Bigger Than the Cockpit Because the System Was Bigger Than the Cockpit

The evolution from Cockpit Resource Management to Crew Resource Management is itself instructive.

FAA guidance explains that CRM expanded as the industry recognized that safe flight operations depended on people beyond the cockpit, including flight attendants, maintenance personnel, dispatchers, and air traffic controllers.

That is a team-of-teams realization.

The outcome depends on a larger system than the most visible team.

Companies make a similar mistake when they focus organizational execution only on the executive leadership team.

The leadership team matters enormously.

But the company executes through many teams.

Aerospace execution may involve Engineering, Manufacturing, Quality, Program Management, Supply Chain, Operations, Finance, customers, and outside partners.

A defense program may rely on people outside the company's formal reporting structure.

A physical-AI company may coordinate hardware, software, field operations, safety, manufacturing, and customer environments.

The operating system eventually needs to connect more than one room.

Peak can operate across leadership teams, functional teams, divisional teams, and other layers of the organization.

The goal is not to make every team identical.

It is to create compatible organizational interfaces through which direction, information, dependencies, ownership, and learning can move.

Why This Matters for Frontier Tech

Frontier-tech organizations combine several characteristics that make CRM's underlying lessons particularly relevant.

Deep specialists.

Technical uncertainty.

Physical-world consequences.

Cross-functional dependencies.

Capital constraints.

Customer commitments.

Long execution cycles.

Government or regulatory involvement.

Rapidly changing information.

A technically sophisticated workforce can actually make coordination harder if every function contains strong people accustomed to operating independently.

The CEO's job is not to suppress that expertise.

It is to create a system through which the expertise can be combined.

That requires:

clear Mission and intent,

explicit ownership,

shared situational awareness,

constructive challenge,

decision pathways,

cross-checking,

operating rhythm,

and learning.

Those are not aviation procedures.

They are organizational capabilities.

CRM and Peak Were Developed Through Different Paths

Crew Resource Management grew out of aviation human-factors research and the recognition that technically proficient individuals could still fail as a crew when communication, decision-making, leadership, monitoring, task allocation, or situation awareness broke down. NASA's 1979 workshop helped catalyze its development, and CRM subsequently expanded across the broader aviation system.

Peak OS emerged from a different environment.

Over more than two decades of working with hundreds of growth-company teams, I repeatedly saw technically and professionally capable leaders struggle when the organizational habits connecting them were weak.

The names are different.

The environments are different.

The mechanisms are different.

But the organizational conclusion is remarkably compatible:

A collection of experts does not automatically become an expert team.

The team needs a system for how expertise interacts.

High-Consequence Teams Need Both Expertise and Teamwork

The strongest lesson from Crew Resource Management is not that technical skill matters less.

It is that technical skill alone is incomplete.

The team needs technical competence.

And communication.

Technical competence.

And situation awareness.

Technical competence.

And clear leadership.

Technical competence.

And appropriate challenge.

Technical competence.

And monitoring.

Technical competence.

And decision discipline.

Technical competence.

And recurrent learning.

The same is true in a scaling company.

Peak OS does not replace functional expertise.

It exists partly to help that expertise combine.

Symbiosis connects the specialists.

Communication moves the information.

Alignment creates shared context.

Empowerment allows people to use their expertise.

Learning makes the system better over time.

The operating rhythm reinforces all five.

For CEOs of aerospace, defense, robotics, advanced manufacturing, autonomy, physical AI, and other frontier-tech companies, the implication is important.

Hiring exceptional specialists is necessary.

But the organization eventually needs another capability:

the ability to reliably turn exceptional individual expertise into coordinated organizational judgment and action.

That is the difference between having great people in the organization and having a great team capable of executing together when the stakes, workload, and uncertainty rise.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?