What does a COO do?

A COO (chief operating officer) is the senior executive responsible for how a company runs day to day: its operations, processes, systems, and the people who deliver the work.

In most companies the COO is the second-in-command and reports to the CEO. Where the CEO decides what the business should do, the COO makes sure it gets done, the same way every time, without every decision going back up the chain.

The role looks different in every company, because a good COO fills whatever operating gap the business has. That’s why the title alone tells you less than the job description.

Plenty of companies have someone doing the COO job without the title: a head of operations, a general manager, a long-time right hand. And plenty of small businesses have no one doing it at all, which usually means the owner is doing it by default, on top of everything else.

They build the processes the team follows. They put the tools in place and make sure they’re used. They set the rhythm: what gets reported, how often, and to whom. They hire and train the people who do the work. They fix what breaks before it reaches the owner. In practice, COO responsibilities usually fall into six areas:

• Operations: how the product or service gets delivered, from order or sale to finished work, on time and to standard.
• People and hiring: building the team that does the work, setting roles and expectations, and making sure managers can manage.
• Systems and process: the documented way work gets done, so it doesn’t depend on one person’s memory. That usually means SOPs your team actually uses.
• KPIs and reporting: the handful of numbers that show whether the business is running well, reviewed on a fixed weekly rhythm.
• Vendors: suppliers, contractors, software, and partners, chosen, managed, and held to what they promised.
• Cross-team execution: the handoffs between sales, delivery, finance, and support, where most work gets dropped.

A typical week has a rhythm to it. A COO reviews the numbers at the start of the week, runs the leadership or operations meeting, clears the decisions that would otherwise stall, and spends the rest of the time on whatever is breaking or about to. Some weeks that’s a hiring problem, some weeks a vendor, some weeks a process that buckled under more volume.

What a COO shouldn’t be doing is the work itself, every day. If the COO is the one shipping the orders or answering every escalation, the role has turned into another bottleneck.

What a COO focuses on changes as the business grows. Early on, the job is getting anything repeatable at all. Later, it’s getting the business to run without the owner. In a larger company, it’s running several teams that each have their own leaders, and making sure they pull in the same direction. Here’s how that usually looks:

Most owner-led businesses we work with sit in the middle row. The business has outgrown the way it’s run, but it’s still small enough that the owner is the glue holding it together.

The CEO owns direction: strategy, capital, and where the company is going. The COO owns day-to-day delivery: making sure the business runs the way the CEO intends, every day.

In a small business, the owner usually does both jobs. That works until the operations take up so much time that nobody is doing the CEO job.

When both roles are filled, the relationship matters more than the org chart. The best CEO and COO pairs agree on priorities, split the work cleanly, and back each other in front of the team. When they don’t, people learn to go around one of them, and the operating rhythm falls apart.

COOs tend to fall into a few types, depending on what the business needs from the role. Knowing which one you need saves you from hiring a great operator for a job that really calls for a change agent, or the other way around:

• The operator: runs the day-to-day machine so the CEO can focus outward. The most common type in owner-led businesses.
• The executor: brought in to carry out a specific strategy, like a new market, a new product line, or a turnaround.
• The partner or #2: works alongside the CEO as a true counterpart, often with complementary strengths.
• The change agent: leads a major change, such as rebuilding operations, integrating an acquisition, or preparing the business for growth or sale.

Many COOs move between these over time. The point is to be clear about which one you need now.

In a small business, it’s almost always the operator, sometimes with a bit of change agent at the start. The first job is getting the basics running without the owner; the bigger changes come once there’s a stable base to build on.

• Systems thinking: sees the business as connected processes, and fixes the cause instead of the symptom.
• Execution: gets things finished, not just started. Projects close.
• People leadership: hires well, sets clear expectations, and holds people to them without drama.
• Comfort with numbers: knows which numbers matter, reads them every week, and acts on what they show.
• Calm under pressure: when something breaks, fixes it first and finds out why second.
• Judgment about what not to do: says no to the tenth initiative so the first nine get done.

The best COOs have run operations themselves. They’ve felt what happens when a process breaks at volume, and they build for it.

Industry knowledge helps, but it matters less than people expect. How work moves through a business, how teams are run, and how numbers are tracked look much the same across product, service, and software companies.

The signs are usually obvious to the owner long before anyone says them out loud:

• The owner is the bottleneck. Decisions queue up on your desk, and work waits for you.
• Things break when the owner steps away. A week off means a week of problems when you get back.
• Handoffs get missed. Work falls between sales and delivery, or between people, and nobody notices until a customer does.
• Nobody owns the numbers. You find out about problems late, because no one is watching the right numbers every week.

If two or more of these are true, the business needs someone in the COO seat. The question is what shape that takes.

Waiting rarely makes it cheaper. The longer operations run through the owner, the more of the business lives in one person’s head, and the harder it is to hand over later. The best time to start building the systems is before the strain shows up in front of customers.

A full-time COO makes sense when the business has multiple teams, the work is complex enough to need someone in the seat every day, and the business can support the role. When you need the work done but aren’t ready for a full-time hire, a fractional COO can take a defined part of it, often building the systems a full-time COO will later run.

Our guide on how to find a fractional COO covers that path in detail, and our fractional COO services page explains how we work. If you have one problem to fix rather than a role to fill, operations consulting may be the better fit.

The COO runs day-to-day operations. They own the systems, the processes, and the delivery, so the work gets done without the owner in every decision.

A full-time COO makes sense when the work needs someone in the seat every day. A fractional engagement makes sense when you need it done, but not a full-time hire yet, and it often builds the systems the full-time hire will run.

We look at it simply: if one system or one process is stuck, someone can take it. If it’s the whole operation and the business is large enough, it’s time for a full-time hire.

Write down what’s stuck. If it’s one system or one process, it can be taken off your plate. If it’s the whole operation, it’s time to think about the COO seat.

If you want us to look at it, send it over. We’ll tell you what it would take.

Scope your project →