JP 5-0 Joint Planning and Peak OS: Why Complex Organizations Need a Team-of-Teams Operating System

As organizations become more complex, execution stops being primarily a problem of managing individuals.

It becomes a problem of coordinating teams.

Engineering has its objectives. Product has its roadmap. Sales has its targets. Operations has its priorities. Finance has its constraints. People has its hiring plan. In frontier-tech companies, that network can expand further across Manufacturing, Quality, Program Management, Supply Chain, Government Affairs, customers, regulators, strategic partners, and investors.

Each team can be highly capable.

Each team can even perform well against its own objectives.

And the organization can still fail.

That is what makes the U.S. military's approach to joint planning particularly interesting when compared with Peak OS.

The Joint Chiefs of Staff describe joint doctrine as principles for employing U.S. military forces in coordinated and integrated action toward a common objective. JP 5-0, Joint Planning, is identified as the keystone document for joint planning and provides the doctrinal foundation for planning joint campaigns and operations.

Peak OS was not developed from Joint Planning doctrine. It emerged through more than two decades of working with hundreds of founders, CEOs, investors, and leadership teams and identifying the operating habits that repeatedly separated teams that scaled effectively from teams that fragmented as complexity increased.

Yet when the two are examined together, an important parallel emerges:

Complex organizations cannot execute through a collection of independently optimized teams. They need a way to coordinate the whole.

In Peak, this is the idea of the organization as a team of teams.

For military and former-military leaders now building aerospace, defense, advanced manufacturing, robotics, autonomy, AI, and other frontier-tech companies, that concept may feel immediately familiar.

What Is Joint Planning?

JP 5-0 is the Joint Chiefs of Staff's keystone publication for joint planning. The Joint Chiefs describe the planning process as determining how available capabilities—the means—can be employed through particular approaches—the ways—to achieve objectives—the ends—while considering risk.

The significance of the word joint is larger than simply having more people involved.

Joint operations require organizations with different capabilities, responsibilities, expertise, and perspectives to contribute toward a common objective.

The broader Joint Doctrine system exists partly to create a common perspective from which different organizations can plan and operate together. The Joint Chiefs describe the 5-0 series specifically as doctrine for joint, interagency, and multinational planning activities.

That creates a coordination problem that should be recognizable to anyone who has led a scaling company.

The organization does not need every team to perform the same job.

It needs different teams to perform different jobs in a coordinated way.

That distinction is central to Peak OS.

Scaling Changes the Unit of Execution

In a small company, the organization may effectively function as one team.

The founder knows everyone.

Engineering hears what Sales hears.

Product understands the customer conversation.

Finance knows what is being hired.

People understand what the product roadmap requires.

Most important information travels informally because everyone is close enough to the source.

As the organization grows, that model breaks.

One team becomes several teams.

Several teams become functional organizations.

Functions develop sub-teams.

New executives arrive with deeper specialization.

More management layers appear.

The number of relationships and dependencies between groups increases dramatically.

The challenge is no longer simply:

Can each team perform?

It becomes:

Can these teams perform together?

That is the organizational transition Peak's concept of Symbiosis is designed to address.

In Peak Teams, Symbiosis is described as people and teams working together in trust, respect, and unity toward shared purpose and goals. Importantly, the book extends the idea beyond the individual team: even if separate teams work effectively internally, the organization must also develop Symbiosis as a team of teams.

Sales performing well in isolation is not enough.

Engineering performing well in isolation is not enough.

Finance performing well in isolation is not enough.

The organization's outcomes depend on the connections between them.

The Leadership Team Has to Optimize the Whole

One of the most common execution problems in scaling companies is local optimization.

Every functional leader is competent.

Every functional leader is motivated.

Every functional leader wants the company to succeed.

Yet each leader naturally sees the organization through the lens of their own function.

Sales wants greater product flexibility.

Engineering wants greater technical stability.

Product wants development capacity.

Finance wants spending discipline.

People wants more predictable hiring requirements.

Operations wants fewer last-minute changes.

None of those perspectives are inherently wrong.

The problem appears when each function optimizes for itself without sufficient understanding of the impact on the rest of the organization.

Peak therefore treats the leadership team as more than a collection of functional representatives.

Its responsibility is to optimize the company as a whole.

That begins by creating shared clarity around Mission, Three-Year Vision, and the One-Year Plan.

In Peak planning, every functional area is represented, and leaders work together to understand and align objectives across the organization. The planning process explicitly looks for cross-functional relationships—for example, Sales requirements aligning with Marketing, Product plans aligning with Engineering, and financial capacity aligning with hiring.

That is where the parallel to joint planning becomes powerful.

Different groups maintain different capabilities.

They do not become one function.

They become coordinated around one outcome.

Planning Has to Move Up, Down, and Across

Many companies describe their planning process as a cascade.

The board gives direction to the CEO.

The CEO and leadership team create the strategy.

Leadership gives goals to functions.

Functions create goals for their teams.

Information moves downward.

That model is incomplete.

Peak planning is better understood as moving up, down, and across the organization.

Before a leadership planning session, functional leaders work with their own teams. They collect information, ideas, constraints, opportunities, and perspectives from the people closest to execution.

The book explicitly describes this as bottoms-up involvement. Functional leaders bring what they have learned from their teams into the leadership planning process.

There is also an upward dimension beyond the leadership team. For a CEO, the board can function as an up-team that provides perspective, expectations, strategic context, and governance input.

The leadership team then synthesizes those different perspectives into an organizational Three-Year Vision, One-Year Plan, and nearer-term objectives.

But the process still is not complete.

The plan travels back through the organization.

Teams interpret what the organizational plan means for them. They discuss the objectives with the people who will execute them. They identify dependencies, resource constraints, missing capabilities, sequencing issues, and assumptions that may not have been apparent at the leadership level.

That creates feedback.

The plan gets challenged and refined.

Meanwhile, information also moves laterally.

Product talks to Engineering.

Sales talks to Product.

Engineering talks to Manufacturing.

Finance talks to People.

Operations talks to everyone.

The result is not:

Leadership plan → functional plans.

It is closer to:

Organizational information → leadership synthesis → team planning → cross-team coordination → feedback → refinement.

That is a team-of-teams planning process.

Good Planning Preserves Specialized Expertise

The objective of integrated planning is not to eliminate differences between teams.

Those differences are the reason the teams exist.

Joint forces derive value from combining distinct capabilities. Joint doctrine provides a common basis for coordinated and integrated action without turning the participating organizations into identical units.

The same principle matters in companies.

A great CFO should think differently from a great CTO.

A great Head of Manufacturing should see problems differently from a great Head of Sales.

A Product leader should not need to become an engineer.

An Engineering leader should not need to become a marketer.

The organization hired those people because of their specialized expertise.

Peak does not attempt to eliminate that specialization by forcing every team to operate identically at the level of its functional work.

Instead, it establishes common organizational fundamentals around:

Mission.

Direction.

Outcomes.

Ownership.

Visibility.

Operating rhythm.

Decision-making.

Learning.

The functions retain their unique expertise while operating from a shared organizational context.

That is the balance scaling companies need.

Common operating system. Different specialized capabilities.

Cross-Functional Dependencies Are Often Where Execution Actually Fails

Leadership teams frequently diagnose missed plans as performance problems inside a department.

Sometimes they are.

But many execution failures occur between departments.

Imagine a frontier-tech company trying to deliver a new autonomous platform.

Engineering has to complete a hardware milestone.

Software has to integrate with the hardware architecture.

Supply Chain has to procure long-lead components.

Manufacturing has to build the system.

Quality has to validate it.

Program Management has contractual milestones.

Business Development has made commitments to the customer.

Finance has assumptions about cash and revenue timing.

People has specialized hiring requirements.

Operations has testing requirements.

No single function owns every piece of the outcome.

If one team changes its timing, the effect may move through the entire organization.

This is why strong functional performance can coexist with weak organizational execution.

Everyone can be busy.

Everyone can complete work.

Everyone can report progress.

Yet the shared outcome can still miss.

Peak OKRs are designed partly around this reality. The book describes objectives and key results as a way to create focused, measurable, cross-functional initiatives, with teams understanding not only their individual contribution but how their work supports the broader organizational plan.

The deeper lesson is:

Dependencies are not edge cases in complex organizations. Dependencies are the architecture of execution.

Peak's Symbiosis Is an Organizational Capability

This is where the Peak behavior of Symbiosis deserves particular attention.

Symbiosis is sometimes easy to mistake for a softer concept about team culture.

It is much more operational than that.

The book describes Symbiosis as an environment in which teams understand where they are going, understand their contribution, trust teammates to execute their roles, and work collectively toward the organization's Mission and Vision.

At organizational scale, that means a team has to understand two things simultaneously:

What do we own?

and

What do others need from us?

That second question is where many organizations break.

A function can be exceptionally accountable for its own goals while being a poor partner to the rest of the enterprise.

The organization then becomes a collection of well-managed silos.

Peak's team-of-teams model requires another level of accountability:

accountability to the whole.

Sometimes that means changing a functional priority because the company priority is more important.

Sometimes it means supporting an objective owned elsewhere.

Sometimes it means identifying a dependency early enough for another team to adjust.

Sometimes it means accepting that the best decision for one department is not the best decision for the company.

That is Symbiosis in execution.

Company-Level OKRs Create Shared Missions Across Functions

The distinction becomes particularly visible in how Peak approaches OKRs.

A traditional goal-setting model can easily produce a list of functional objectives:

Sales has Sales goals.

Engineering has Engineering goals.

Marketing has Marketing goals.

Finance has Finance goals.

The teams may all be perfectly clear and accountable.

But nothing necessarily forces them to work together.

Peak starts with a small number of the most important team-level or company-level objectives, particularly when an outcome requires multiple functional contributions.

A successful product launch, for example, may have key results owned across Product, Engineering, Marketing, Sales, and Customer Success.

One objective.

Multiple specialized contributors.

Shared understanding of the outcome.

Clear ownership of individual components.

Then the functions develop their own supporting objectives in the context of those company priorities.

In Peak Teams, the process intentionally gives the entire leadership team visibility into functional objectives because objectives rarely exist in isolation; one function's work is often dependent on or consequential to another function.

That creates a business version of a powerful joint-planning principle:

Different capabilities converge on a common objective.

The Board Can Be Part of the Operating Picture Without Running the Company

The team-of-teams concept can extend upward as well as downward.

The CEO sits at an unusual intersection.

The leadership team looks to the CEO for organizational direction.

The board looks to the CEO for organizational performance.

Investors may have expectations about capital, growth, milestones, and risk.

The CEO therefore connects multiple systems.

Peak's planning architecture can create a common language across those boundaries.

The Three-Year Vision gives stakeholders a shared understanding of where the company intends to go.

The One-Year Plan makes the nearer-term definition of success visible.

KPIs create measurable signals of business performance.

OKRs create visibility into the organizational capabilities and initiatives being built to advance the plan.

The book notes that creating the Three-Year Vision together gives the organization a clearer message that can be communicated to stakeholders, including investors and the board.

That does not mean the board should manage the company's functional objectives.

It means governance becomes stronger when the board, CEO, and management team can discuss execution from a shared picture of direction, progress, risks, and dependencies.

That is organizational visibility without collapsing the boundaries between governance and management.

Visibility Is What Connects the Teams During Execution

Integrated planning gets the teams pointed in the same direction.

But organizations can drift apart again quickly once execution begins.

Every function returns to its specialized work.

New information appears.

Priorities compete.

Customers make requests.

Technical issues emerge.

People leave.

Budgets change.

Teams naturally begin narrowing their field of view toward the work immediately in front of them.

Peak uses a common operating rhythm to reconnect those perspectives.

The Weekly Camp provides recurring visibility into OKRs and KPIs. Teams identify what is On-Course, Off-Course, Done, or intentionally being pushed.

Off-Course items move to Triage.

Cross-functional issues can be discussed by the people who collectively understand the implications.

That rhythm does not require every person in the company to attend the same meeting.

Each team can operate its own cadence while the organizational architecture maintains alignment between the teams.

This distinction matters:

Team-of-teams does not mean one giant team meeting.

It means an organization of connected teams operating through compatible rhythms and shared context.

A Team of Teams Requires Both Vertical and Horizontal Alignment

Organizations traditionally spend more energy on vertical alignment.

Does the employee understand their manager's priorities?

Does the functional leader understand the CEO's priorities?

Does the CEO understand the board's expectations?

Those relationships matter.

But complex execution increasingly depends on horizontal alignment.

Does Engineering understand the effect its decision has on Manufacturing?

Does Sales understand Product constraints?

Does Finance understand hiring requirements early enough to model capacity?

Does Product understand commitments Program Management has made externally?

Can teams see a dependency before it becomes a missed deadline?

The more specialized an organization becomes, the more its execution risk migrates into these horizontal relationships.

That makes the organizational structure look less like a simple hierarchy and more like a network.

The hierarchy still matters.

Ownership still matters.

Authority still matters.

But organizational performance increasingly depends on how information, decisions, dependencies, and commitments move across the network.

Joint doctrine's emphasis on coordinated and integrated action offers a useful external parallel because it begins with the assumption that different organizational components must contribute their capabilities toward common objectives.

Peak reaches a similar conclusion from the business environment.

Slingshot Aerospace Shows Why the Parallel Resonates

The Slingshot Aerospace story in Peak Teams provides an especially relevant example.

Melanie Stricklan, reflecting on her experience as CEO and co-founder, described how she and a fellow co-founder brought combat-tested U.S. Air Force experience into the company. They understood mission, end goals, and decisive action under uncertainty.

Yet Slingshot still encountered organizational fragmentation.

The leadership team was not consistently aligned around one understanding of the Mission and Vision. Parts of the business were effectively pulling in different directions.

Through the Peak process, those differences became visible.

Stricklan described the company ultimately looking for people who could work together in a team of teams led by a mission-driven perspective, and she connected that shift with greater alignment and productivity.

That is an important example because it demonstrates why Peak can resonate so strongly with military and former-military leaders.

They may already believe deeply in mission.

They may already understand decentralized execution.

They may already understand coordinated teams.

The challenge is translating those beliefs into a repeatable operating architecture for a company.

Peak provides business mechanisms for doing that.

Frontier Tech Is Inherently a Joint Execution Environment

This becomes particularly important in frontier technology.

A software company can sometimes change a product and deploy the new version in hours.

A spacecraft cannot.

An autonomous vehicle cannot.

A defense hardware platform cannot.

A complex manufacturing system cannot.

Physical systems create deeper interdependencies.

Engineering decisions affect materials.

Materials affect supply chain.

Supply chain affects manufacturing.

Manufacturing affects testing.

Testing affects certification.

Certification affects delivery.

Delivery affects revenue.

Revenue affects financing.

Financing affects hiring.

Hiring affects engineering capacity.

Everything connects.

External organizations can also become part of the system:

government customers,

prime contractors,

suppliers,

regulators,

research partners,

investors,

and strategic partners.

The organization is therefore coordinating not simply a hierarchy but an ecosystem of teams and capabilities.

That makes integrated execution a competitive capability.

The companies that learn to operate as a team of teams can use specialization without being fragmented by it.

Symbiosis Does Not Mean Consensus

There is another important distinction.

Coordinated teams do not need to agree on everything.

In fact, strong teams should contain meaningful differences in perspective.

Engineering should challenge Sales.

Finance should challenge operating assumptions.

Product should challenge technical priorities.

The board should challenge management.

Leadership should challenge the plan.

The objective is not harmony.

It is shared understanding followed by coordinated commitment.

In Peak Teams, strong communication includes the ability for people to be heard, disagree, and then commit to the team's decision.

That is essential in a team-of-teams organization.

Without disagreement, the organization loses the benefit of specialized expertise.

Without commitment after the decision, the organization fragments.

High-performance execution requires both.

Local Success Is Not Organizational Success

The central lesson from the comparison between Joint Planning and Peak OS can be stated simply:

The company is the unit of performance.

Not Sales.

Not Engineering.

Not Product.

Not Finance.

Not the leadership team.

The organization wins or loses as a system.

That means a functional leader's responsibility eventually extends beyond their own department.

The Head of Engineering is responsible for Engineering—but as a member of the leadership team, that leader is also responsible for the company.

The CFO is responsible for Finance—but also for the company.

The Head of Sales is responsible for Sales—but also for the company.

That change in identity is one of the most important transitions a leadership team makes as a company scales.

Peak's concept of Symbiosis captures it well:

My team matters. Your team matters. But the whole matters more than either of us independently.

Similar Complexity Produces Similar Operating Principles

The Joint Chiefs of Staff developed joint doctrine from the need to coordinate distinct military capabilities in integrated action toward shared objectives. JP 5-0 provides the planning doctrine supporting that environment.

Peak OS emerged through a completely different path.

Over more than two decades and hundreds of engagements, I repeatedly saw the same business execution problem.

As organizations grew, highly capable people formed highly capable teams.

Then those teams became disconnected.

The problem was rarely lack of effort.

It was lack of alignment between efforts.

That experience helped shape the Peak behaviors of Symbiosis, Communication, Alignment, Learning, and Empowerment and the systems that reinforce them.

Different environments.

Different terminology.

Different consequences.

But a remarkably similar organizational truth:

Complex organizations succeed when specialized teams can contribute their distinct capabilities while remaining coordinated around the mission, the plan, and the outcomes of the whole.

That is the deeper parallel between Joint Planning and Peak OS.

And it is one reason a team-of-teams operating model may become increasingly important as frontier-tech companies scale into some of the most complex organizational environments in business.

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?