How VPs of Operations in Discrete Manufacturing Build the Track Record That Reaches COO

The VP of Operations who advances to COO is not the one who ran operations the most efficiently last quarter. It is the one who transformed the operational cost structure and production reliability simultaneously, over multiple years, in a way the board can read as an EBITDA contribution.

The gap between those two descriptions is significant. The first is operational competence. The second is operational leadership at the executive scale. Boards and CEOs promote the second. The path from VP of Operations to COO is built on three things: a financial track record that is legible at board level, organizational capability that survived the tenure of specific individuals, and skills the COO role requires that the VP of Operations role only develops with deliberate effort.

This guide covers all three. It is written for VPs of Operations who are thinking about the COO path, as well as those who are new to a VP of Operations role and want to build the track record correctly from day one.

What the COO Track Record Actually Looks Like

The board conversation that produces a COO promotion is not "this person ran operations well." It is "this person improved the operational cost structure and production reliability of the enterprise simultaneously, and we can see the P&L impact."

Three specific track record elements support this narrative:

Measurable reduction in enterprise maintenance cost as a percent of revenue. This is the structural margin improvement that persists beyond any single year's budget exercise. A VP of Operations who moved the enterprise from 4.2% to 2.6% maintenance cost as a percent of revenue over three years delivered a structural margin improvement that compounds. This improvement is board-visible because it shows up in the P&L every year, not just in an operational report.

OEE improvement across sites, not just at one site. A single-site OEE improvement is a Plant Manager achievement. An enterprise-wide OEE improvement, from 71% average to 79% average across 12 sites, is a VP of Operations achievement. It demonstrates that the improvement was produced by a program, not by a specific plant team, and that the program scaled across different equipment, different products, and different management teams.

Production uptime record expressed in dollar terms. Not "we reduced unplanned downtime by 18%." The board language is: "We protected an estimated $[X] million in production value over 36 months by improving reliability across the enterprise. The majority of that protection came from converting reactive maintenance events to planned interventions, reducing emergency repair premiums and eliminating OEM penalty exposure." This framing connects operational outcomes to EBITDA in terms the board tracks.

The VP of Operations who has all three elements has a record that a board can evaluate as executive leadership. The one who has only operational performance numbers has a record that looks like management.

Five Skills That Differentiate COO-Track VPs of Operations

Skill 1: Enterprise operational financial modeling. The ability to build and defend a financial model connecting operational program decisions to EBITDA outcomes. This is the rarest skill among VP of Operations candidates and the most consistently cited by COOs as the credibility threshold. The model does not need to be complex. It needs to be defensible: built from actual operational data, validated by finance, and presented in CFO language. The VP who can walk a CFO through the three-layer financial case in the ROI article in this series, with their enterprise's actual numbers, has demonstrated this skill.

Skill 2: Board-level operational performance presentation. The ability to compress enterprise operational complexity into a four-slide narrative that a board can evaluate in 15 minutes. This is not a reporting skill. It is a synthesis skill. The board presentation that advances a VP of Operations is the one that opens with the financial exposure, presents the program investment against it, shows the three-year trajectory, and closes with a specific capital or organizational ask. Boards promote people they can visualize as COOs. The board presentation is the audition.

Skill 3: Cross-functional operational leadership. The VP of Operations who stays in operations is a strong VP of Operations. The VP of Operations who connects operational decisions to supply chain commitments, quality outcomes, and finance expectations has built the cross-functional fluency the COO role requires. In practice, this means translating reliability investment decisions into supply chain risk language for the supply chain team, into margin improvement language for finance, and into OEM relationship risk language for commercial leadership. The translation capacity is the skill.

Skill 4: M&A operational due diligence. COOs are increasingly involved in assessing acquisition targets for operational health. A VP of Operations who can evaluate a target's enterprise production value at risk, identify reliability liabilities that affect purchase price, and develop the integration plan has a capability that most COO candidates lack. This positions the VP of Operations as a strategic contributor to M&A processes, not just an operational executor, which is the right positioning for a COO candidate.

Skill 5: Organizational capability building. The COO manages through organization, not through personal operational expertise. The VP of Operations who demonstrates this by building teams, systems, and standards that produce consistent results across all sites regardless of who is managing each facility has already demonstrated COO-level organizational leadership. The evidence is the consistency of the track record across sites, not the performance of any individual site.

Building the Financial Track Record in Dollar Terms

Financial fluency is the primary career differentiator for VPs of Operations on the COO path. The ability to translate operational outcomes into dollar terms, consistently and at enterprise scale, is what separates the VPs who advance from those who plateau.

Here is the translation framework for the four most common operational metrics a VP of Operations manages:

Each of these translations requires one calculation: the dollar value of the operational improvement. The calculation is the financial modeling skill. The presentation of it in these terms is the board communication skill.

Practice recommendation: At the end of each quarter, take your operational performance report and translate every metric into its dollar consequence. Not for external reporting. For your own development. The VP of Operations who has done this exercise for 12 consecutive quarters is not guessing when the board asks about the financial impact of the reliability program. They have been calculating it consistently and can present it with confidence.

The annual financial narrative: Once per year, compile the full enterprise operational financial narrative: production value at risk at the start of the year, production value protected through the reliability program, maintenance cost as a percent of revenue trend, and CAPEX efficiency improvement from asset life extension decisions. This annual narrative is the track record document. Over three years, it tells the EBITDA story that advances a VP of Operations to COO.

Managing Upward: The Board and COO Relationship

The VP of Operations who advances to COO is the one the current COO and board are already treating as a COO candidate. Building that perception requires intentional management of the upward relationship.

The quarterly operational review presentation. This is the primary board visibility touchpoint for a VP of Operations. The presentation that builds COO credibility opens with the enterprise annual production value at risk trend (is the enterprise more or less exposed than last quarter?), presents the three operational KPIs in financial terms, and closes with one strategic initiative and its expected EBITDA impact. This structure signals strategic operational leadership, not operational reporting.

The CFO relationship. COOs work alongside CFOs on capital allocation, budget approval, and investor communication. The VP of Operations who builds a peer relationship with the CFO before the COO promotion conversation is removing a potential objection. The way to build this relationship is through the financial modeling skill: bring the CFO into the enterprise production value at risk calculation, ask them to validate the methodology, and present them with the three-layer investment case before it goes to the board. The CFO who has already endorsed the financial logic of your operational program is a natural advocate in the COO promotion discussion.

The CEO visibility point. Most VP of Operations roles have limited direct CEO visibility unless something goes wrong. Creating positive CEO visibility requires connecting operational decisions to the CEO's strategic priorities. If the CEO is focused on OEM relationship strength, present the JIT reliability track record in OEM scorecard terms. If the CEO is focused on EBITDA margin improvement, present the maintenance cost as a percent of revenue trajectory. Map your operational narrative to the CEO's strategic narrative and present it at the right moments: board prep, strategy offsites, and investor narrative discussions.

Building Organizational Capability Across Functions

The COO track record is not built by the VP of Operations personally. It is built by the organization the VP of Operations has constructed. The enterprise result is the proof of organizational capability.

Enterprise decision architecture. Design the operational decision framework so that Plant Directors can make the right call without escalating to the VP level. This means: clear escalation thresholds (which decisions require VP involvement, and which do not), a common data standard (Plant Directors making decisions from the same asset health and financial data), and a documented response protocol (when a Tier 1 asset health alert is generated, what happens, in what sequence, by whom). A VP of Operations who has built this architecture can be in a board meeting when a production issue arises at a plant and trust that the Plant Director is handling it correctly without VP guidance.

Cross-site knowledge transfer. The best-performing sites in the enterprise have practices, responses, and program decisions that have produced better outcomes. The VP of Operations who systematically identifies those practices and transfers them to underperforming sites is building organizational capability, not just site management. This is the standardization story: how do you take Site A's reliability performance and replicate it at Site G? The answer is a combination of common standards, common data, and structured knowledge transfer. The VP of Operations who can answer that question with a program, not an individual, has the COO-level organizational capability.

Succession depth. COO candidates are evaluated on whether the organization can continue to perform if they are promoted away from their current role. The VP of Operations who has developed Plant Directors who could step into the VP role, and who has built systems that produce consistent results without personal VP involvement, has already demonstrated organizational leadership at COO scale.

M&A Operational Due Diligence as a COO Differentiator

Most VP of Operations candidates are not involved in M&A until they become COO. The candidates who build M&A operational due diligence capability before the COO conversation stand out as strategically oriented, not just operationally competent.

The M&A operational assessment a COO performs has three components:

Production value at risk assessment. For an acquisition target, calculate the aggregate annual production value at risk using the same methodology as your internal enterprise calculation. What is the target's maintenance cost as a percent of revenue? How does their OEE variance compare to sector benchmarks? What is the estimated production value at risk from their current reliability program posture? This assessment identifies operational liabilities that affect purchase price and integration priority.

Asset health and CAPEX liability. A target with aging assets and a reactive maintenance program has hidden CAPEX liabilities: assets that will require replacement sooner than a time-based schedule predicts, because the maintenance program did not extend their life. Condition monitoring data on target assets, if available during due diligence, is the most accurate input to this assessment. In its absence, maintenance cost as a percent of revenue and OEE trend data provide a reasonable proxy.

Integration plan. The operational integration plan for a manufacturing acquisition is primarily a reliability program standardization plan: bringing the acquisition's maintenance practices, monitoring tools, and response protocols into alignment with the enterprise standard. The VP of Operations who has already executed enterprise standardization across their existing portfolio has a template. This is a COO differentiator.

The 30/60/90 Day Plan for a New VP of Operations Role

Whether you are new to a VP of Operations role or entering a new organization, the first 90 days establish the track record trajectory. The decisions made in this window determine whether you spend the next three years running operations or transforming them.

Days 1 to 30: Baseline the enterprise.

Calculate the aggregate production value at risk across all sites. This is the most important number you will produce in the first month. It tells you what the financial exposure is, which sites are most concentrated, and where the investment case for reliability improvement is strongest. Do this calculation before you attend a single site visit. You want to arrive at each site already knowing what the financial exposure looks like from above.

Identify the two or three sites most exposed to a major reliability event in the next 12 months. These are the sites running reactive programs on Tier 1 assets with no monitoring coverage. They are your highest-priority reliability investments. They are also your highest-priority board communication risk.

Map the enterprise maintenance cost as a percent of revenue variance. Which sites are at benchmark? Which are above 3.5%? What is the cost of the variance in dollar terms annually? This is the operational cost reduction opportunity that will appear in your track record.

Days 31 to 60: Establish the enterprise standard.

Set the reliability program standard that applies to all sites. This document establishes what Tier 1 assets are, what monitoring coverage is required, what the response protocol is when an alert is generated, and what the minimum planned maintenance execution standard is during changeover windows. It does not need to be implemented at all sites immediately. It needs to exist as the enterprise standard against which every site is measured.

Identify the condition monitoring investment that addresses the highest-exposure sites first. Structure it as an enterprise program proposal with the three-layer financial case. Take it to the CFO for methodology validation before it goes to the COO or board.

Days 61 to 90: Present the transformation plan.

The 90-day deliverable is a board-level three-layer financial case, site prioritization by exposure, expected year one outcomes, and a three-year EBITDA trajectory. This presentation establishes your operational leadership agenda for the full tenure. It signals that you are not running operations as they were handed to you. You are transforming them.

The VP of Operations who delivers this presentation at the 90-day mark has already demonstrated the COO track record capability. The next three years are about executing the plan and documenting the results.