The first operations hire is the one most owners get wrong.
Not because they pick a bad person. Because they hire before they know what the job is, hand over the title without the authority, and then wonder why nothing changed.
I look at owner-run companies for a living, both as a consultant and as someone who wants to buy and run one. This is how I'd approach that first hire, and how I'd judge it after 90 days. It's a point of view, not a study. Treat it that way.
First, decide if you have an operations problem or a sales problem
An ops manager fixes work that is happening badly. They can't fix work that isn't coming in.
If the phone is quiet, hire for demand. If the phone is ringing and jobs are late, quotes go out slowly, crews show up without the right parts and you personally are the dispatcher, the estimator and the complaint desk, that's an operations problem.
A quick test: write down the last five things that went wrong this month. If four of them trace back to "nobody owned it" or "it depended on me being there," you're ready. If they trace back to "we didn't have enough customers," you're not.
What the role actually is
"Operations manager" means something different in every company. In a small business it usually bundles four jobs:
- Scheduling and dispatch. Who is where, with what, and when.
- Quality and follow-through. The job gets finished, checked and closed out, and the customer hears back.
- People management. Hiring, training, correcting and the daily problems that crew leads shouldn't have to carry to the owner.
- The numbers. Job costing, margin by job type, overtime, callbacks and what a late job really costs.
If you can't say which of these you want the person to own first, you're not ready to write the posting. Pick one or two. The rest comes later.
The best description I know of this seat is the "integrator" idea: someone who runs the business day to day so the owner can work on direction. You don't need to adopt the vocabulary. You do need the underlying split. The owner decides where the company is going. The ops manager makes the Tuesday work.
Write the job down before you recruit
Most small business owners can't hand over what's in their head, because it was never on paper. That's the real obstacle to this hire, more than salary.
Before you post anything, spend two weeks writing down:
- What you do every week that only you do. Approvals, pricing exceptions, customer escalations, vendor calls.
- Which of those need your judgment and which only need your information. Information can be handed off. Judgment needs rules you're willing to state.
- What "done" looks like on a normal job. Not the ideal. The normal.
This is the same exercise I describe in how to systemize a small business. If you skip it, your new hire spends six months reverse-engineering you, and you will judge them against standards they never saw.
Give authority with the title
A title with no authority is a trap for both of you.
Decide in writing what they can do without asking: spend up to a set amount, reschedule crews, send someone home, reprice a change order within a range, fire a vendor. And what still comes to you. Put dollar figures on it.
The failure I see over and over: the owner hires someone, then overrules them in front of the crew within the first month. The crew learns who actually decides. The new manager learns it too, usually faster. You can overrule in private. You can't do it on the job site and expect to keep the hire.
What to look for
I'd weight these, roughly in this order:
- Has run a messy process end to end. Not "managed a team." Ask them to walk you through a job that went sideways and what they changed afterward.
- Writes things down. Ask what they did in the first 30 days of their last role. People who document answer concretely.
- Is comfortable telling you no. In an interview, give them a realistic scenario where your instinct is wrong and watch.
- Respects the trade, even if they don't know it. A manager who needs to prove they're smarter than the crew will lose the crew.
Industry experience matters less than people think. Someone who has run field work, a warehouse, a clinic schedule or a fleet can learn your vocabulary in a few months. Someone who can't hold a process together won't learn that from you.
The first 90 days
I'd structure it in three stages, and I'd tell the hire this plan on day one.
Days 1 to 30: listen and shadow. Ride along, sit in on calls, read the paperwork. No major changes, except stopping obvious bleeding. The output is a written list of what's broken, ranked.
Days 31 to 60: fix two things. Not ten. Two, chosen together with you, each with a number attached. Late jobs per week. Days from completed work to invoice. Callbacks. Pick things you can already measure or can start measuring now.
Days 61 to 90: hand off one of your own jobs. Pick something you currently do every week, and watch it move off your plate. If you still do all the same things at day 90, the hire isn't working, whatever else is true.
How to tell it's working
You don't need a dashboard. Four questions, asked on day 90:
- What did I stop doing? If the answer is nothing, that's the answer.
- Did the two chosen numbers move? Even a little, in the right direction, is a good sign.
- Does the crew bring problems to them first? That means authority is real.
- Could they run a week while I'm away? Test it. A short, planned absence is the cheapest audit you'll ever run.
If the answers are mostly yes, the hire is paying for itself, because your time is now going to the work only you can do. If they're mostly no, the cause is usually one of three things: the job was never defined, the authority was never given, or the person was the wrong fit. Figure out which before you replace anyone, or you'll repeat it.
When not to hire yet
Two situations where I'd wait:
- The business only works because of you. If customers call your cell and ask for you by name, an ops manager can't fix that. See what to do about an owner-dependent business.
- There's no margin to carry the salary. The hire has to free up or recover more than they cost. If you can't point to where that money comes from, fix pricing and job costing first, then hire.
If the business is heading toward a sale or an owner's retirement, this hire is also the first piece of the succession plan, and a buyer will value it. I wrote about that side in what happens when an owner retires with no succession plan.
Where I can help
If you're trying to work out what the role should be, or whether you need an ops hire at all, Di-Hy does that kind of outside read for owners. Start with the free audit.
FAQ
When should a small business hire an operations manager?
When work is coming in but delivery is inconsistent and the owner is the bottleneck for scheduling, quality or approvals. If the real shortage is customers, hire for demand first.
What does an operations manager do in a small business?
Usually scheduling and dispatch, quality and follow-through, people management and job-level numbers. Pick one or two to own first rather than handing over everything at once.
How do you know if your first ops hire is working?
Check what you stopped doing, whether two agreed numbers improved, whether the crew brings problems to them first, and whether they can run a week without you.
Should the first operations hire come from your industry?
It helps but isn't required. Someone who has run a messy process end to end in a related field usually beats a specialist who can't document or delegate.