Day 263 of the Daily · Talent Management

The Interview Illusion

5 min read · 4 principles · apply it by lunch

Morning. You’ve never met a candidate you couldn’t read. That’s precisely the problem.

The question

Think about the last person you interviewed and turned down — can you name the specific thing they said that changed your mind, or was it that the conversation never quite lifted, and if it’s the second, what exactly did you learn that morning about the candidate rather than about the room?

The idea

Jason Dana, who teaches at the Yale School of Management, ran a set of experiments with the Carnegie Mellon psychologist Robyn Dawes and Nathanial Peterson. Undergraduates interviewed other students and then predicted their grade average for the coming semester. Some interviews were ordinary. In others the person being interviewed had been told to answer the second half at random, deciding each yes or no by a rule about the letters in the question rather than by anything true about themselves. Nobody was warned, nobody noticed, and the interviewers came out reporting they’d got a sense of the person. In a second study, students who watched recorded interviews were told afterwards that half had been random, and still judged more than half of the random ones genuine. The arithmetic is the part that hurts. A student’s prior grades, used alone as the forecast, tracked the real result at .65. Predictions made after an interview managed .31. The conversation didn’t merely fail to add — it diluted what was already there. The paper ran in Judgment and Decision Making in 2013, and Scott Highhouse of Bowling Green State University had explained five years earlier why a finding like that changes almost nobody’s process: a method that removes your read on people feels like a verdict on your judgement. Day 70 named the mechanism. An interview is the ladder of inference at its most expensive — whatever a candidate says, you’ll build it into a story, and coherence feels exactly like insight.

In the Daily · 4 principles and a template

The Interview Illusion is Day 263 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Talent Management

The next four in the course.

All 19 Talent Management frameworks
Day 276 · Talent Management

The Structured Interview

Pull up the last interview you ran: how many of the questions were written down before you walked in, how many were asked of every candidate in the same order, and how many answers did you score on paper before you heard what anyone else in the room thought? Whatever that count is, it’s the share of the decision that wasn’t really about the candidate.

See the framework →
Day 286 · Talent Management

The Work Sample

For the last role you filled, what did you actually watch that person produce before you signed the offer — a document, a call, a piece of code, a plan for something real — as opposed to hearing them describe having produced things like it? If the honest answer is nothing, you didn’t hire on evidence. You hired on a well-told story about evidence.

See the framework →
Day 295 · Talent Management

The Reference Search

Think about the last reference call you made, or the last one you quietly skipped: did you go in with a specific scorecard line you were trying to settle, or with a vague hope that somebody might volunteer a warning? One of those is a search. The other is a formality with a phone attached.

See the framework →
Day 308 · Talent Management

Adding Up, Not Sizing Up

Think about the last person you hired: when the decision actually got made, was there a total on the page — a number per candidate, produced by a rule fixed weeks earlier — and could every person in the room see it, or was there a sheet in front of one of you and a conversation in front of the rest? If no total existed, you’ll never know whether your process works, because you never wrote down what it predicted.

See the framework →