How to make a defensible hiring decision

Then comes the uncomfortable moment. You chose someone for the role, you announced it, and then the question appears: “why this one and not the other who also looked good?”. Your manager asks it, the team that requested the opening asks it, sometimes the candidate who didn’t make it asks it. And if your only honest answer is “they seemed like the best one to me,” you have a problem: you made a decision you can’t defend.

A defensible hiring decision is exactly the opposite: it’s the one you can justify with comparable and traceable evidence. You defined what mattered for the role before looking at anyone, you assessed everyone against the same yardstick, and you can show why one person ended up above another. It’s not about being right every time; it’s about being able to explain the why with arguments that hold up to a second look.

Why intuition is no longer enough

For years, hiring was largely an act of personal judgment: you read the resume, you talk, you choose whoever gives you the best impression. The problem isn’t that intuition is useless —human judgment is irreplaceable—, but that a hunch can’t be compared or explained. If you interviewed six people and chose one, the legitimate question is: against what did you compare them, and how?

Today that question carries more weight. Teams ask for an accounting of why a given person was hired. High-volume processes make it impossible to remember the detail of each candidate. And when a decision affects someone’s working life, “they seemed right” is a fragile basis. The alternative isn’t to hire with less humanity; it’s to hire with more backing.

The four steps of a defensible decision

Building a decision that holds up doesn’t require a heavy process. It requires order, and that the order be recorded:

1. Define the criteria before assessing. Decide which competencies that role needs —not a generic template— and write them down. This avoids the bias of adjusting the yardstick to the candidate you liked most.
2. Assess everyone against the same yardstick. Apply the same assessment to each applicant to get a comparable signal across people. Comparing requires measuring the same way; if each candidate goes through a different process, you’re not comparing, you’re improvising.
3. Order with evidence, not with impression. Use the reports to see who shows signals of fit to the role and why. The ranking orders the pile; you read the context behind each signal.
4. Keep a record of the why. Document the arguments behind each step. If later someone asks how that hire was reached, the answer lives in traceable evidence, not in the memory of whoever was in the room.

Defensible to whom

It’s worth distinguishing who you need to defend a decision to, because each audience asks for something different:

• To your team and leadership: you need to show that the process was consistent and that the choice follows common criteria, not individual preferences. Here it helps to have decisions explained to the internal stakeholder.
• To the business that requested the opening: you need to connect the assessed competencies with what the role actually requires, so the hire is understood as a response to a need, not as a formality.
• To an audit or internal review: you need traceable evidence: what was measured, how, and where it was recorded. It’s worth reviewing with your legal team what your country’s regulations require regarding the handling of candidate data.

In all three cases, the material is the same: defined criteria, even assessment, and a record. Only the part you emphasize changes.

The difference between a score and a decision

It’s worth being clear about something: a defensible decision is not delegating the decision to a number. A score, a ranking, or a fit signal are inputs for deciding, not the decision itself. If you let a data point choose without anyone reading it with judgment, you didn’t make the process more defensible: you made it more opaque, because now no one can explain the context behind the number.

What’s defensible lies in the combination: comparable evidence that orders the conversation, plus a human team that reads that evidence, weighs what a data point doesn’t capture —the motivation behind a change of industry, the fit with the team, the weight of each competency depending on the role— and chooses with arguments. That’s why it’s worth learning to read an assessment report rather than blindly trusting its summary.

In short

A defensible hiring decision is the one you can justify with comparable and traceable evidence, not with intuition. To build it: define the role’s criteria before assessing, apply the same yardstick to everyone, order with evidence, and keep a record of the why. That doesn’t make you infallible nor replace human judgment —the team keeps the final decision—, but it lets you answer with arguments when someone asks why you chose who you chose. In hiring, being able to explain the why is worth as much as getting it right.