VP of Operations to COO: The Horizon Jump That Fails

The VP of Operations Who Can't Become COO: The Horizon Jump Nobody Sees Coming

She ran operations flawlessly for five years. Every KPI was showing green. Every process tight.

By month four as COO, she was underwater. Not in operations. In everything.

Navigating ambiguity. Managing cross-functional politics. Serving as the CEO's strategic partner on decisions that had no playbook and no KPI.

The board was confused. She'd been excellent. Now she was struggling. By month ten, they were discussing whether the promotion had been a mistake.

It wasn't a mistake about who she was. It was a mistake about what the job required.

Two Roles That Share a Name

On the org chart, it looks like a step up. In reality, it's a different job.

Both touch operational domains. Both manage teams that build and run systems. The title progression seems natural.

This is the largest horizon jump in most organizations. And the least understood. Because nothing in the VP of Ops role trains you for it.

Larger than VP of Sales to CRO. Larger than VP of Engineering to CTO. Because while those transitions expand the scope within a defined function, the VP of Ops-to-COO transition fundamentally changes what the job is.

The VP of Ops improves systems. The COO decides which systems should exist.

One operates inside the machine. The other redesigns it.

The VP of Ops asks: "How do we make this work better?" The COO asks: "Should this exist at all?"

That difference sounds subtle on paper. In practice, it's the gap where most promotions fail.

The Three Capabilities That Don't Transfer

Ambiguity Tolerance

A great VP of Ops needs clarity to perform. Define the objective, establish the metrics, set the timeline, and they will execute relentlessly. This is a genuine strength.

A COO rarely gets it.

The CEO says, "Our margins are thinning and I'm not sure why." There is no process for this. No SOP. No dashboard that gives the answer. The COO needs to investigate across functions — pricing, sales mix, supply chain costs, headcount allocation — and synthesize an answer from incomplete information spread across domains they may not have operated in before.

The VP executes defined problems. The COO defines undefined ones.

The VP of Ops, promoted to COO and encountering their first truly ambiguous problem, often responds by trying to create structure around it. They build a process for diagnosing margin issues. They create a dashboard. They schedule recurring meetings.

They try to build structure before forming judgment.

These are VP of Ops solutions applied to a COO problem. The structure helps, but it doesn't replace the judgment required to operate when the structure doesn't yet exist.

Cross-Functional Authority Without Functional Ownership

The VP of Operations has clear authority within their function. The supply chain, logistics, and production teams report to the VP of Ops, who makes decisions about how these teams operate.

The COO owns problems nobody owns.

When the COO identifies a problem at the intersection of sales, product, and operations, they can't simply direct the VP of Sales and the VP of Product to change course. They need to build alignment, manage competing priorities, and navigate the politics of functional leaders who view the COO's involvement as either helpful or intrusive.

Authority shifts from control to persuasion.

The VP of Ops who earned credibility through operational results discovers that those results don't automatically translate into influence over peers who run their own functions. The CRO doesn't defer to the COO because the COO fixed the supply chain. The CRO defers to the COO when the COO demonstrates an understanding of revenue dynamics and proposes solutions that serve both functions.

Results don't grant influence. Relevance does.

The VP of Ops who can't make this shift — from directing their own teams to influencing peers they don't- gets stuck. They either avoid cross-functional problems (ceding the territory that defines the COO role) or try to direct other functions (creating turf conflicts that erode their standing).

Strategic Partnership With the CEO

The VP reports. The COO interprets.

The VP of Operations interacts with the CEO through updates. Operational performance review. Project status. Risk flags. The relationship is structured around reporting.

The COO interacts with the CEO as a thinking partner. The CEO shares half-formed ideas and expects the COO to pressure-test them. The CEO raises concerns that don't have a functional home and expects the COO to take ownership.

The CEO doesn't need another operator. They need someone who sees what they don't.

This requires a different kind of conversation. The VP of Ops who updates the CEO on fulfillment metrics is operating at one altitude. The COO who tells the CEO, "I think our organizational structure is creating a bottleneck between product and sales, and here's what I'd change," is operating at a fundamentally different level.

The altitude shift isn't about intelligence or capability. It's about how the person has been trained to think. Five years of optimizing systems trains you to see the business through the lens of operational execution. The COO needs to see through organizational design, strategic prioritization, and leadership dynamics,  domains the VP of Ops was rarely asked to enter.

The Signals That Distinguish Readiness

Those who made the jump were already operating there.

They solve problems no one assigned them. The VP of Ops who voluntarily addresses the disconnect between sales commitments and operational capacity, rather than simply escalating it, demonstrates cross-functional thinking. They're choosing to own the problem.

They challenge the CEO without waiting for permission. The VP of Ops who tells the CEO, "You're asking me to optimize a process that shouldn't exist. Here's what I'd replace it with," is thinking at the COO level. They're not just running the system. They're questioning it.

They talk about structure, not just execution. If their conversations with the CEO naturally move from "here's how the operation is performing" to "here's how the organization is structured and why that structure is creating problems," they're operating above their title.

They're comfortable speaking without data. The VP of Ops who can walk into a room, listen to a cross-functional debate they have no metrics on, and offer a perspective that moves the conversation forward,  that's ambiguity tolerance in action.

They're already slightly uncomfortable in their current role. The scope feels constraining. They're reaching into adjacent functions because the boundaries of their job feel arbitrary. That discomfort is a signal.

The F1 Parallel

In F1, this is the jump from race engineer to team principal.

The race engineer optimizes the car's performance within defined parameters, setup, strategy, tire management, and pit stop timing. They excel at making a defined system produce its best result.

The engineer optimizes the car. The principal runs the team.

The team principal operates at a different altitude entirely. They manage the intersection of engineering, commercial relationships, driver management, and organizational politics. They decide which problems get resources and which get deferred. They navigate FIA regulations, sponsors, and internal dynamics between departments that all believe their priorities should come first.

One wins laps. The other wins championships.

The best race engineers are extraordinary at their job. That doesn't make them ready to be team principal. The skills overlap, but the altitude is different.

The best engineers aren't ready. The ones already thinking beyond the car are.

The Pattern

This isn't a promotion. It's a role change disguised as one.

The skills that made them excellent at operations, process discipline, metric obsession, and system optimization have become necessary but insufficient. The new job demands capabilities they may never have been asked to develop: ambiguity tolerance, cross-functional influence, and strategic partnership with a CEO who needs a thinking partner, not an operations reporter.

The skills that got them there still matter. They just don't decide success anymore.

Some make the jump. They're the ones who were already operating above their title, solving problems nobody asked them to solve, challenging assumptions nobody expected them to challenge.

The rest discover that the promotion they earned through operational excellence leads to a role that measures a completely different kind of performance. And by the time everyone realizes the gap, the VP of Ops has been set up for a predictable, preventable failure.

The mistake isn't the person. It's assuming the next level is more of the same.

Charlie Solórzano is a Managing Partner at Alder Koten, a boutique executive search firm specializing in C-suite and board placements across the U.S. and Mexico markets. He advises founders, investors, and boards on leadership transitions using The Race Conditions Model™, a proprietary diagnostic framework built on the thesis that leadership success is determined by conditions, not credentials.