Start a Conversation
Insights

What a COO Should Own in a Mid-Sized Company

Chief operating officer is the most loosely defined seat in the executive suite. Here's how to give it a real job.

Ask ten companies what their COO does and you'll get eleven answers. In one place the COO is the heir apparent, waiting for the CEO to retire. In another, the COO handles everything the CEO finds boring. In a third, it's an honorary title for a longtime employee who deserved a promotion when there was nowhere else to put them.

None of those is crazy, exactly. But none of them is a job. And a COO without a clear job tends to drift toward whatever is on fire, which is a fine way to spend a week and a terrible way to spend a career.

Start with the split

The cleanest way to define the role is to start with what the CEO keeps. In most mid-sized companies, the CEO owns direction: strategy, the biggest customers, capital, the board or the owners, and the tone at the top. The COO owns execution: turning that direction into work that gets done, reliably, at a cost the business can afford.

If you can't say where that line falls in your company, start there. Everything else depends on it.

What a COO should own

Here's a reasonable starting list for a company somewhere between a few dozen and a few hundred employees:

  • The operating plan. The yearly and quarterly goals for delivery, cost, and capacity, and the measures that show whether they're on track.
  • The operating leaders. Production, service, distribution, and purchasing report here, and often IT and HR too.
  • The handoffs between departments. Sales to operations, operations to billing, purchasing to production. If it falls between two teams, it belongs to the COO until someone else clearly owns it.
  • Capacity. Whether the business has the people, equipment, and process to deliver what sales is about to sell.
  • Process and systems. How the work flows and the tools that support it, chosen to fit the business and not the other way around.

What a COO shouldn't own

It's just as useful to write down what isn't in the role. A COO who is also the head of sales, the controller, and the office manager isn't an executive. They're a very tired person with a nice title.

As a rule, the COO shouldn't own the company's direction, its banking relationships, or the final word on the largest accounts. They should have a strong voice in all three, but the call belongs to the CEO.

Authority to match

A COO who owns execution has to be able to change how execution happens. That means real authority: to hire and move people in the operating functions, to change process, and to spend within a budget without the CEO's signature every time.

Without it, you've built a role that answers for results it can't influence. We've written about why accountability without authority doesn't work. Short version: it doesn't.

How you'll know it's working

Pick three or four outcomes for the first year and write them down before you hire. Good ones are specific enough that two reasonable people would agree on whether they happened:

  • On-time delivery above a set level, measured the same way every month.
  • Overtime or rework down by a set amount.
  • Finished work billed within a set number of days.
  • The CEO spending most of the week on direction instead of daily decisions.

That last one is the real test. If the CEO is still fielding every operational question a year in, the role hasn't taken hold, no matter what the org chart says.

The hire itself

Once the role is clear, the hire gets easier. You aren't looking for an impressive executive in general. You're looking for someone who has owned this kind of work, at this size, in a business that looks something like yours. A great COO from a company of ten thousand may struggle in a company of two hundred, where there's no layer of managers to carry out the plan.

A clear job won't guarantee a good hire. A vague one almost guarantees a frustrating one, for the company and for the COO.