COO vs Chief of Staff vs CPO:
What's the Difference?

A COO runs operations. A Chief of Staff coordinates across teams on borrowed authority. A CPO decides what gets built. A PM manages one team's backlog.

The Operator Seat is the role that makes the everyday calls on what ships, inside the strategy leadership already set, and makes them happen across teams.

In 83 executive job postings at small product companies, only one gave a single role both of those responsibilities.

Who gets which half of the job, from 83 executive job postings Two overlapping circles. Left circle, makes the decisions: CPO (product decisions) and CTO (tech decisions). Right circle, owns the seams: Chief of Staff. The overlap is the Operator Seat, found in 1 of 83 postings. The COO sits in its own circle, running the back office, overlapping partly into the seams. Makes the decisions CPO product decisions CTO tech decisions Owns the seams Chief of Staff Operator Seat 1 of 83 postings COO the back office Who gets which half of the job: CPO and CTO make decisions, the Chief of Staff owns the seams, the Operator Seat does both (1 of 83 postings), and the COO runs the back office, overlapping partly into the seams. Makes the decisions CPO product decisions CTO tech decisions Operator Seat 1 of 83 postings Owns the seams Chief of Staff COO the back office
From 83 executive postings at small product companies: 7 of 21 CPOs and 1 of 15 CTOs get the call on what ships, and only 2 of each own the seams between teams. 25 of 39 Chief of Staff roles own the seams; none gets the call. 7 of 8 COOs carry finance, legal, HR or other back-office work, and 4 of 8 get some of the seams. One posting gave a single role both.

The short version

Every one of these is a real job, and none of them is wrong to hire. The problem is what founders expect the hire to fix.

The Chief of Staff gets the seams: the cross-team problems nobody owns. In the postings I read, 25 of 39 Chief of Staff roles were explicitly handed that work. None of the 39 got the final call. So the calls still go back to the founder, and the Chief of Staff carries messages. A liaison gathers the information and takes it to whoever makes the call. The Operator Seat makes the call.

The CPO gets the opposite half. Seven of 21 CPO postings gave the role the final call on what gets built, more than any other title. Only 2 of 21 also owned the work between product, engineering, sales and operations. The CPO, or the founder, sets what to build. The Operator Seat makes the everyday calls that get it shipped.

The COO in these postings runs the business functions. 7 of 8 carry back-office work like finance, legal and HR, 4 of 8 get some of the cross-team work, and 1 of 8 gets the call on what ships.

The one posting that gave a single role both responsibilities was a CTO at a hardware company who also owned the product roadmap. Reading the list of things that role was meant to own, I'm not sure one person could do all of it.

Side by side

RoleWhat it ownsFinal call on what ships?Owns the work between teams?Where its authority comes fromWhat the postings show
COOFinance, legal, HR and the operating rhythmRarely (1 of 8)Sometimes (4 of 8)Owns its own functions5 of 8 list finance, legal and HR
Chief of StaffCross-team problems, special projects, the operating rhythmNo (0 of 39)Often (25 of 39)Borrowed from the CEO34 of 39 use borrowed or mixed authority; 30 of 39 also carry HR, admin, finance or legal work
CPOWhat gets built: roadmap and prioritiesSometimes (7 of 21)Rarely (2 of 21)Owns product21 of 21 own product decisions
CTOEngineeringRarely (1 of 15)Rarely (2 of 15)Owns engineering15 of 15 own engineering execution
PMOne team's backlog and requirementsNoNoWorks inside a plan someone else setNot in the study
Operator SeatWhether what gets decided actually shipsYes, inside the strategy the founder setYesHanded over by the founder, on purpose, for a defined set of calls1 of 83 postings described it

Which one do you need?

A table won't make the call for you. Look at the decisions that are waiting on you right now.

  • If they're engineering calls, you might look at a CTO or head of engineering.
  • If they're about what to build next, a CPO.
  • If finance, legal, HR and operations are eating your week, a COO.
  • If the cross-team work keeps falling through but you're not ready to hand over decisions, a Chief of Staff can carry the coordination. Expect the decisions to keep coming back to you.
  • If decisions keep landing on your desk because nobody else can both make the call and make it happen, that's the Operator Seat.

You may already have someone doing that job without the title. They just need to be blessed with it: the title, the authority to make a defined set of calls, and the knowledge to make them well. If any of the three stays with you, the calls drift back up.

Searching for a fractional CPO?

A lot of founders who search for a fractional CPO already know what they want to build. What's stuck is getting it to land across engineering, sales and operations without every call routing through them.

A CPO is the right hire when the open question is what to build. When the open question is why decisions don't turn into shipped work, a CPO covers the deciding. Getting those decisions to land across engineering, sales and operations is the other half, and only 2 of 21 CPO postings included it.

One way to tell: list the last three calls that waited on you. If they're product calls, look at a CPO. If they're calls between teams, look at the Operator Seat.

Questions

What's the difference between a COO and a Chief of Staff?

In small product companies, the COO usually runs the business functions: finance, legal, HR and operations. The Chief of Staff works across teams on the CEO's behalf, on borrowed authority. In 111 postings, none of the Chief of Staff roles got the final call on what ships.

Is the Operator Seat just a COO?

No. A COO in a small company mostly runs the back office. The Operator Seat makes the everyday calls on what ships, inside the strategy leadership already set, and makes them happen across teams, so stuck decisions stop landing on the founder's desk.

Do I need a fractional CPO or a fractional operator?

If what's stuck is deciding what to build, a CPO. If you know what to build and it doesn't land across teams, that's the Operator Seat.

Can someone already on my team fill the Operator Seat?

Often, yes. If someone has been doing the job without the title, give them the title, the authority over a defined set of calls, and the context to make those calls well.

Is everything still landing on your desk?

The free Operator Vacuum Diagnostic: three quick checks, and the question to ask before you hire into any of these titles.