We ran two finalists through an identical interview spine and still nearly picked wrong, because one panelist was measuring against a different job. What the debrief is really for.
One hour of debrief taught me more than six hours of interviews this week. We closed a search for a senior design technologist, the hybrid seat where design systems, production code, and AI-assisted workflows meet, and we’d run two finalists through the same interview spine deliberately: same question architecture, same scorecard, so the panel could compare two full pictures instead of two vibes. I recommend the standardized spine to anyone who hires. I also now know it’s half the job.
Ten minutes into the debrief, one panelist’s read on our leading candidate diverged hard from everyone else’s. Where the rest of the panel saw range and initiative, he saw risk and sprawl. We circled politely, each side re-describing the same interview, until the cause surfaced: he’d been scoring against a different job. His honest picture of the seat was an executor, someone who receives well-defined tickets and dispatches them cleanly. The rest of us were scoring for a builder of new capability. Same candidate, same transcript, two measuring sticks that had never been laid side by side. Once the role definition got restated out loud, his assessment moved, with no stubbornness in it. He’d answered the question he thought we were asking, and the failure was upstream and mine to own.
A shared question spine is worthless without a shared answer key, and the answer key is the role definition.
With the sticks aligned, the actual choice emerged, and it was a good one. Our finalists spiked in different directions. One spiked toward the role’s future: agentic AI workflows, token architecture as a machine-readable system, guardrails that keep autonomous tools from freestyling new components. The other spiked toward the role’s present: governance at human scale, the craft of running a system dozens of designers consume daily without friction. Neither spike is wrong, which is what made it a decision instead of a sorting problem. We chose the future spike because it fills a gap nobody on the team can cover, while the present spike overlaps strength we already have. Your team may point the other way. The shape of the reasoning travels even where the outcome doesn’t: when finalists spike differently, you’re choosing which gap matters more, and that’s a strategy question wearing a hiring question’s clothes.
The offer under discussion risked landing above what a comparably skilled woman on an adjacent team earns in base salary. We held base parity and moved the flexibility to a signing bonus. The mechanics took ninety seconds; the precedent avoided would have lasted years. Inequity is a stack of individually reasonable decisions viewed from above, and the debrief is the last room where the fix costs nothing.
The teachable part
Lay the measuring sticks side by side before anyone scores a human against them, and when spikes differ, decide the strategy question first. Interviews test the candidates. The debrief tests whether the organization knows what it’s hiring for.