The COO role lives or dies on the CEO-COO partnership.

A strong COO with a weak partnership becomes politically exposed. A strong CEO with a poorly defined COO creates confusion. A friendly relationship without decision clarity creates drift. A high-trust relationship without productive tension becomes mutual reinforcement. A tense relationship without trust becomes a company-wide anxiety machine.

The partnership has to be designed.

The CEO and COO do not need to be the same person in two bodies. In fact, the best partnerships often work because the executives are different. The CEO may be externally oriented, visionary, product-driven, market-facing, or capital-focused. The COO may be integrative, operationally rigorous, system-minded, and execution-focused. The value comes from complementarity.

But complementarity without rules becomes ambiguity.

Proxy authority is the core issue

The COO often acts as the CEO's operating proxy. That does not mean assistant. It means the COO can make or drive decisions on behalf of the company's operating model with the CEO's trust and visible backing.

Proxy authority must be explicit. It should be visible enough that executives know when they are dealing with the COO's personal opinion, the COO's delegated decision right, or the CEO-COO operating position.

Can the COO reprioritize cross-functional work? Can they tell an executive that a plan is not good enough? Can they move headcount between initiatives? Can they decide a tradeoff when two functions disagree? Can they represent the CEO's view in operating forums? Can they say no to work the CEO has casually encouraged? Can they escalate performance concerns about a functional leader?

If the answers are unclear, the company will test the role.

Executives are rational. If they believe the COO is merely coordinating, they will treat COO requests as optional. If they believe the COO speaks for the CEO on operating matters, they will engage differently. If they see the CEO override the COO casually, they will route around the COO. If they see the COO make decisions the CEO later disowns, trust collapses.

The CEO creates the COO's authority through behavior, not announcement.

The CEO must stop being the appeal court for everything

One common failure mode is executive triangulation.

A functional leader dislikes the COO's call and goes to the CEO. The CEO, trying to be helpful or maintain connection, reopens the decision. The COO becomes uncertain. The functional leader learns the real decision forum is the CEO's private channel. The operating system degrades.

This does not mean the COO is always right or that executives cannot escalate. It means escalation rules need to be clear.

A healthy rule might be:

  • Disagree directly with the COO first.
  • If the decision is within the COO's delegated authority, commit after debate.
  • If escalation is appropriate, bring the COO into the conversation with the CEO.
  • The CEO does not reverse operating decisions privately unless there is a serious issue.
  • When the CEO and COO disagree, they resolve it quickly and communicate one operating answer.

Without rules like these, the COO's authority becomes performance art.

Productive tension is required

The COO should not be a smoother of all CEO ideas.

A useful COO creates tension. They ask whether the strategy is resourced. They point out when the CEO's new idea contradicts last week's priority. They expose operating consequences. They say when the company is trying to do too much. They challenge fuzzy ownership. They force tradeoffs into the open.

This can be uncomfortable because CEOs often generate energy by creating possibility. The COO often creates value by converting possibility into constraint.

That tension is not a bug. It is the mechanism.

The CEO says, “This matters.” The COO asks, “What will we stop, who owns it, what decision rights change, how will we measure it, and what operating cost are we willing to pay?”

If the COO never creates this pressure, they are not protecting execution. If the COO creates pressure without understanding ambition, they become the department of no.

The partnership needs both altitude and friction.

The private disagreement, public alignment rule

CEO and COO disagreement should be frequent enough to improve decisions and private enough not to destabilize the company.

The executive team should see that the COO has real authority and independent judgment. They should not see a constant unresolved rift between the CEO and COO.

The practical rule is simple: debate hard in private, align clearly in public.

This requires a regular CEO-COO operating session, not just ad hoc Slack threads. The session should cover:

  • strategic priorities and operating implications;
  • unresolved executive-team tensions;
  • upcoming decisions;
  • resource tradeoffs;
  • CEO commitments that may create operating load;
  • COO concerns about execution risk;
  • people and performance issues;
  • where the CEO needs to visibly reinforce the COO;
  • where the COO may be overstepping or under-communicating.

The best CEO-COO pairs maintain a shared operating map. They know which problems are strategic, which are execution risks, which are people issues, and which are noise.

Do not split the company accidentally

Some CEO-COO partnerships create an accidental two-government system.

The CEO owns vision, product, culture, and external relationships. The COO owns operations, people, finance, and execution. On paper this looks clean. In reality, many company decisions cut across those domains. Product strategy affects operations. Culture affects execution. Finance affects strategy. People decisions affect every plan.

If the split is too simplistic, leaders start asking: who really decides?

The answer is not to avoid division of labor. The answer is to define decision rights at the boundary.

For example:

  • The CEO owns company strategy; the COO owns operating plan translation.
  • The CEO owns final call on existential strategic bets; the COO owns resource allocation process and execution tradeoffs within agreed priorities.
  • The CEO owns executive hiring decisions; the COO owns operating performance expectations and cadence for the executive team.
  • The CEO owns board narrative; the COO owns operating truth and plan integrity.
  • The CEO owns culture direction; the COO owns the systems that reinforce or contradict it.

The boundary should be explicit enough that leaders know where to go and flexible enough that the CEO and COO can adapt as the company changes.

Write down proxy authority before stress arrives

The CEO and COO should define proxy authority in calm weather, not during a missed quarter or executive conflict. A simple charter should name:

  • decisions the COO can make independently;
  • decisions the COO can make as CEO proxy;
  • decisions the COO can recommend but not finalize;
  • decisions that require CEO involvement before communication;
  • where functional leaders retain final authority;
  • how appeals work without reopening every hard call.

The value of the charter is not legal precision. It is reducing the number of moments where the company has to guess whether the COO really speaks with authority.

The working agreement

Every CEO-COO pair should write a working agreement. It does not need to be bureaucratic. It needs to be honest.

Include:

Role thesis. Why does this COO role exist now?

Decision rights. What can the COO decide independently? What requires CEO input? What requires executive-team input? What is reserved for the CEO?

Proxy authority. In which forums does the COO represent the CEO's operating authority?

Escalation rules. How do leaders challenge COO decisions? How do CEO and COO handle appeals?

Communication rules. What gets communicated jointly, by CEO only, by COO only, or through the executive cadence?

Conflict rules. How do CEO and COO disagree, resolve, and align?

Success measures. What should be better in the company if the partnership is working?

Anti-patterns. What behavior would damage the partnership? Examples: private reversals, triangulation, surprise commitments, silent disagreement, unclear ownership, COO overreach, CEO avoidance.

Trust is built through operating consistency

The CEO trusts the COO when the COO exercises judgment, not just energy. The COO trusts the CEO when the CEO reinforces authority, shares context early, and does not create unmanageable operating load through casual commitments.

The company trusts the partnership when decisions are clear, escalation is fair, and leaders do not have to guess which executive reality is real.

A great CEO-COO partnership is not comfortable all the time. It is reliable.

That reliability is what lets the COO do the real job: turn strategy into operating reality with enough authority, tension, and trust to make the company executable.