For most of the twentieth century, the Chief Operating Officer kept the machine running while the CEO looked outward. Production, logistics, headcount, the plumbing of the business — the COO owned all of it so the CEO could sell the vision and court investors. That job still exists. But the version of the role that wins today is broader: the modern COO owns how strategy actually turns into results, how fast the company can change, and how it uses data to do both.

The shift matters because it changes what a good COO is measured on. The old standard was steadiness — did the trains run on time. The new standard adds a second question: did the organization move fast enough, and in the right direction, when the market moved first.

If you are stepping into the role or trying to define it, the practical takeaway is this. Being reliable is table stakes. The difference between an average COO and one the board trusts with succession is the ability to translate a strategy deck into a working operating model, then change that model without breaking it.

The role has always been "second in command" — but the reasons changed

The best way to understand the modern COO is to see how many different jobs the title has always covered. In their 2006 Harvard Business Review article "Second in Command," Nathan Bennett and Stephen Miles argued there is no single COO job description. Companies create the role for at least seven distinct reasons, and the reason shapes everything the COO actually does.

What has evolved is not this list — it is the mix. Twenty years ago most COO appointments leaned toward Executor and Other Half. Today far more are framed as Change Agent and Heir Apparent, because boards want the number two to prove they can lead transformation, not just administer it. If you are defining a COO role, name the archetype out loud: a Partner COO and an Executor COO need different authority and different metrics, and the fastest way to fail is to be hired as one and reviewed as another.

From operations manager to execution owner

The biggest change is scope. A traditional operations lead optimized the functions they were handed. A modern COO owns the connective tissue between strategy and delivery — the operating model itself.

Strong looks like this: the CEO commits to a goal in the boardroom, and within weeks it exists as a set of owned objectives, sequenced initiatives, clear decision rights, and a cadence to review them. Weak looks like a COO who runs excellent departments that are each pulling in a slightly different direction, so the strategy stalls not from bad execution but from no shared execution.

The practical tool here is disciplined goal-setting plus clear ownership. Pair a framework like OKRs (objectives and key results) with a RACI map (responsible, accountable, consulted, informed) so every priority has one accountable owner and a measurable result. A mid-sized firm rolling out a new product line, for example, can use OKRs to set the quarterly target and RACI to settle the recurring fight over who owns pricing, launch, and support before it becomes a turf war. Getting this right is the heart of operational excellence as a repeatable discipline rather than a slogan.

The technology and data mandate

Technology used to be the CIO's problem and the COO's inconvenience. Now it is central to the job, because most operational improvement runs through software, automation, and data.

The modern COO does not need to write code, but they do need to make good calls about where automation pays off and where it just adds fragility. Strong looks like a leader who can read a process, spot the repetitive high-volume steps, and decide which ones to automate first — then measure the result. Weak looks like buying platforms because competitors have them, then discovering nobody changed how they work, so the tool becomes expensive shelfware.

Data is the other half of this. A capable COO builds a small set of numbers that reflect how the business actually runs and reviews them on a fixed cadence, instead of drowning in dashboards nobody trusts. This is the practical core of running operations on data instead of anecdote, and it is also where the newer digital-first COO mandate lives — not in owning the tech, but in owning the outcomes the tech is supposed to produce.

Speed and adaptability: the agile operating model

The pandemic years taught a hard lesson: an operation optimized only for efficiency can be brittle. The modern COO is expected to build a company that adapts quickly without falling apart, which is a different design goal than pure cost reduction.

In practice this means shorter feedback loops, cross-functional teams that can move without a chain of sign-offs, and processes that scale up or down as demand shifts. Strong looks like a COO who can reopen, expand, or wind down a line of business in a controlled way — if you reopen a channel to 10% of traffic first, watch the numbers, then scale, you learn cheaply. Weak looks like an all-or-nothing operator who only knows one speed and treats every change as a fire drill.

Adaptability is inseparable from change management, because new operating models fail on the human side more often than the technical side. A structured approach — the Kotter change model, or simply a clear plan for managing organizational change without losing your people — is what separates a transformation that sticks from one that quietly reverts the moment attention moves elsewhere.

Sustainability and stakeholders as operating decisions

Environmental and social expectations used to sit in a separate corporate responsibility function. Increasingly they land on the COO's desk, because the decisions that move carbon, waste, and labor practices are operational: which suppliers you use, how you source materials, how you run facilities, how you report what you did.

Strong looks like a COO who treats sustainability as an operating constraint to design around — building it into supplier selection and process design so it improves resilience at the same time. Weak looks like a separate ESG report that has no connection to how the business is actually run. Building more sustainable operations works best when it is folded into the same efficiency and risk work the COO already owns, not bolted on as a compliance afterthought.

The CEO–COO partnership, redrawn

None of this works without a clear relationship at the top. The classic model was simple: CEO decides, COO delivers. The modern model is more of a genuine partnership, where the COO brings operational reality back into strategy so the plans are executable in the first place.

The clean version of this split is the "Visionary and Integrator" pairing from the EOS operating framework — one leader sets direction and holds the big relationships, the other makes the organization run and holds people accountable to the plan. Strong looks like a COO who can disagree in private, commit in public, and give the CEO honest operational truth even when it is unwelcome. Weak looks like a COO who either rubber-stamps everything or fights every decision. Getting this balance right is the whole game — see how the best CEO and COO pairs actually work together.

What the modern COO actually needs to be good at

The skill set has widened, but a few capabilities do most of the work: turning strategy into an operating plan, making technology and data decisions, leading change through people, and holding a partnership with the CEO under pressure. Notice that only one of those is "operations" in the traditional sense. The rest are leadership and judgment.

For someone climbing toward the role, this reframes the development path. Deep functional expertise gets you noticed, but breadth across finance, technology, and people is what makes you credible as a number two. If you are on that track, focus on the core capabilities every modern COO is expected to have and treat the manager-to-COO journey as a deliberate broadening exercise, not just a series of promotions.

Key takeaways

• The COO role has shifted from keeping operations running to owning how strategy gets executed, how fast the company can change, and how it uses data.
• There is no single COO job. Name the archetype — Executor, Change Agent, Partner, Heir Apparent — because it defines your authority, your metrics, and your relationship with the CEO.
• Modern COOs own the operating model, not just individual functions. OKRs plus RACI turn a strategy deck into owned, measurable work.
• Technology and data are central to the job, but the value is in the outcomes, not the tools. Automate the high-volume, repetitive steps first, then measure.
• Build for adaptability, not just efficiency. Shorter feedback loops and controlled, staged change beat one-speed operations.
• Sustainability and stakeholder decisions are operational decisions — design them into sourcing and process work, not a separate report.
• The strongest COOs win on judgment and partnership, not just functional depth.

Frequently asked questions

What is the difference between a traditional COO and a modern COO? A traditional COO focused on running existing operations efficiently — production, logistics, and headcount under the CEO's direction. A modern COO still does that but adds ownership of execution across the whole operating model, technology and data decisions, change leadership, and a genuine strategic partnership with the CEO. The bar moved from "keep things steady" to "keep things steady and move fast in the right direction." Is there one standard job description for a COO? No, and that is by design. As Bennett and Miles set out in their 2006 HBR article "Second in Command," companies create the role for different reasons — to execute the CEO's plan, to lead a turnaround, to mentor a new CEO, to complement the CEO's weaknesses, to test a successor, or to retain a key executive. The reason for the role shapes the actual work, so define it explicitly rather than assuming a universal template. Does a modern COO need to be technical? They need to be technically literate, not a technologist. The job is to make good decisions about where automation and data actually improve the business, judge vendor claims, and hold teams accountable for the outcomes technology is meant to deliver. You do not need to build the systems; you do need to know which processes are worth automating first and how to measure whether it worked. How is the modern CEO–COO relationship supposed to work? It works best as a partnership rather than a strict decide-and-deliver hierarchy. The CEO sets direction and owns the big external relationships; the COO makes the organization run and feeds operational reality back into strategy so the plans are executable. The healthiest versions allow honest private disagreement, full public alignment once a decision is made, and a clear split of who owns what. What metrics should a modern COO be judged on? The right metrics depend on the archetype, but most COOs are accountable for a small set that reflects how the business really runs — on-plan execution of priorities, operational efficiency, quality and customer satisfaction, and progress on major change initiatives. The trap is tracking dozens of dashboards nobody trusts; a focused scorecard reviewed on a fixed cadence beats sprawling reporting. How do I move from an operations manager to a COO? Broaden deliberately. Deep functional expertise gets you noticed, but the number-two role rewards breadth across finance, technology, change, and people, plus the judgment to hold a partnership with the CEO under pressure. Treat the path as a series of stretch assignments that widen your scope — leading a cross-functional initiative, owning a turnaround, or running a transformation — rather than waiting for a title to confer the skills.