Book a walk-through

The ops hire I made 18 months too early (and the $68K it cost)

A negative case study: why hiring an operations manager into an undocumented business multiplies chaos instead of fixing it, with the real numbers and the sequencing rule we extracted from the wreckage.

Zack PetroccaOrigin, the right hand most owners never had · 2 min read
In this article
  1. What actually happened
  2. The accounting
  3. The sequencing rule we extracted
  4. If you’re about to make this hire

Consultants love telling you what worked. Here’s what didn’t.

In the middle of scaling the team, I hired an operations manager to “take things off my plate.” Smart person, real experience, good references. Eighteen months and roughly $68,000 in fully-loaded cost later, we parted ways, and almost none of the operational weight had left my plate.

The failure wasn’t theirs. It was mine, and it was structural.

What actually happened

I hired an ops manager into a business with nothing written down about how it ran. No documented processes, no defined meeting rhythm, no scoreboard, no role clarity beyond “help with ops.”

So every decision still routed through me, now with an extra hop. My tribal knowledge didn’t transfer; it got interpreted, and every interpretation drifted. Within months I was managing the person managing the chaos, which is strictly worse than managing the chaos.

The kicker: they spent most of their time building ad-hoc processes (badly documented, tool-scattered, half-adopted) because I’d effectively outsourced designing the processes to a person whose job should have been running them. Those are different jobs.

The accounting

  • ~$60K in salary and costs over 18 months
  • ~$8K in tools bought for workflows that never stabilized
  • Unmeasured but real: my time managing the role, the team’s whiplash from process churn, and the year we didn’t build the actual infrastructure because “we hired someone for ops”

The last line is the expensive one. The hire didn’t just fail. It deferred the fix.

The sequencing rule we extracted

Processes before staff. An operations hire runs and improves written processes; they cannot conjure them from an owner’s head. If the business isn’t documented, an ops manager inherits your chaos at a monthly salary.

The sequence that works, and the one we now set up with clients:

  1. Purpose first: define the seats and what “great” means in each (the one-page operating vision), including the ops seat you’ll eventually fill.
  2. People second: put the seat on the Ownership Map with a named outcome, and run the 3C Check (Clarity, Commitment, Capability) on the role before anyone is in it (write the role before you hire).
  3. Process third: document the core processes yourself; badly is fine. V1 SOPs beat perfect tribal knowledge (the one-page SOP template).
  4. Rhythm fourth: a weekly cadence where the new hire will live.
  5. Then hire, into documented processes, with a scorecard, owning execution from day one.

When we re-hired the role two years later, into a documented business, the ramp took three weeks instead of never, and my plate actually got lighter.

If you’re about to make this hire

Take the Origin Score first: twenty-seven questions, about five minutes, and it shows where your business is narrowest right now. If that is process, the honest move is a quarter of writing processes down before the job post goes up, whether that’s on your own inside the Inner Circle or with us through our services. It’s a fraction of $68K. I checked.

Questions this usually raises

When should a small business hire an operations manager?
Short answer

After the business has written processes for them to run. The sequence is purpose, people, process, rhythm, then the hire: define the seat, put it on the Ownership Map, document the core processes yourself, set a weekly cadence, and only then post the job.

Why do operations manager hires fail?
Short answer

Because they get hired into a business with no documented processes, no meeting rhythm, no scoreboard, and no role clarity. Every decision still routes through the owner with an extra hop, and the ops hire ends up designing processes instead of running them. In this case it cost roughly $68,000 over 18 months and deferred the real fix.

What is the difference between designing the processes and running them?
Short answer

An operations hire runs and improves written processes; they cannot conjure them from an owner's head. Deciding the seats, documenting the processes, and setting the cadence is design work, and it has to come first. Badly documented V1 processes are fine; they beat perfect tribal knowledge.

What should I do before posting an ops manager job?
Short answer

Take the Origin Score: twenty-seven questions, about five minutes, and it shows where your business is narrowest right now. If that is process, spend a quarter writing your processes down before the job post goes up, either on your own inside the Inner Circle or with us. When the role was re-hired into documented processes, the ramp took three weeks.

The System Drop

One thing to put to work, every week.

A short email with one setup, the steps, and the prompt or template to do it. Plus the news that changes how you run the business.

Step 1 of 2

More in Your team
When you're ready

When you'd rather we build it with you.

Most owners start here. When you want a right hand to build it with you, start with a walk-through. We walk your business with you and find the priority that will do the most for it.

“I went from an independent contractor to a business owner.”

$7.3M to ~$11M in sales

Beau P.Real Estate Team Leader