When to Hire an Operations Manager (and What to Hand Them First)

The honest test for when to hire an operations manager is not how busy you feel. It is whether the work you would hand over already has a shape. Hire when decisions queue on you every day, when recurring responsibilities have no single owner, and when growth runs on heroics instead of capacity. Hire before that and you have added a salary to a business that still routes everything through you.

When to hire an operations manager: three signs it is a seat, not a favor

Most owners come at this backward. They feel underwater, they like somebody on the team, and a title gets invented to keep them. A seat is not a favor: it exists because work exists that nobody owns.

1. Decisions queue on you. Not questions, decisions. One electrical contractor described his company in a line: it is a decent place to work, but it could be aggravating because there is no structure, it is me, me, me.
2. Responsibilities float in a bucket. In a 55-person cleaning company, seven office people were one bucket labeled anyone-who-answers-the-phone, with scheduling, dispatch, sales, finance, and HR blurred into it while the org chart kept changing.
3. Growth runs on heroics. An executive coach at one contractor's board meeting named the ceiling: the company had grown with zero visibility, carried by the heroic efforts of talented people who burn out, get sick, or leave.

None of those three is about hours. The first two are structural, and a manager can fix them. If only the third is true, you are short of capacity, and scaling without hiring a huge team buys it cheaper than a leadership salary.

What an operations manager cannot fix

An operations manager cannot fix a process nobody wrote down. They can only run it from memory, the way you do, and then two people are improvising instead of one.

We watched this with a cleaning company COO who sat in many seats at once. Working operations, sales, and hiring on the same day left no time to build the systems the seat existed for, and her playbook grew bloated: three redundant versions of one process, nobody able to find anything. She called it cognitive overload: she starts one, gets pulled to operations, and never makes them cohesive.

Hiring a manager into an undocumented business does not remove a single point of failure, it creates a second one.

There is a quieter cost. One field services owner took payables back after a key person left and found 500 to 800 dollars leaking every week from skipped audits and missed deductions, up to 10,000 dollars a month by his own math. A new manager would have inherited that leak without knowing it existed.

Write the seat before you write the job post

The job post is the last step, not the first. Describe the work before you describe a person: a seat you cannot describe is one you cannot evaluate later.

1. List the recurring work. Every responsibility that repeats weekly, monthly, or once per job, in plain language.
2. Put today's name on each. Not the name you wish were there. The person who does it now, including you, several times over.
3. Circle the unowned. Anything with no name, or with three names, is the first draft of the seat.
4. Name what stays yours. Write it down deliberately, or it drifts back to you by accident.

If every responsibility on that list still has your name beside it, you are not ready to write the job post. You are ready to document, a different project with a different budget.

One cleaning company owner asked whether we needed her org chart, then answered herself: I am trying to build things based off our org chart, and that is not the way it is built. A chart shows reporting lines, not work, so the exercise starts from the work rather than the boxes.

Promote from inside or hire outside?

Promote from inside when somebody already holds the process knowledge and the room's trust. Hire outside when the seat's real work is work your company has never done, or nobody inside wants it.

The scoring we use for picking a system-building partner transfers cleanly here. Do they want to participate, will they schedule the time, are they influential enough to be a galvanizer, and are they a good example of the work done right? Title does not equal fit.

Promoting from inside has a cost nobody prices: you open a hole exactly where your most capable person sat, and that job is usually among the least documented in the building. Document the job they are leaving while you document yours, or you solve one dependency by creating another.

What to document before their first day

Two things, in this order: your job, and the decisions inside it. A job description written from memory will not survive contact with a Tuesday.

A founder of three companies put it plainly while planning his own handoff: there are a lot of things that I know that nobody knows but me, and I do not even know what I have told people and what I have not. That is the normal condition of anyone who built the thing. So we record practitioners doing the work instead of asking them to write it down, and here the practitioner is you, at 2 to 4 hours per process.

Start with the processes you touch every week, not the whole role, as in documenting your own job before you hand any of it over.

The first three things to hand over, in order

Pick the process that repeats most, not the one that annoys you, and hand it over in three moves.

1. Hand over the purpose. Why the process exists, what outcome it protects, and who it affects. If they cannot defend the why, they will not defend the process the first time somebody asks to skip a step.
2. Hand over the decision points. Every process has forks where the right answer depends on context. Name each fork and what the right call looks like, because undocumented forks are where processes break down.
3. Hand over the steps last. Screen by screen, click by click. Steps are the easiest part to transfer and the least valuable to transfer first.

Most owners run that order in reverse. They show the clicks, keep the judgment, then wonder why every fork still lands in their inbox. Expect the first runs to come back rougher than yours, which is the trade in handing off work when you have no time to train.

---

How do you tell in 90 days whether it worked?

You test it by leaving. One electrical contractor planned a two-week absence as a measurement instrument, and was clear-eyed about why: you may get some honest feedback when I am not expected to pop into your office.

The gate at each stage is the handover test: purpose, decision points, steps. Can they state the purpose of the processes they own, name the decision points without checking, and run the steps without asking? Set those checkpoints with a 30-60-90 day plan with the handoff built in.

The measure is not how much the operations manager is doing, it is how many decisions stopped coming to you. That is what decides whether you are getting out of day-to-day operations or just adding a layer between you and the work.

The failure mode nobody plans for: the quiet hire

The seat rarely fails loudly. It goes quiet. In one contracting business, a coordinator stopped sending proactive updates, projects stalled with nobody flagging them, and the owner ended up describing himself as his employee's personal assistant, running on reminders and pushing. It ran that way for years, tolerated because the company was not built for turnover.

The fix was not discipline. It was structure: a standing place where updates get posted on a schedule, so status is visible without the owner chasing it. Define what visible means in the seat during week one, in writing. At The Systems Effect we map role responsibilities across departments before anyone writes a job post, and that map is usually the first time an owner sees which responsibilities carry no name.

Then the harder discipline starts. A turnaround CEO described typing a long late-night reply telling a subordinate exactly how to do something, then deleting it and sending three words instead: whatever you think. That was the moment the employee started owning the work.

Before you write a line of a job post, write down the five decisions people interrupted you about this week and the rule you actually used for each. That list is the seat.

Frequently Asked Questions

When should a small business hire an operations manager?

Hire when decisions pile up on you daily, when recurring responsibilities have no single owner, and when growth is carried by the heroics of a few people. Those signals are structural, and a manager can fix them. Being tired is not one of them, because exhaustion is usually a capacity problem or a documentation problem wearing a staffing costume.

What is the difference between an operations manager and a COO?

In a small business the titles overlap enough that the honest difference is scope, not seniority. An operations manager owns the execution of processes that already exist. A COO owns the operating model itself: which processes exist, who owns them, and what gets built next. The trap is hiring a COO and then filling the calendar with execution, leaving no time to build a single system.

Should you hire an operations manager or fix your processes first?

Document first, at least the processes you personally run every week. A manager who inherits an undocumented process has to rebuild it from memory, so the knowledge ends up in two heads instead of one. You do not need a full library before the hire, just the recurring work you touch.

What should a new operations manager take over first?

Give them the process that repeats most often, handed over as purpose, then decision points, then steps. The purpose lets them defend the process, the decision points let them handle the forks without calling you, and the steps are the easy part. Owners who hand over steps and keep judgment get questions forever.

How do you know if an operations manager is working out?

Count decisions, not activity. At 90 days, the choices routing back to you should have dropped in the areas they own, and they should be able to state the purpose of those processes, name the decision points, and run the steps unaided. The cleanest test is your own absence: take a week off and see what waits for you.