On this page
Why Gut Tie-Breaks FailStep 1: Score Both Candidates Against the Same Job Description on the Same DimensionsStep 2: Compute the Per-Dimension Delta — A Worked ExampleStep 3: Document the Tie-BreakerStep 4: Write It So It Is AuditableFAQYou have interviewed six people, advanced two, and now you are stuck. Both finalists are "strong." The debrief keeps circling back to feel. Someone says "I just think Candidate A has the edge" and everyone nods — or argues. An hour later you have a decision no one can quite explain to the candidate who didn't get the offer.
This is the most common failure point in hiring, and it is almost entirely avoidable.
Why Gut Tie-Breaks Fail
The problem with intuition at the final stage is not that it is always wrong — it is that it is untraceable. You cannot explain it to the rejected candidate, you cannot learn from it, and you cannot defend it if the hire goes badly. When two senior people disagree on gut, you get a deadlock resolved by whoever has the most status in the room.
The fix is not to eliminate judgment — it is to make judgment legible. You do that by scoring both candidates against the same dimensions, anchored to the same evidence, before the comparison begins.
Step 1: Score Both Candidates Against the Same Job Description on the Same Dimensions
The single most common cause of a meaningless final comparison is that the two candidates were evaluated against different implicit criteria. Before you compare, align on the dimensions the role actually requires.
Verdict's six-dimension model provides a ready-made structure: Capability (can they do the work at the required level?), Track Record (measurable outcomes at comparable scope?), Trajectory (growth rate accelerating, flat, or declining?), Influence (can they move stakeholders they don't control?), Domain edge (specific knowledge hard to build quickly?), and Risk surface (signals that reduce confidence in any of the above?).
Score each dimension 1–5, anchored to verbatim evidence from the CV or interview. See the six-dimension evaluation reference for level anchors.
Critical rule: complete scores independently before placing the two candidates side by side. Simultaneous comparison invites contrast bias — a candidate looks stronger because the other is weaker on one dimension, not because they are objectively strong.
Step 2: Compute the Per-Dimension Delta — A Worked Example
Once you have independent scores, the comparison becomes arithmetic, not negotiation.
Suppose you are hiring a Senior Product Manager to own a B2B growth loop. Two finalists: Candidate A and Candidate B.
| Dimension | A | Evidence (A) | B | Evidence (B) | Δ |
|---|---|---|---|---|---|
| Capability | 4 | "Shipped pricing experiment that lifted NRR 6 pp; walked through the test design cold" | 3 | "Strong instincts, but take-home showed limited SQL-driven funnel analysis" | +1 |
| Track Record | 3 | "Two major launches; one shipped late, no retrospective documented" | 4 | "Three launches, all on schedule; churn analysis credited to her in two separate CVs" | −1 |
| Trajectory | 3 | "IC → PM → Senior PM in 6 years; last two roles same scope" | 4 | "IC → PM → Senior PM in 4 years; took on 40% larger team after 14 months in current role" | −1 |
| Influence | 4 | "Cross-functional spec co-authored with engineering lead, cited in board deck" | 3 | "Influenced design, but all examples were within the product org" | +1 |
| Domain edge | 4 | "Published PLG teardown cited by two SaaS newsletters" | 2 | "B2C background; B2B experience limited to one pilot" | +2 |
| Risk surface | 2 | "Left two roles in under 18 months; no narrative bridging the gaps" | 1 | "Consistent tenure; one role ended with acquisition" | −1 |
Totals (equal weights): A: 20 / 30 — B: 17 / 30.
Scoring note: Risk surface is scored inversely — a lower score means more risk signals, not fewer. A scores 2 (two short tenures, no bridging narrative); B scores 1 only because the one short role had a documented cause (acquisition). B therefore leads on three dimensions — Track Record, Trajectory, and Risk surface — while A's higher overall total is driven primarily by the two-point Domain-edge advantage.
The story is in the deltas, not just the totals. A leads on Capability, Influence, and Domain edge — the dimensions most relevant to a PLG-heavy B2B role. B leads on Track Record, Trajectory, and Risk surface, which matters for long-run retention and execution consistency. The delta table makes the real trade-off explicit: a specialist with stronger PLG knowledge and a monitored flight-risk signal (A) vs. a consistent executor who needs to build B2B depth (B). That is a business decision — but now it is a legible one.
Step 3: Document the Tie-Breaker
When totals are genuinely close (within 2 points on a 30-point scale) and the dimension deltas don't yield a clear answer, you need an explicit tie-breaker declared before you look at the scores.
- Role criticality weighting — assign 2× weight to the two or three dimensions that most directly determine first-90-day success, then rerun the totals.
- Risk asymmetry — ask which failure mode is more recoverable. Hiring A and discovering the tenure pattern repeats costs 9–12 months and a re-hire. Hiring B and investing in B2B ramp costs 3–6 months of slower onboarding. The asymmetric cost often resolves the tie.
- Reference check differential — if scores are tied but one candidate's references are materially more specific ("she identified the pricing ceiling no one else had measured"), weight that.
Document which tie-breaker you used and why, before the decision is announced.
Step 4: Write It So It Is Auditable
A defensible hiring decision has three written artifacts:
- Independent scorecards — one per interviewer per candidate, completed before debrief, with verbatim evidence quotes. These are the raw material.
- The delta table — the side-by-side comparison above. Two pages maximum. The evidence column forces you to confirm every score has a source.
- The decision memo — three to five sentences: "We chose Candidate A because Domain edge and Influence scores materially outweighed B on the dimensions the role weights most. The Track Record delta favoured B, and references surfaced a partial explanation for A's shorter tenures, but the pattern remains a monitored risk. We applied 2× weight to Domain edge based on the enterprise client requirement in the JD."
Ten minutes to write. Prevents the two most common post-hire problems: the team forgetting why the decision was made, and the rejected candidate receiving an explanation that sounds like a brush-off.
Verdict automates the scorecard and delta table steps — upload both CVs against the same JD and get parallel six-dimension scores with verbatim CV evidence, ready for debrief.
FAQ
What if both candidates score identically on every dimension? Extremely rare once scores are evidence-anchored. When it happens, apply role criticality weighting (Step 3). If weighted totals are still tied, extend the process — a second reference round or a brief task scoped to the dimension with greatest uncertainty.
One interviewer gave very different scores from the rest. What do we do? Don't average it away. Ask the outlier to show the evidence for their score. Either they saw something others missed (update the group score) or they applied a different standard (recalibrate to the rubric). Averaging buries the signal.
Is it fair to use Domain edge as a differentiator if one candidate simply had more access to opportunities? Score what they produced, not where they sat. Domain edge grounded in publications, open-source contributions, or published analysis is evidence of output. Domain edge inferred from a prestigious employer's name is pedigree bias dressed as evaluation.
Does this framework apply to internal promotions? Yes, with one adjustment: Risk surface gains weight in a Promote evaluation because internal moves have a longer evidence record and the failure mode — a misaligned promotion — disrupts an existing team. Add a "first-90-days readiness" column drawn from the manager's direct observation notes.