The Coherence Trap in Intake Meetings

Issue No. 9 • 19 May 2026 • Author: Joonatan Hongell

A friend in Berlin describes her new apartment over the phone. Big windows. Old wooden floors. A galley kitchen with a pass-through to the living room. By the time she stops talking you can already see the place. You'd recognize it if you walked past. A week later you visit and almost nothing matches. The windows face north instead of south. The pass-through is a doorway. The floors are vinyl. Neither of you described it badly. You both filled the gaps. Neither of you noticed you were filling them.

Something similar happens every time you sit down with a hiring manager to review a job description.

The brief is clear. Both of you say so. The hiring manager describes the role in two more sentences. You nod. You ask one or two questions and the answers confirm what you were already imagining. The meeting ends in forty minutes instead of the scheduled hour. Productive.

Three weeks later the shortlist gets rejected. The first candidate, who looked perfect to you, was "too operational." The second, who you flagged as a stretch, was "closer but not what we discussed." You read the JD again. The JD says exactly what you thought it said. The hiring manager isn't reading a different document. So why are the two of you not on the same page?

Daniel Kahneman, the psychologist whose work with Amos Tversky founded behavioral economics, called this WYSIATI. What You See Is All There Is. The brain takes whatever is in front of it and builds a coherent story. It ignores what's missing.

You feel this in something as small as a news headline. "Mayor Apologizes for Comments." Before you read the article, you have a complete story already. A male mayor, mid-fifties, said something insensitive at a press conference. The apology was half-hearted. You're confident about this picture, and you wouldn't notice you built it all from four words. Open the article and the mayor is twenty-eight, female, apologizing for cuts to a community arts program her predecessor had committed to.

Kahneman noticed that confidence rises when information is thin, not when it's complete. A coherent story is easy to build from a few details. A coherent story built from many details is harder, because the details start to contradict each other. The mind grades itself on coherence, not completeness.

Most recruiters think of a job description as a document that explains the role. It works more like a story prompt. The hiring manager wrote three pages of bullet points and the document feels complete. You read it and it feels complete to you. Both of you have constructed a person from the page. Both of you have constructed a different person. Neither of you can see the other's picture, so the question of whether they match never comes up.

This isn't a problem with the document. A perfect JD doesn't fix it. It makes it worse. The more coherent the document reads, the less either of you thinks to ask what's missing. "Technical leadership" might mean a hands-on engineer who still writes code and reviews PRs. It might mean a strategic relationship-builder who hasn't touched a codebase in eight years. Both interpretations fit. Both feel complete. Neither is challenged because the JD doesn't show the gap.

You see the divergence later, in the rejection language. "Too operational." "Too strategic." "Closer but not what we discussed." These sound like judgments about the candidates. They're the hiring manager's mental picture meeting yours for the first time. First shortlist is where the two of you discover you were never aligned.

You left the intake confident. The hiring manager left confident too. This is the part that frustrates good recruiters. Confidence is what the brain produces when a story is coherent, not when you've checked it. Two people leaving the same intake meeting both feeling certain isn't evidence that they agree. It's evidence that each of them constructed something internally consistent. The internal consistency is what makes the misalignment invisible.

This is why the standard advice, write better JDs and ask more questions, only helps at the margin. A clearer JD reduces gaps but doesn't eliminate them. Asking more questions surfaces what you both already know you don't know. WYSIATI is about gaps you don't know exist. You can't ask about a gap you can't see.

The exception is specialisation. A recruiter who has hired fifty engineers carries a mental picture of what a complete engineering brief looks like. The gaps feel absent, not filled. For a generalist reading the same document, nothing announces itself as missing. In practice, function specialists tend to show better intake alignment without deliberate intervention.

What helps is forcing the gaps to become visible by comparing pictures, not documents. The exercise adds ten minutes to the end of an intake meeting. After you and the hiring manager finish reviewing the brief, separate for five minutes. Each of you writes down what the new hire's first ninety days look like in concrete terms. Which meetings are they in by the end of week one? What's the first thing they should fix? Who do they spend the most time with in month one? Then come back together and put the two descriptions next to each other. The order matters. Both parties write before either sees the other's version. If one person speaks first, the second picture adjusts to fit theirs. You lose the contrast you needed to see.

The divergences surface in the specifics, not the headlines. The hiring manager pictures the new hire in the Monday operating review. You had them in the strategy syndicate. The hiring manager has them fixing pipeline conversion. You had them rebuilding the team. Each of these is a real preference the hiring manager has, and none of them are in the JD. None of them came up in the meeting because both of you read the JD as complete.

The first time you run this, you'll find more divergence than you expected in ten minutes. Each one is a candidate you would have screened against the wrong picture. Cost of finding out is a coffee. Cost of not finding out is the third week of search when you both stare at a strong profile and the hiring manager says "closer, but not really."

Run this enough times and you'll produce fake divergences too. Two pictures will differ on something the hiring manager doesn't care about, and the meeting runs an extra hour debating whether to add a line to the JD that nobody needed. The model explains invisible gaps, not every gap. When both parties already know information is missing (comp under review, reporting line TBD), they don't fill it in, because they know it isn't there. The exercise has the most value on roles where the JD reads as fluent and complete. On roles where the brief is openly thin, you don't need WYSIATI. You need a better brief.

The friend in Berlin will text you a photo of her apartment eventually. You'll see it and update your picture. The intake meeting doesn't text you a photo. It sends you a shortlist three weeks later, half of which the hiring manager rejects. By the time you find out, the picture you were both working from has felt correct in your head the whole time.

The Recruiting Lattice takes mental models from fields like behavioral science, sociology, and decision theory and turns them into practical tools for talent acquisition.