Your Intake Meetings Are Solving the Wrong Problem

Author: Joonatan Hongell

Picture a kitchen renovation. The architect, the structural engineer, and the homeowner all agreed on the same drawings. "Open-plan living area," the blueprint said. The architect meant a flexible entertaining space with a view to the garden. The engineer saw main walls that needed reinforcing. The homeowner pictured a quiet home office with some visual separation from the kitchen. Three people, one document, three different rooms.

More drawings wouldn't have helped. Everyone had the same plans in front of them. Three people looked at identical information and formed three incompatible pictures of what it meant. You could add a hundred pages of specifications and still end up with the wrong room.

A recruiter walks out of an intake meeting with clean notes, a completed template, and a brief that starts falling apart two weeks later. Candidates arrive and get rejected for reasons that weren't in the brief. Or two stakeholders evaluate the same candidate against different versions of the role, and nobody realizes it until the search has burned a month.

The usual fix is better preparation. Sharper templates. Pre-reads so the hiring manager comes ready. All reasonable advice, but it assumes the meeting's problem is informational. That the recruiter left without enough data, and that more data would have prevented the confusion.

In Sensemaking in Organizations, Karl Weick drew a distinction that explains why more data doesn't help. Uncertainty is a gap in information. You don't know the market salary for a director-level PLM role in Finland, so you look it up. Done. Ambiguity is a gap in meaning. The recruiter, the hiring manager, and the hiring manager's boss read the same job description and picture three different people. More data doesn't help, because there are too many interpretations, not too few facts.

Each problem demands a different response. Uncertainty needs research. Ambiguity needs conversation.

When a hiring manager says "I'll know the right person when I see them," most recruiters hear uncertainty. They send more profiles and wait for the shortlist to sort it out. But that statement almost always signals ambiguity. The hiring manager wants two different things and hasn't realized it yet. Maybe a technical builder and a strategic leader. Maybe a fix-it operator and a growth driver. Each version sounds right in isolation.

A sharper brief won't resolve this. Neither will a better template. Ambiguity requires people in a room, hearing each other's framing, pushing back, redirecting, building toward a shared picture.

Most intake meetings, though, are structured as briefings (or "intakes" as the name suggests). The hiring manager talks. The recruiter asks questions and fills in a form. That structure works well for uncertainty. You're extracting information and documenting it. When the real problem is ambiguity, a briefing is the wrong format. You need a meeting where everyone who'll make the decision gets their version of the role into the open.

You've probably noticed when this plays out. The intake where the hiring manager gives clear, confident answers and you leave feeling good, only to discover three weeks later that the VP who wasn't in the room has a different picture of the role. The meeting collected information efficiently. It never let the disagreement surface.

When a hiring manager says "I need someone senior," that word collapses a dozen dimensions into a single label. Scope of ownership, technical depth, stakeholder complexity, tolerance for ambiguity, team leadership. Hiring managers elaborate, of course. But it rarely gets precise enough to show the disagreement.

Weick called this "the vocabulary richness effect". The precision of a team's shared language determines what it can see. A vivid, specific term draws attention to distinctions that a vague term hides. When a hiring team operates with limited shared vocabulary, important differences stay invisible.

"I need someone who can own the product roadmap, influence without authority across the business lines, and build the team from scratch." That sounds like a clear brief. But "own the roadmap" means "decide what gets built" to the product lead, and "make sure we can sell it" to the commercial director. "Build the team" means hire three senior engineers to one stakeholder and stand up a new function to another. The conversation felt thorough. The brief still points in different directions. The clarity is an illusion built on language that sounded specific enough.

A recruiter who suspects the brief is confused can't easily prove it. The evidence is the brief itself, which says "senior strategic product leader" and which everyone signed off on. The confusion lives inside language that looks precise enough to pass. To reveal it, you have to force precision into the conversation.

The shift starts before the meeting begins. If you can tell early whether you're dealing with uncertainty or ambiguity, you'll know whether the standard template is the right tool. Before asking about requirements or experience levels, make sure the right people are in the room and ask the room what problem this hire is solving. If the answer comes quickly and everyone agrees, you're probably in uncertainty territory and the template works fine. Hesitation, competing explanations, a long pause. That's ambiguity territory. The rest of the meeting shifts from collecting answers to exposing differences.

Once you've made that shift, the meeting itself has to change. Put two competing descriptions of the role on screen and ask which one is closer. Ask each stakeholder to describe what the new hire is doing at the twelve-month mark, and let the descriptions diverge. When they diverge, you've found the gap. Work through it before anyone leaves the room. The goal is a shared picture of the role, not a filled-in form.

But the right format only works if the vocabulary can keep up. When someone says "senior," push on which dimension they mean. When someone says "entrepreneur-minded," ask them to describe the specific behavior they're picturing. It feels uncomfortable. When you ask "what do you mean by senior?" in a room where everyone thinks the brief is clear, you sound like you're slowing things down. You are. But the alternative is three weeks of sourcing against a brief that everyone reads differently, and by then the cost is someone else's wasted time, not just yours. The room will resist this. Language vague enough for everyone to agree on is comfortable. Precise language forces choices, and choices surface the disagreements that were hiding under words everyone thought they understood.

These shifts assume the participants want to resolve the ambiguity. When two factions want different things from the hire and the hiring manager can't afford to disappoint either one, keeping the brief vague is the path of least resistance. Sharper vocabulary and better meeting design won't help. You can't resolve ambiguity that someone has a reason to preserve. That situation doesn't have a clean answer, and if you've been recruiting long enough, you've been in that room.

But when the ambiguity is unintentional, and it usually is, the recruiter is often the only person in the room positioned to see it. Everyone else is too close to their own version of the role. And once you can say "we're not missing information, we're looking at the same brief and picturing different people," you can slow the room down. Making the confusion visible before it costs everyone three months is the work.

About that kitchen renovation. The room they built wasn't the room anyone wanted, and everyone had the signed drawings to prove they'd agreed. Right now, somewhere, a recruiter is sourcing against a brief that nobody reads the same way.

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