What Makes an Operations Executive Search Different

Most functions have a title that means roughly the same thing everywhere. A CFO owns the P&L, the close, and the banking relationships regardless of which company signs the paycheck. Operations does not have that stability, and the reason is structural rather than a naming problem: an operations org chart follows the physical footprint of the business — how many plants, how many shifts, how the distribution network is drawn — rather than a functional template that repeats from company to company. Two people can carry the exact same title and have done almost nothing in common.

That makes operations the function where the standard read of a resume travels worst. It’s also the center of gravity for the searches Cerna takes briefs for — COO, VP/Head/Director of Operations, Supply Chain, Logistics, and Manufacturing — which is why reconstructing scope claim by claim, with a source matters more here than in almost any other function. This is the specific version of that discipline for this set of roles: how to reconstruct scope when the title will not tell you, how to treat the regulated/unionized/capital-intensive constraint set as a question about transfer, and how to look one sector over before ruling a candidate out.

Why titles travel worst here

In most functions the title constrains the job enough to be a usable starting filter. Operations breaks that pattern because the org design is drawn around whatever the company’s physical footprint happens to be, not around a repeatable functional shape. A “VP Operations” at a single-site chemical plant and a “VP Operations” at a large multi-site consumer goods manufacturer hold the same words on a CV and almost nothing else in common — different span, different P&L authority, different skill entirely.

The title cannot do the filtering work it does in most other functions, so the search has to do more reconstruction before screening even starts.

Reconstructing multi-site P&L scope

The single most load-bearing reconstruction in an operations search is working out what the P&L actually was, because “ran operations” hides several very different jobs behind one phrase.

• Site count, and whether it moved. Did the footprint grow, shrink, or stay flat on this person’s watch? A network that expanded materially is a different job than one held flat.
• Consolidated or site-level. Did this person own one number across every site, or did each site GM own their own P&L with this person coordinating above it? Different jobs wearing the same title.
• What the P&L authority actually included. Capex sign-off, headcount authority, and working-capital ownership do not always travel together. A person can carry P&L language on a CV while only controlling part of it.
• Organic growth or acquisition rollup. Building a network from scratch and integrating someone else’s plants onto a shared system after an acquisition are different skills that both get described as “grew the operation.”
• Layers to the plant floor. Direct site GMs reporting in, or a regional layer in between? The coordination burden changes with every added layer.

Most of this does not sit on the resume. It comes from investor materials, plant announcements, trade-press coverage, and how the company describes its own footprint in its own filings — the same triangulation screening at executive level generally requires, applied to the facts an operations role turns on.

The constraint set as a transferability question

Regulated, unionized, and capital-intensive are the three axes that shape how an operations executive works day to day, more than the sector label does. The mistake is treating them as a label to match rather than a question about transfer.

Regulated. The question is not whether the sector carries a regulator’s name. It is whether the person has built and defended a compliance system under audit, or only operated inside one someone else already built. A resume that lists the right regime does not tell you which one you are looking at.

Unionized. Labor relations is a discrete, learned skill — contract negotiation cycles, grievance handling, running a shop floor under a collective agreement — not a byproduct of general operational strength. A candidate with an outstanding non-union record has, by definition, never exercised it. Not disqualifying on its own, but worth naming plainly rather than assuming operational strength simply carries over.

Capital-intensive. Asset-heavy businesses run on capex planning horizons, utilization discipline, and maintenance cycles that behave nothing like an asset-light operation’s. Strength at optimizing a network of leased fulfillment space does not automatically transfer to planning a multi-year capex cycle for owned manufacturing capacity, even when both carried the word “operations.”

None of the three is a pass/fail line. They are three separate questions about which skill the record actually shows was built, and folding them into one “has ops experience” verdict erases the distinction that decides whether the first year goes well.

Adjacent-sector mapping

Because the constraint set matters more than the industry label, the pool worth searching is often one sector over from where the brief’s industry keyword points — provided the operating constraints rhyme even when the products do not.

• Food and beverage processing and pharmaceutical manufacturing. Different end markets, but both run on batch-record discipline, sanitation audits, and traceability back to a specific lot.
• Contract logistics and high-volume e-commerce fulfillment. One owns the trucks and warehouses; the other typically leases the space. Asset ownership differs, but network design, peak-season throughput, and labor scheduling against volume swings are close enough to be worth a look.
• Utility-scale power generation and municipal water treatment. Different commodities, similar operating shape: regulated, capital-intensive, unionized in most markets, run against uptime rather than growth targets.

A pool assembled by searching the brief’s named industry alone will systematically miss operators who built the exact skill the role needs somewhere the industry keyword never points.

Where the usual proxies mislead

Revenue size without site count. A single-site chemical plant and a large multi-site consumer goods network can post the same revenue figure. The operational complexity behind that number is not remotely the same, and revenue alone does not distinguish them.

Headcount without depth. A large headcount spread thin across a few sites with mostly seasonal labor is a different coordination job than a smaller headcount organized into several real management layers. The raw number tells you neither.

Employer name as a stand-in for scope. A recognizable manufacturer’s name says nothing about whether the person ran one line or the whole network, and it is easy to let the name stand in for the answer.

Tenure length without direction of travel. Whether an operation grew, held steady, or was being wound down changes what the tenure actually demonstrates, and it rarely sits on the resume — it has to be pulled from the same sources as the P&L reconstruction itself.

None of this collapses into a single verdict. A candidate fluent in capital planning who has never worked under a collective agreement is a different candidate from one who is neither, and a single “operations experience: yes” line cannot hold both facts at once. Evaluating each requirement on its own, with a source attached to what is confirmed, is what keeps that distinction visible instead of averaging it away.

Related reading: what private equity ownership changes, the in-the-room version of this argument, what COOs actually earn, how to screen executive candidates, how executive search researchers actually find candidates, what a good executive search shortlist contains, the research bottleneck at boutique executive search firms, and what a retained executive search firm does.