From Plant Manager to Operations Director: The Jump Most People Misread

A plant manager runs the best site in the network. Safety is good, the team is stable, and the numbers hold through the peak. The obvious thing happens: they are given three sites and the title of Operations Director. Within a year, they are working longer hours than they ever did when running one plant, and the results across the three are worse than those of the one they left.

This is common enough that I would call it the default outcome rather than the exception, and it is almost never a competence problem.

Running one site is a job you can do with direct control. You can walk the floor. You know which line is struggling before the report tells you. When something breaks, you can be standing next to it in four minutes, and a great deal of your reputation was built on exactly that.

Running a network permanently removes that option. You cannot be in three places at once, so the work stops being intervention and becomes something else: setting a standard, deciding where to spend your limited attention, and building people who will do the fixing without you. The daily texture of the job has almost nothing in common with the one that earned you the promotion.

The cruel part is that the better you were at the first job, the more your instincts would mislead you in the second. Your method worked. Personally, it is natural to want to install it everywhere. That impulse is what turns a capable multi-site leader into an exhausted one who has effectively taken on three plant manager jobs and done none of them properly.

These are what I look for when a client asks me to find someone ready for a first multi-site role, and they are rarely accidental. If you are aiming at this step, these are worth being deliberate about now.

Evidence that you improved something you did not control.
Almost every plant manager can show results on their own site, where they have the authority. Far fewer can point to a measurable improvement somewhere they had no line authority at all: a sister site they helped recover, a shared function they influenced, a network-wide standard they wrote that other people adopted. That is the closest available proxy for the actual job, and it is the single most useful thing on a resume at this level.

A successor you built.
If you were promoted tomorrow, who would run your site, and did you develop it? Being irreplaceable feels like security and, from the outside, reads as a limitation. A business will hesitate to move someone whose departure creates a hole, and a hiring company will wonder whether you build capability or absorb it.

Capital literacy.
Have you written a capital request, defended it to skeptics, and then lived with the payback you promised? Multi-site leadership is largely about allocating finite capital across competing sites, each with a manager who believes their case is the most urgent. If you have never been on the requesting side of that conversation with real money on the line, you will be learning it in public.

Standing outside operations.
Have you ever won an argument with procurement, commercial, or finance without escalating to your boss? Network roles run on influence across functions you do not own. The plant manager who resolves everything by going up the chain of command is not building the muscle the next job requires.

The hardest instruction I give people making this step is to stop being the best troubleshooter in the building.

It is the skill that got you here, and it is genuinely valuable, which is what makes it difficult to put down. But every problem you personally solve at a site is a problem that the site's manager did not learn to solve, and you are now accountable for whether they can. Restraint is the competence, and it looks like doing less, which feels wrong for a long time before it starts working.

There is an honest constraint worth naming, because it stalls more careers at this step than any skill gap: most Operations Director roles cover several sites, and most of those sites are not near each other.

That means relocation, or substantial travel, or both, often at the stage of life where people have the least flexibility to offer either. I speak with strong operators regularly who are fully ready for the role and cannot take the version of it that is within reach where they live.

That is a legitimate choice and not a failure of ambition. It does mean being clear-eyed: if you will not move and will not travel, the realistic path is a large single site, a cluster of sites in one region, or a corporate functional role, and it is better to aim at those deliberately than to keep applying for national roles and reading the silence as a verdict on your capability.

Worth saying, because I speak to people in this position often, and they usually think they are the only one. If you made the jump recently and it feels like you are failing, the question to ask is not whether you are working hard enough. Which of the three sites have you been trying to run personally, and what would happen if you stopped?

If you would like a 30-minute conversation about your leadership pipeline or a specific gap, use the button below.