Your first ops hire: scope it in a page, not a personality.

A good hire is not a person. It is a durable answer to a specific problem you would rather not be solving yourself.

Most first ops hires go wrong in roughly the same way. The owner describes the role as a person — someone who “can just get things done,” or is “a real rockstar,” or “fits the culture.” The job ad goes out written in that register. Someone delightful is interviewed. The offer is extended on chemistry. Six months later the problem the role was supposed to solve is still on the owner’s plate — usually because the role was never properly defined in the first place. It was described, not defined.

This is not a rare pattern. Gallup’s research on management talent — widely cited and still largely true — found that companies pick the wrong candidate for manager-level roles 82 percent of the time. Not because candidates are bad. Because hiring tends to be built around personality and tenure rather than the outcomes the role is meant to deliver.

The fix is not a personality test. The fix is a scorecard. One page. Written before the job ad.

Where most owners get this wrong

The first mistake is hiring the title, not the work. Owners picture the first big operational hire as a COO. In almost every case at the 5-to-50-person scale, the role that actually stabilizes the business is an Operations Manager — someone to document processes, run daily operations, and take fires off the owner’s plate. A COO is a later hire, usually triggered by geographic expansion or by the owner stepping fully away from the running of the business. SCORE’s guidance on first hires lines up cleanly with what I see inside owner-operated firms: stabilize first, scale later.

Hiring a COO-title person to do ops-manager-scope work creates its own failure mode. The person you hired expects span of control the organization cannot yet give them. The role you needed stays undone.

The second mistake is writing the job ad before the problem. Owners sit down to write a job ad and immediately reach for responsibilities: oversee operations, manage vendors, lead team. None of those sentences describe a problem. They describe activity. A role defined by activity is nearly impossible to measure in 90 days — because activity is easy, and the outcome the role was meant to produce is unmeasured.

Before you write the job ad, write the problem. One paragraph. The three decisions this role removes from your plate. If you cannot write it in one paragraph, you are not ready to hire. What you have is a wish, not a role.

The third mistake is hiring for “culture fit.” Culture fit is usually a shorthand for “I can imagine having lunch with this person.” That is a fine thing to check and a terrible thing to hire on. It is the phrase most often uttered right before the 82 percent miss happens. I watched it happen at the design studio I helped run: a delightful hire, great over lunch, who could not take a single recurring decision off the founder’s plate by day sixty. I will not say never check it. I will say check it last, after the scorecard has been met. Not first.

The scorecard — one page, written before anything else

A scorecard is not a job description. A job description is a list of tasks. A scorecard describes what done well looks like. Geoff Smart and Randy Street codified this in Who: The A Method for Hiring — three parts: the mission, the outcomes, and the competencies. I adapt theirs slightly for owner-operators. The version I hand clients fits on one page and reads like this:

The sections are in that order on purpose.

The problem comes first because the role is a durable answer to the problem — not a list of activities that happen near it. The mission comes next because the mission is how the problem gets solved in one line. The outcomes come third because they are how you will know, in 90 days, whether the problem got solved. The competencies come fourth because you can teach competencies — you cannot teach a misaligned problem.

And the anti-pattern — the one paragraph describing what the role is not — is the quietest and most useful part of the whole page. Half the “we didn’t work out” stories I hear would have been prevented by a written sentence on day one about what the role was not supposed to do.

The 30-60-90 — measured against owner time, not ramp velocity

Every 30-60-90 I have seen at the owner-operator scale measures the wrong thing. It measures the hire — how fast they are ramping, how many people they have met, how much of the product they can explain.

Measure the owner. Outcomes, not tasks. The 30-60-90 measures the gap that closes, not the ramp that fills.

If the scorecard is honest, the right metric is how much time the owner has reclaimed by day 90. Not approximately. Actually. Track it. The calendar on day 90 should look visibly different from the calendar on day 1. If it does not, the hire has not done its job — even if the hire is delightful.

AIHR’s template library has the general structure if you want a starting point. The piece above is my adaptation — outcomes, not tasks; owner hours, not hire ramp. Both versions share the core insight that each 30-day window has a different purpose. The first is about learning. The second is about taking over. The third is about owning.

The real cost of getting this wrong

The Work Institute’s turnover research puts the average cost of a departure at 33 percent of annual salary, rising to 200 percent for senior or specialized roles. The direct costs — recruitment, training, replacement — are about 11 percent of that. The remaining 22 percent is hidden: productivity loss, team drag, institutional memory walking out the door. Nearly one in three new hires leaves within the first year.

What the data does not say, but I will: the scorecard does not just help you hire better. It helps you exit faster when the hire is wrong. When the 30-60-90 is measurable and the scorecard is written, you will know by day 60 whether the hire is going to take. You can course-correct cleanly, or part ways cleanly, with evidence in hand on both sides. Most owner-operators I work with wait too long on a bad hire because there was nothing written down to point at. The scorecard is that written thing.

Edge cases

“I cannot write the five outcomes yet — I don’t know the role well enough.” Good. That is the right answer. Spend two weeks writing the problem first. Talk it through with a peer. Outcomes will follow from the problem. If they do not, you do not have a role yet — you have a wish.

“My hire did great at 30 days and faded at 60.” Normal. Days 31–60 is where the scorecard earns its keep. It is also where most owners quietly abandon the scorecard because the hire is likable — which is exactly how an 82 percent miss rate gets made.

“I want a COO, not a manager.” Very rarely the right first hire at the 5-to-50-person scale. Start with an Operations Manager. If the business outgrows the role, promote or replace later — with a scorecard for that seat too.

“What if the 30-60-90 does not clear?” You have clean, written evidence that the agreement was not met. That is the quiet gift of the scorecard. You know when to act, and you can act kindly because the agreement was clear from day one.

What to read next

For the canonical text on scorecards and the A Method, Who by Geoff Smart and Randy Street. The excerpt on the author’s site is a good introduction.

For a small-business-appropriate walk-through of first hires and where to put them in the sequence, SCORE’s guide to the first ten.

For the Gallup research on managerial talent, read the original piece. Not for strategy — for a calibration of expectations going in.

---

A good hire is a durable answer to a specific problem. Write the problem first. Write the scorecard before the job ad. Measure the hire against the owner’s calendar, not the hire’s enthusiasm. The personality screen comes last.

Scorecard before resume. Outcomes, not tasks.

— Priya