A five-minute argument
The room is on its fourth candidate of the afternoon. The scores are inconclusive. The panel is split — two in favour, two unsure, one quietly checking his phone. And then the decision arrives, in a sentence everyone in hiring knows:
“I have a good feeling about her.”
Careers turn on that sentence. So do companies.
This page is about that sentence — where it comes from, why it decides so much, and what it would take to retire it.
No one hires for the sake of hiring. A role opens because something must be achieved — revenue that isn’t growing on its own, a function that needs an owner, a problem that will not solve itself. And someone decided that a new person is the right way to get it done.
Before there was a vacancy, there was an outcome someone needed.
Which makes every hire a prediction. Someone looked at the available evidence and predicted that this person, out of everyone considered, would deliver that outcome.
The offer letter is the wager.
So it is worth asking how that prediction usually gets made.
Over the last thirty years, nearly every part of hiring has been rebuilt. Job boards replaced newspaper columns. Applicant tracking systems replaced filing cabinets. LinkedIn made half the working world searchable from a desk. Now AI reads resumes in milliseconds and sends outreach by the thousand.
Every one of these made hiring faster. Some made it wider. None of them fixed what happens before the tools switch on — the standard that was never defined.
Better methods for judging candidates do exist. Structured interviews, work-sample tests, evidence-based scoring — all measurably better than a conversation and a hunch. But a tool cannot define success for you. That part was left to the people. And the people were given nothing to work from.
Ask anyone who has hired for twenty years whether hiring feels more certain than it did in the nineties. You will get a wry look.
Thirty years of better tools — and the decision still rests on a standard nobody wrote down.
We improved every step of the process without ever asking what the process was for.
Go back to the moment a role opens. At that moment, the standard exists. The hiring manager knows — often precisely — what the new person must produce. That need is the reason the role exists at all.
Then the translating begins.
The outcome becomes a job description: requirements, responsibilities, qualifications. The job description becomes search keywords. The keywords surface resumes. The resumes become impressions — a strong brand here, a familiar title there.
Every translation loses something. And it always loses the same thing: the reason the role exists.
By the time a candidate sits in an interview, they are being measured against a photocopy of a photocopy of the outcome. And nobody in the room has seen the original.
It is easy to miss the loss, because each instrument does measure something. Just never quite the right thing.
And when the standard is missing, something predictable fills the gap: personal judgment. Not because people are careless — it is simply what judgment does when nothing else is written down. It is why interviews drift into chemistry tests. Why a famous employer on a resume outweighs an unglamorous decade of results. Why five interviewers reach five verdicts about the same person. Why bias finds room to work.
Nobody wrote the standard down. So everyone in the process quietly invented their own.
That is the room this page opened in. The good feeling was never the real problem. The missing standard was.
Which leaves one question
Many teams will say the standard already exists — they have scorecards, competency frameworks, structured interviews, success profiles. Good. Now read one honestly.
It lists what the person must have and what they will be responsible for. Skills, years, duties. It almost never states what the role must produce — or what evidence would show that a particular candidate can produce it. Even the sophisticated versions measure the inputs to the job, not the outcome the job exists to create.
So the honest answer to “what are we measuring against” is usually: a blurry picture that firms up as the meeting goes well.
The fix is not a new technology. It is a discipline older than any of the tools: define the standard before you measure. No laboratory calibrates an instrument against a feeling. In hiring, that is the norm.
So write it down — before anyone is searched, screened, or interviewed. What must this role produce? Which capabilities produce it? What separates a person who will succeed here from a person who merely qualifies?
This is not an innovation. It is a recovery. The standard existed the day the role opened. Defining success first simply refuses to let it evaporate on the way to the interview.
If it is that simple, why does almost nobody do it?
Because doing it properly is hard. It means working out what the business actually needs, which capabilities demonstrably deliver it, and what observable evidence would separate the genuinely capable from the well-rehearsed. It is hours of structured thinking per role. It is the first thing abandoned when a requisition is urgent. It is the work everyone agrees matters — and nobody has time to do.
It is also the work Ann was built to do first.
Before any search begins, before any resume is read, before any interview is scheduled, Ann defines the standard and writes it down. The definition is called a RoleDNA — not a summary of the job description, but the standard the job description failed to preserve. Recovered.
ROLEDNA — BUSINESS DEVELOPMENT SPECIALIST, EARLY-STAGE SAAS
(one of its Critical Success Factors, as delivered)
CSF 02 — Discovery-led demo that converts interest into a committed next step.
Runs a demo that begins with workflow discovery — the buyer’s current screening and interview steps, the systems in use, the bottlenecks, the success metrics — and then shows only what maps to what was heard, earning a concrete next step rather than a polite ending.
STRONG LOOKS LIKE
asks specific workflow questions before sharing a screen, tailors the demo path, names what would make the product a yes or a no, and closes with a scheduled next step and a stakeholder plan.
WEAK LOOKS LIKE
jumps straight into a feature tour, cannot connect the product to the buyer’s process, leaves the call with “we’ll get back to you,” and treats the demo as the finish line.
Read the two columns again. They are not requirements. Not competencies. Not keywords. They are descriptions of evidence — the observable difference between a person who has this capability and a person who merely talks like one.
And notice the uncomfortable part. The weak column is not describing a bad candidate. It is often describing the impressive one.
Most people who see a RoleDNA for a role they know well say the same thing: I have hired for this role three times, and I have never once seen its success written down.
Every hiring process is exactly as good as its definition of success. No better.
Once the standard exists, everything downstream inherits it.
Search stops being a keyword exercise. It becomes design — looking for people in whom evidence of this success could plausibly exist: adjacent companies, unfamiliar titles, places a keyword search cannot reach.
Resumes are read for evidence, not impressions. Claims are weighed against the definition. Strengths are credited. Gaps are recorded, not glossed over.
The interview becomes verification — structured, scored on evidence, asking for exactly the proof the standard demands.
The same standard governs every decision.
And this matters more than any single stage. Each stage is no longer a ritual to complete. Each one gathers evidence for the same prediction — this person will deliver these outcomes — stated once, at the start, in the definition of success.
Search gathers it. The resume evaluation weighs it. The interview tests it. The recommendation assembles it.
Search
gathers it
Resume evaluation
weighs it
Interview
tests it
Recommendation
assembles it
The prediction
This person will deliver these outcomes.
Not six stages. One prediction.
That is the whole innovation — and it is a change of thinking before it is a change of tools. Which is why thirty years of faster tools never produced it.
What arrives at the end is a recommendation you can hold. A shortlist — not a longlist. And for each person on it: what the evidence says, where it came from, how strong it is, and what it does not cover.
When a CFO asks why this candidate, the answer is not a score. It is the reasoning under the score — this claim, from this answer, weighed against this part of the standard. The confidence is earned. You can take it apart and check every piece.
Confidence comes from evidence. It never works the other way around. A hiring process that starts from confidence and works backward to justification has already failed.
And honesty requires saying the rest plainly: evidence is powerful, but evidence cannot see everything.
No definition of success makes the future certain. A candidate with strong evidence can still fail. Circumstances change. Organisations change. People change.
What evidence can do is different — and better than what it replaces. It can say how strong the prediction is, and show exactly what it rests on. Where the evidence is thin, the report says so. Where a capability could not be verified, the gap is admitted, not smoothed over. And Ann’s confidence in her own evaluation is stated separately from the candidate’s score — because those are two different things, and merging them is how numbers learn to lie.
A prediction that knows its own limits is worth more than a certainty that doesn’t.
If a page like this one promised you certainty, you would be right not to trust the rest of it.
Every hire you will ever make is a prediction. That was true before this page, and it will be true after it. The only question is what your predictions are built on.
Before there was a vacancy, there was an outcome someone needed. Before your next one, there can be a standard.
There is one way to see the difference, and it takes a day, not a meeting. Send Ann a live role — one you know well. Read what comes back.
You will know within a page whether it is right. You have lived this role. You are the one reader it cannot bluff.
See what success looks like before hiring begins.