The hard part of hiring starts before the hire.

Everyone's asking the wrong question

When this happens twice, the conclusion owners usually draw is that they picked wrong. So the next search gets more rigorous. More interviews, a better recruiter, a longer look at the resume, more reference calls into whether this person really did build that pipeline.

That's answering "how do we hire the right person," and it's the wrong question to lead with.

Hiring the right person gets a lot easier once you know exactly what you need them to do. Most of the work sits there, before the job post ever goes up.

Shift it to "how do we win when we hire" and the whole thing changes shape. You're no longer searching for somebody who will arrive and figure out what winning means around here. You're hiring against a definition you already own.

Where it actually breaks

Look again at the friction in the middle of that arc, because that's the part everyone misreads as a personality problem.

A new leader walks into an undefined job and does the only thing they can do. They invent a direction. It might be a good one, and it's usually the direction that worked at their last company. But it's theirs, not yours, so every review of it becomes a referendum on whether the owners still like the plan, rather than a measurement of whether the plan is working.

Six months of that and both sides feel it. The owners feel like the hire went off script. The hire feels like there was never a script. Both are right.

This is the same failure we wrote about in the people, process, technology piece. A capable person put on top of an unstable layer doesn't stabilize it. They just become the next thing that gets replaced when the number stays flat.

Hire into structure, not into a gap

So what do you actually do? You define the role and the expectations, and then you hire to fill them, in that order.

It's one thing to hire somebody who has built huge pipeline numbers somewhere else. It's an entirely different thing to design how pipeline gets built in your company, with your offer, in front of your buyers, and then agree with that person on how they're going to hit it.

Hiring into a structure where the expectations are defined takes the guesswork out for both sides. Everybody starts on the same page, and disagreement surfaces in week two, when it's cheap, instead of month six, when it isn't.

The tell

There's a simple test, and you can run it on yourself today.

When you're about to hire, do you know what you want? Can you say out loud what winning with this person looks like?

"I need" is a powerful motivator, and it's usually where owners stop. "I need a strong sales leader." That's the beginning of a correct sentence. It just isn't the whole sentence. Finish it and it sounds more like this: I need a strong sales leader so that average pre-scope deal margin gets to a specific percentage by a specific date.

Now they walk in clear on the expectation, and you can actually tell what they're doing and whether it's working.

If the need is ethereal, what do you do with that? Let the new hire guess?

Because that's the real choice. The definition is going to get written either way. The only question is whether you write it before you hire, or whether your new hire writes it for you, quietly, out of whatever they did at the last place.

What we're not saying

Hiring isn't the problem, and waiting isn't a strategy. Sometimes the right move is to hire now, this month. Here's how we read the ones we hear most.

None of these are wrong. They're conditional, and the condition is whether the win is defined by the time the person starts.

What a miss actually costs

The cost of getting a hire wrong is monstrous even when you only count the obvious line items. Salary, benefits, recruiting, onboarding, the training time your existing team gave up to bring somebody along who's now gone.

But that's the accounting version, and it's the smaller half.

The world operates on the dollar, and it keeps operating while you're stuck. Six months with an ill defined hire and a number nobody owns is six months of business actively being transacted around you. Deals your competitor closed. Margin you didn't hold. Growth that was available and went somewhere else.

None of that lands on a spreadsheet, and it's usually several times the salary.

How this shows up in the work

When we assess a revenue engine, we score every stage across nine dimensions. Two of them decide almost everything about whether a hire is going to take: Accountability, meaning somebody is clearly responsible for a number and reviewed against it, and Alignment, meaning the people around that number are working toward the same outcome.

Every metric also carries two scores. A performance score for how the number compares to a healthy range, and a management score for whether it has an owner, a review cadence, and a history of somebody acting when it moved. Management carries thirty percent of the weight on its own.

Which is why an unowned number is the thing we flag before anybody talks about headcount. Hiring into a stage where nobody owns the outcome doesn't create ownership. It just adds a person to a number that still belongs to nobody, and hands them the blame for it six months later.

You can see where your own stages land on that scale in about ten minutes. It's the same scoring we run inside an engagement, and it's honest enough to be uncomfortable.

So, can you hire your way to a better company?

Yes, when you know what better means and can say it in a sentence with a number in it. The companies we've watched do this well weren't better at interviewing. They just knew what the seat was for before they filled it, so the person they hired had something real to succeed at.

That's the part that gets missed. A definition isn't a leash. It's the only thing that lets a good hire actually win. People rarely leave because the job was hard. They leave because they could never tell whether they were doing it right.