The Owner Who Kept Hiring: What Three Operations Managers in Two Years Actually Revealed

He was not hiring bad people.

In two years, a manufacturing client of mine cycled through three operations managers. Each one was qualified. Each one understood the role. Each one lasted less than eight months.

He blamed the first one for not being hands-on enough. He blamed the second for not understanding the industry. By the time the third left, he had started to wonder whether the role was the problem, or whether the business was.

It was the business.

The Pattern Behind the Revolving Door

This is a pattern I see more often than people want to admit. An owner grows a business to a point where they cannot run every function personally. They hire someone to take operations off their plate. The person starts well. Six months later, they are fighting the same fires the owner was fighting. And shortly after that, they are gone.

The reason is almost never what the exit interview says.

Capable people leave when they are set up to fail. And the most common way to set a capable person up to fail is to put them inside a business that has not been built to support the role you hired them for.

The systems are not connected. The data cannot be trusted. The information they need to make decisions is either missing, outdated, or locked inside the owner's head. So they adapt. They work around the gaps. And eventually they exhaust themselves keeping a fragile structure running, rather than doing the job they were hired to do.

You cannot hire your way out of an infrastructure problem. The role will keep failing until the foundation is fixed.

What the MAP Revealed

When I started working with this client, the first thing we did was walk the business. Not the org chart. The actual business. How work moved from one function to the next, where it slowed down, where it stopped, and where it had to route through the owner before it could continue.

What the MAP surfaced was not a people problem. It was four specific infrastructure failures.

First, the four core systems, quoting, scheduling, inventory, and billing, were not connected. A job would be quoted in one system, scheduled in another, tracked in a third, and invoiced in a fourth. No system talked to any other.

Second, there was no single source of truth for job status. A client asking where their order was required the owner to check three places and make a phone call. No ops manager could answer that question independently.

Third, decision ownership was undefined. Approvals that should have been automatic were routing to the owner by default, not because he had set it up that way, but because nobody had ever explicitly given the authority to anyone else.

Fourth, reporting was manual. The ops manager was spending four hours every month compiling a report that confirmed what the owner already knew. It was not informing decisions. It was confirming instinct.

None of these were the ops manager's fault. All of them made the ops manager's job impossible.

The BUILD: What We Connected and Why in That Order

The temptation in a situation like this is to fix everything at once. We did not do that.

We sequenced the BUILD around the two things that were costing the most: the owner's time and the ops manager's ability to answer a straight question.

The first connection was between quoting and scheduling. This was where the most manual transfer of information was happening. We built the integration so that a confirmed quote automatically created a scheduled job with all the relevant information in the right place.

The second connection was job status visibility. We built a single dashboard that pulled live status from all four systems. For the first time, anyone with access could answer a client question without making a phone call. The owner was removed from that loop completely.

The third change was decision ownership. We mapped every approval routing to the owner and asked a simple question: should this actually require him? In most cases the answer was no. We documented the criteria for each decision and assigned clear ownership to the ops function.

The reporting came last. Once the data was clean and connected, the report built itself. What had taken four hours every month took forty minutes and was more accurate than it had ever been.

The sequence mattered. Foundation first. Then the structures on top of it.

What Changed

The fourth ops manager started eight months ago. He is still there.

Not because he is exceptional, though he is capable. Because the business is now built to support the role.

He can answer a client question without calling the owner. He can see job status across all four functions from one screen. He can approve routine decisions without escalating. He produces a monthly report in under an hour that leadership can actually use.

The owner still gets called. But only for the things that genuinely require him. Strategic decisions. Unusual situations. Relationships he owns personally.

He took a week off in March. The business kept running.

A business that runs when the owner is there and stops when the owner leaves is not a business. It is a dependency.

The shift from integration layer to owner does not happen by hiring better. It happens by building better.

How to Recognise This in Your Own Business

The revolving ops hire is one version of this pattern. There are others.

The manager who is always firefighting. The team that works hard but cannot scale. The growth that keeps stalling at the same point. The owner who is involved in decisions they should have delegated two years ago.

All of them trace back to the same root cause. The business has been built around the owner's capability rather than around a system. And capability, no matter how good, cannot scale the way a system can.

The question to ask is not whether the people are good enough. The question is whether the business is built to let them do the job.

If the answer is not clearly yes, that is where to start.

Find out where your gap is. 5 questions, free:

Start Your Assessment -> assessment.sabrishchand.com/

Ready to get inside the engine room? Book an Operations Audit:

Book an Operations Audit -> intheraconsultinggroup.com/3-day-business-audit