Hire an operations manager, or build the systems first?
Why the first operations hire so often lands back on your desk.
Hiring someone to run operations feels like the obvious move. You're buried, so you hire someone to dig you out.
Sometimes it works. Often it goes like this. The new hire spends the first months asking you how things are done, because the answers live in your head. Then they start making calls you'd have made differently. You step back in, and the work lands on your desk again, now with a salary attached.
Why the hire inherits the problem
An operations manager runs a system. If there isn't one, they have nothing to run. So they become you, minus everything you know: the person every question routes through, without the history to answer it.
Good people notice fast. Some leave. The ones who stay learn to wait for you. That's why hiring great people so often changes nothing.
When hiring first is the right call
When the work is already defined and volume is the problem. If the process exists, the numbers are tracked and every decision has an owner, a good operator multiplies it. Give them a system and they'll run it better than you do. Hand them chaos and they'll inherit it.
The hire that finally works usually doesn't win on talent. It lands on structure the earlier hires never had.
The test
Before you post the job, write the new hire's first week. What they'd own. Which decisions they could make without asking you. Which numbers they'd watch. Where they'd find the answer when something breaks.
If you can't write that week, the person you hire can't do it either. Every gap you hit is a system to build before the seat gets filled.
Want to know which systems your business is missing before you hire for them? The X-Ray shows where they are and what they're costing you.
Request your X-Ray. You keep the report either way.