When to Hire an Operations Person: The Signals, and What the Role Actually Holds

An operations person is not another pair of hands for existing work but whoever holds the processes themselves: making sure things happen, that information is where it should be, and that whatever fell once does not fall again. The role justifies itself once the owner has become the bottleneck for everything that is not selling.

The five signals

The fifth is the economically critical one: when there is demand you cannot serve, the cost of not hiring exceeds the cost of hiring - and unlike the other four, it can be quantified in lost orders.

What the role actually covers

In a small business an operations person usually holds four things: the work queue - what came in, who is handling it, what is stuck; coordination between whoever sells and whoever delivers; control - that what was promised happened; and the processes - fixing what breaks rather than only firefighting.

What the role is not: a personal assistant, a meeting scheduler, or whoever does what nobody else wants. A role defined that way will be filled, but it will not solve the problem you hired for.

When it is too early

When the processes do not exist at all yet. An operations person arriving at a business where nothing is defined will spend months defining - which is legitimate, but you should know that is what you are buying. Businesses expecting immediate improvement and receiving two months of mapping feel disappointed, even though they got exactly what they needed.

So when the business is very small, it is sometimes better to start with processes rather than a person: map, assign ownership, and document - as covered in mapping business processes. It is cheaper, and it is also what lets the first operations hire be effective from week one.

When it is too late

When the business already depends entirely on one person who knows everything, and hiring becomes a months-long project because there is nothing to hand over. The clearest sign is being unable to explain to a newcomer how you work - not because it is complicated but because it is written nowhere.

In that state hiring itself becomes harder: the candidate enters a role with no definition, no documentation, and an expectation that they will work it out. A large share of first-year departures from such roles come from exactly that.

What should be ready before hiring

1. A role definition in five lines - what they are accountable for, not what they do.
2. Defined authority - what they decide without asking.
3. Three processes handed over in full.
4. One metric per process, so success is unambiguous.
5. Who covers when they are unavailable.

The second decides it. Defining the authority itself is covered in approval limits and controls, and without it the operations person becomes a pipe relaying requests to the owner - which leaves the bottleneck exactly where it was.

What the first three months look like

Month one: learning and documenting. By its end there should be a map of the three handed-over processes including the exceptions - which is already a result in itself.

Month two: starting to hold. They run the queue, flag what is stuck, and fix small things. This is when the things that used to fall should start disappearing.

Month three: improving. They propose a change to one process and implement it. If by the end of month three all their time still goes on firefighting, something in the definition did not work - usually the authority or the scope.

How do you avoid the role becoming a new bottleneck?

That is the most common failure after a successful hire: everything routes through the operations person, and they become exactly what the owner used to be. The difference is that now two people are waiting on each other.

What prevents it is defining the role as whoever ensures rather than whoever performs. When they handle every exception themselves, the team stops solving and starts forwarding; when they decide who handles it and check that it happened, operations distributes properly. The early sign is them being busy all day with no time to review the processes - meaning they have become a doer.

It is also worth checking after six months how much of their time goes on the three defined processes and how much on things added along the way. The answer is nearly always a surprise, and it is the opportunity to trim and return the role to where it is useful.

What happens to the owner after the hire

That question gets forgotten and it is decisive. Hiring an operations person is meant to free the owner's time - but only if they genuinely stop doing what was handed over. In practice many keep answering the same questions, approving the same things, and tracking the same tasks, simply out of habit.

The simple check is to look after two months at how many operational enquiries still reach them directly. If the number has not fallen meaningfully, the handover did not really happen - and that is usually not the new hire's fault. The same logic of genuine delegation is in who owns a process.

What completes it is the owner redirecting in person: when they are asked and pass it on rather than answering, the message travels faster than any announcement - and it is visibly their decision.

Sources

• How to improve business efficiency
• Israel Tax Authority - information for businesses