Skip to content

The role, explained

What Does a COO Do? Roles, Responsibilities and the Real Job

Chief operating officer is the least standardised title in the C-suite — which is why most answers to this question are vague. This guide gives you the real job: what a COO actually owns, how the role changes as a company grows from fifty to five hundred people, where it ends and the CEO’s begins, and the myths worth retiring.

Ask ten boards what a COO does and you will get ten different answers — operations chief, deputy CEO, integrator, heir apparent. The title is genuinely variable, but the variability hides a constant: every real COO owns the system that turns the company’s promises into delivered work. Sales makes commitments; the COO owns the machinery that honours them — the flow from sale to delivery to cash, the quality that survives volume, the cadence by which decisions get made, and the numbers leadership actually trusts. Job descriptions differ by company; that operating mandate does not. Once you see the constant, the role stops being mysterious and starts being assessable.

The responsibilities follow from the mandate. A chief operating officer designs the operating model — who owns what, how work moves, where decisions sit. They run the operating cadence: the weekly review where commitments are checked and closed. They own the quality system, because at scale quality is a system property, not a personality trait. They build the measurement layer — a single source of truth the leadership team stops arguing with. And they translate strategy into capacity: the people, process and tooling that can actually carry next year’s plan. What changes by stage is proportion, not substance: at fifty people the COO installs; at five hundred, they govern.

I write this as an operator, not a theorist. Nineteen years inside operations, most recently as Senior Director, Business Excellence at Publicis Groupe — quality and delivery across 500+ clients, 2,000+ teams and more than USD 750 million in annual media spend, for brands including Disney, Samsung, Adobe and P&G. I have done this job at scale, and I now do it fractionally for companies between fifty and five hundred people. This guide reflects that vantage: the role as it looks from inside the operating seat rather than from a textbook — including the honest cases where a company does not need a COO at all.

In depth

What you need to know.

The operating mandate: what a COO actually owns

Strip the title back and the COO owns one thing: the operating system of the business — the connected machinery that converts a signed deal into delivered work and collected cash. That breaks into five owned layers. Flow: how work moves from sale through delivery to invoice, and where it queues. Quality: the standard the company delivers at volume, defined and enforced as a system rather than a hope. Cadence: the rhythm of reviews and decisions that keeps a hundred moving parts synchronised. Measurement: the small set of numbers, on one source of truth, that tells leadership the truth about the machine. And capacity: whether people, process and tooling can carry the growth the strategy assumes. Everything else a COO does — hiring, tooling, vendor calls, firefighting — is in service of those five layers.

COO roles and responsibilities, listed plainly

If you need the list for a job description, the responsibilities of a chief operating officer are these. Design and own the operating model — structure, ownership, decision rights. Translate strategy into an executable plan with named owners and dates. Run the operating cadence: weekly reviews that close decisions, monthly deep dives that correct course. Own cross-functional delivery — the handoffs between sales, delivery, finance and support where most value leaks. Define and govern the quality standard. Build the measurement layer: definitions, one source of truth, a scorecard leadership trusts. Own capacity planning and the operating cost base. Manage operational risk — the failure modes that could genuinely hurt the company. And develop operating leaders beneath them, so the system survives their absence. That last responsibility is the one that separates professionals from heroes.

The COO is defined by the CEO

The COO is the only C-suite role defined relative to another person. A CFO’s remit is roughly the same in any company; a COO’s remit is whatever the CEO cannot or should not carry — which is why the job varies so much, and why copying another company’s COO job description usually fails. In practice the pairing settles into a division: the CEO faces outward — capital, market, vision, the defining relationships — while the COO faces inward, running the machine that delivers what the outward face has promised. The common variants are all versions of this: the executor who scales what the founder invented; the change agent brought in to rebuild; the mentor who professionalises a young team; the partner who halves the load. Before hiring, a CEO should be able to state in one sentence which of these they need.

What a COO owns at 50, 150 and 500 people

At fifty people, the job is installation. The company still runs on the founder’s memory; the COO’s work is to move it onto systems — first process definitions, first honest numbers, first cadence — while keeping the speed that got everyone here. At a hundred and fifty, the job is enforcement and delegation: the layer of team leads is new and wobbly, quality starts depending on people who have never met the founder, and the COO’s value is making standards hold without founder charisma in the room. At five hundred, the job is governance: multiple entities, markets or lines, an operating review that spans them, and the discipline to run the machine through leaders rather than around them. The mandate never changes — flow, quality, cadence, measurement, capacity — but the verb does: install, then enforce, then govern.

COO versus CEO: where the boundary actually sits

The clean boundary is promise and delivery. The CEO decides what the company promises the world — strategy, positioning, capital, the bets. The COO owns whether the company can keep those promises at volume, and says so honestly before they are made. Trouble starts when the boundary blurs from either side. A CEO who keeps reaching into operations relitigates decisions the COO already closed, and the organisation learns to wait for the second opinion — which is slower than having no COO at all. A COO who starts making strategy quietly becomes a rival rather than a complement. The working test is decision rights: if both executives can name, without checking, which decisions are the COO’s to close alone, the pairing works. If every meaningful call still routes through the CEO, the company has a deputy, not a chief operating officer.

COO versus CFO, and the rest of the C-suite

The CFO measures the business; the COO runs the machine the measurements describe. They meet — deliberately — on working capital: billing cycles, collections, the cash that operations traps or releases. When I compressed a billing approval cycle from roughly two months to fifteen days across 75 entities, that was operating work with a finance-shaped result; the CFO reported the improvement, but the operating system produced it. Against a CRO or sales head, the COO owns everything after the signature. Against a VP of Operations, the difference is altitude: a VP runs a function well inside an operating model someone else designed; a COO designs the model, owns the cross-functional whole and answers to the board for it. Companies that promote a strong VP and expect a COO to appear often discover the difference expensively.

Myths about the COO job, retired

Myth one: the COO is always the number two and heir. Sometimes; more often the role is a complement, not a succession plan, and treating it as an anointing distorts hiring. Myth two: the COO owns the back office. The real job runs straight through revenue — the sale-to-delivery-to-cash flow is the front of the business, not the back. Myth three: every company needs one. Below roughly fifty people, a strong founder with good functional leads usually suffices; a premature COO adds a layer of management, not speed. Myth four: great COOs manage by presence — walking the floor, willing things done. At any scale worth the title, the job is systems: standards, cadence, measurement, decision rights. Presence is what you fall back on when the system does not exist. The best COOs make themselves progressively less necessary.

When a company needs a COO — and the fractional route

The signals are consistent. The founder has become the bottleneck — every decision queues behind one calendar. Quality wobbles under load: the work that won the first hundred clients is not surviving the next hundred. Growth is stalling on execution rather than demand. The leadership meeting reviews anecdotes because nobody trusts the numbers. Any two of those, sustained for a quarter, and the operating seat is empty whatever the org chart says. The choice is then full-time or fractional. A full-time COO fits when the operating agenda is permanent and the company can attract genuine calibre to a permanent seat. A fractional COO — a senior operator embedded one to three days a week — fits companies between fifty and five hundred people that need the judgement now, without the compensation, equity and mis-hire risk of a permanent executive.

Questions

Common questions.

A chief operating officer owns the system that turns the company’s promises into delivered work and collected cash — the flow from sale to delivery to invoice, the quality standard that holds at volume, the operating cadence that closes decisions, the measurement layer leadership trusts, and the capacity to carry next year’s plan. Titles and org charts vary widely by company; that operating mandate is the constant. If a COO job description cannot be traced back to it, the company is usually hiring a deputy or a department head, not a chief operating officer.

Eight recur everywhere: design the operating model, including decision rights; translate strategy into an executable, owned plan; run the operating cadence of weekly and monthly reviews; own cross-functional flow from sale to delivery to cash; define and govern the quality system; build the measurement layer on a single source of truth; plan capacity and the operating cost base; and manage operational risk. In founder-led companies a ninth matters as much as any of them: absorbing operational load from the founder, so the company stops queueing behind one person. The proportions shift with stage; the list does not.

The CEO faces outward and decides what the company promises — strategy, capital, market position, the defining relationships. The COO faces inward and owns whether those promises are kept at volume, and says so honestly before they are made. A useful test of a healthy pairing is decision rights: both executives should be able to name, without checking, the decisions the COO closes alone. When every meaningful call still routes through the CEO, the company has an operations manager with a grand title — and the CEO is still the real chief operating officer.

The CFO measures and finances the business; the COO runs the machine the numbers describe. Finance closes the books, manages capital and reports the truth; operations determines what that truth says. The two meet on working capital — billing, collections, the cash operations traps or releases — which is why a strong COO-CFO pair is worth so much. As one example of the overlap: compressing a billing approval cycle from roughly two months to fifteen days across 75 entities was operating work through and through; the CFO’s cash position simply inherited the result.

No. Below roughly fifty people, a capable founder with strong functional leads usually covers the ground, and an early COO adds management without adding speed. The role earns its cost when scale breaks improvisation: the founder becomes the bottleneck, quality wobbles under load, handoffs leak, and the numbers stop being trusted. From about fifty people onward those symptoms compound rather than resolve, and somewhere between fifty and five hundred the operating seat has to be filled deliberately — full-time if the agenda is permanent, fractionally if what you need is senior judgement at partial cadence.

The mandate is identical — flow, quality, cadence, measurement, capacity — but the verb changes with scale. In a startup or fifty-person company the COO installs: first processes, first honest numbers, first operating rhythm, often building alongside the team. At mid-size the COO enforces and delegates: standards must hold through a new layer of managers who never sat next to the founder. At five hundred or more the COO governs: entities, markets, an operating review that spans them, leaders developed to run the machine. A COO who is excellent at one altitude is not automatically excellent at another — probe for the stage you are actually at.

The best COOs share three habits. They think in systems — every recurring problem becomes a process, a standard or a decision right, never a repeated act of personal heroism. They measure honestly — few numbers, defined once, on one source of truth, reviewed on a cadence that closes decisions. And they transfer — they build leaders and playbooks so the operation runs without them, which is the opposite instinct of executives who make themselves indispensable. Résumés show titles; these habits show up in references and artefacts. Ask a candidate what they installed, what they measured, and what survived their exit.

Yes — with one condition: the mandate must be real. A fractional COO takes the same operating seat — owns processes, runs the cadence, answers for outcomes — at one to three days a week, which suits companies between fifty and five hundred people that need senior operating judgement without a permanent executive’s compensation, equity and mis-hire risk. What does not work is advice without ownership: a part-time attendee reviewing slides changes nothing. If the decision rights and the cadence are genuine, a fraction of the time does not mean a fraction of the authority.

The next step

A short conversation settles most of this — and a fixed-fee diagnostic settles the rest.