The COO role should make the company faster, clearer, more reliable, and more honest.

If it does not, something is wrong. The problem may be the person, but it is often the design of the role. COO roles fail when authority is vague, expectations are sprawling, decision rights are unclear, the CEO does not truly delegate, functional leaders route around the role, or the company expects one executive to compensate for an underbuilt operating system.

The right question is not “Do we have a COO?”

The right question is “Is our operating model working?”

This audit is a practical way to answer it. Use it with the CEO, COO, and executive team together; if each group scores the model differently, that disagreement is itself useful signal.

1. Role thesis

Start with the most basic question: why does the COO role exist now?

A strong role thesis sounds like:

  • “The COO owns the operating system that turns strategy into resourced execution across functions.”
  • “The COO reduces CEO bottleneck by owning planning, cadence, resource tradeoffs, and cross-functional execution.”
  • “The COO is responsible for making enterprise customer delivery reliable across GTM, product, legal, finance, and support.”
  • “The COO owns the operating model required for the next stage of scale.”

A weak role thesis sounds like:

  • “The COO handles operations.”
  • “The COO brings discipline.”
  • “The COO helps the CEO.”
  • “The COO makes sure things get done.”

Vague roles create vague accountability.

Audit question: can the CEO, COO, and executive team describe the COO's role in the same concrete way?

2. CEO-COO authority

The COO needs visible authority. Not unlimited authority. Clear authority.

Audit:

  • What can the COO decide independently?
  • What can the COO decide as the CEO's proxy?
  • What requires CEO approval?
  • What requires executive-team debate?
  • How are COO decisions challenged or escalated?
  • Does the CEO reinforce COO decisions publicly?
  • Do executives route around the COO to get a different answer?

If leaders are unsure whether the COO is facilitator, coordinator, decision-maker, president, chief of staff, or operating architect, the role will create confusion.

3. Strategy-to-execution translation

A COO should make strategy operational.

Audit:

  • Do strategic priorities show up in headcount, budget, roadmap, incentives, and executive attention?
  • Are priorities few enough to be resourced?
  • Are tradeoffs explicit?
  • Does the operating plan explain what will stop, slow, or be deprioritized?
  • Are goals connected to accountable owners and decision forums?
  • Are strategic initiatives reviewed for outcome progress, not just activity?

If strategy changes but the operating system does not, the COO function is underpowered.

4. Resource allocation

Resource allocation is where strategy becomes real.

Audit:

  • Is there a clear process for allocating headcount and budget across priorities?
  • Are resources reviewed when reality changes?
  • Can the company move capacity away from lower-priority work?
  • Are pet projects protected by politics?
  • Do functions optimize their own plans at the expense of company priorities?
  • Does the COO have influence over resource tradeoffs, or only visibility?

A COO who cannot affect resources can often describe the problem but not solve it.

5. Decision flow

Decision drag is one of the clearest signs of operating model weakness.

Audit:

  • Which decisions are repeatedly slow or unclear?
  • Are decision owners defined?
  • Is input confused with approval?
  • Are escalation paths clear?
  • Are decisions reopened through backchannels?
  • Are tradeoffs named directly?
  • Are decisions made at the lowest responsible level?

The COO should reduce decision fog, not become the destination for every decision.

6. Cross-functional execution

The COO role should improve work that spans functions.

Audit:

  • Do major initiatives have one accountable owner?
  • Are dependencies visible and actively managed?
  • Do cross-functional forums make decisions or only exchange updates?
  • Are risks escalated early with options and recommendations?
  • Does work move without COO heroics?
  • Are repeated handoff failures fixed at the system level?

If everything important requires the COO's personal involvement, the company has not built cross-functional capability. It has built COO dependency.

7. Accountability system

Accountability should be clear without becoming bureaucratic.

Audit:

  • Are commitments specific, resourced, and owned?
  • Are standards defined before review?
  • Is progress evaluated by evidence, not vibes?
  • Are misses diagnosed accurately?
  • Are repeated misses acted on?
  • Is reporting producing decisions?
  • Do teams surface bad news early?

If accountability requires constant executive pressure, the system is weak.

8. Company metabolism

The company needs to sense, decide, allocate, execute, and learn at the right speed.

Audit:

  • How quickly does important reality reach leaders?
  • Are metrics and frontline narratives compared?
  • Do operating reviews change decisions?
  • Are resources moved when priorities change?
  • Does the company learn from misses?
  • Where has process become operating debt?

A good COO improves metabolism. A bad operating model traps reality in meetings.

9. Stage fit

The role must fit the company's stage.

Audit:

  • At the current size, does the COO add the right amount of structure?
  • Is the role too heavy for the company's speed needs?
  • Is the role too light for the company's complexity?
  • Has the COO role evolved as the company scaled?
  • Are expectations still based on an earlier stage?

A 30-person COO, a 300-person COO, and a 3,000-person COO are different jobs. The role should evolve before the company breaks around it.

10. Failure modes

Look for the common COO failure patterns:

  • Chief bottleneck officer: every hard issue routes through the COO.
  • Executive assistant with a title: lots of coordination, little authority.
  • Shadow CEO: unclear split creates triangulation and confusion.
  • Functional super-leader: one function improves while company operating architecture remains weak.
  • Process importer: discipline increases, speed dies.
  • Heroic fixer: problems get solved, systems do not improve.
  • Toothless integrator: accountable for execution without resource or decision authority.

Name the pattern early. COO role problems rarely fix themselves quietly.

How to score it

For each section, use a simple 1-3 score:

  • 1 = unclear or personality-dependent. The company relies on informal access, heroics, or private interpretation.
  • 2 = partially designed. Some mechanisms exist, but authority, ownership, or follow-through is inconsistent.
  • 3 = explicit and operating. The mechanism is understood, used, maintained, and improves execution.

The total score matters less than the pattern. A low score in CEO-COO authority will contaminate decision flow. A low score in resource allocation will make accountability theatrical. A low score in company metabolism means reality is arriving too late. Fix the constraint, not the most visible symptom.

The final scorecard

A COO operating model is healthy when:

  • the role thesis is clear;
  • the CEO visibly backs the COO's authority;
  • strategy becomes resourced execution;
  • decision rights are legible;
  • cross-functional work has accountable owners;
  • cadence produces decisions and learning;
  • resource allocation reflects priorities;
  • accountability is firm without bureaucracy;
  • reality surfaces early;
  • operating debt is actively reduced;
  • the company is less dependent on heroics over time.

The best COO makes the company more executable. Not more ornate. Not more managed for its own sake. More executable.

That is the final test.

If the COO disappeared for two weeks, would the operating system continue to function? If the answer is no, the COO may be powerful, but the system is fragile. If the answer is yes, the COO is doing the deeper work: building a company that can turn strategy into reality repeatedly, honestly, and at scale.