10 August 2026 · 3 min read

The hire that changes what you can take on

Most hires make the business slightly better. A small number make it a different business. Knowing which one you are making changes how you should make it.

Most hires are additive. You had one person doing a job, now you have two, and the business can do roughly twice as much of that job. Useful, but not the interesting case.

A small number of hires are not additive. They change what the business is capable of taking on at all. Before them, certain work was off limits, not because nobody wanted it but because nobody could actually do it well. After them, it is available.

The two look identical on a job spec. The difference only shows up in how you should be making the decision.

Why the ordinary process fails the important hire

The standard hiring process is built for the additive case, and it is good at it. Define the role, list the requirements, interview against them, pick the best fit. It works because you already know what good looks like, because you or someone like you has done the job before.

The capability hire breaks that process at the first step. You cannot fully specify the role, because part of the point is that this person will do things the business currently cannot imagine doing. Write the job spec too tightly and you filter out exactly the person who would have expanded it.

This is why these hires are so often made through a relationship rather than a process. Not because process is bad, but because the thing you are actually assessing, whether this person can be trusted to operate somewhere you cannot yet see, is not something a scored interview matrix captures well.

What to look for instead

A few things are worth more than the usual checklist, for this specific kind of hire.

• Evidence they have expanded a role before, not just filled one. Ask what they changed about how the job was done, not just what they did in it.
• Comfort with an unclear brief. Someone who needs the scope defined for them will operate inside whatever scope you give them, which is the opposite of what you need.
• A track record you can actually check, because you are trusting judgement in situations you cannot yet specify, and the only evidence for that is what they have already done unsupervised.

None of this rules out a structured process. It changes what the structure is testing for.

The cost of getting it wrong

An ordinary bad hire costs you a role's worth of output and the time to replace them. Painful, bounded, recoverable.

A bad capability hire costs more, because you tend to build around them before you realise the capability was not really there. Other decisions get made assuming the new capacity exists. Commitments get taken on. By the time it is clear the hire has not landed, you are not just short a person, you are exposed on everything you built on top of them.

That asymmetry is the actual argument for taking longer over these hires and moving fast on the ordinary ones. It is not caution for its own sake. It is that the two failure modes are not the same size.

The test worth applying

Before making one of these hires, it is worth asking plainly what changes if it works.

If this hire lands, what can the business do in a year that it cannot do today?

If the honest answer is "the same things, a bit faster," you are making an ordinary hire, and the ordinary process is the right one. If the answer names something the business cannot currently attempt, you are making the other kind, and it is worth treating that differently: slower, more relationship led, and judged on trust rather than on a scorecard.

Getting that distinction right, before you start, is most of the work.