Statements Open People Up, Questions Close Them#
Where it comes from#
It’s called elicitation, developed by John Nolan and written up in a book called Confidential, now out of print. It came out of intelligence work, which sounds more sinister than it plays in practice.
The mechanic is simple. A question is a request, and requests get evaluated. A statement is just a thing in the room, and correcting a wrong thing feels like being helpful rather than being asked.
The three moves#
Get the record corrected. Say something inaccurate and wait. Tell a Whole Foods employee you read that staff had all been moved to $26 an hour, and you’ll hear “what? I’m on $17.” Nobody asked them anything.
The Cold War version is the same shape with higher stakes — Soviet handlers telling a US Navy sailor that German submarines were faster because their propellers were 22 feet across. The sailor turns round and corrects the number, and the number was classified.
Bracket it. Offer a range and let them land inside. “Was that between March and May?” “Are you somewhere in the 39 to 59 range?” People correct a bracket almost reflexively, even when they’d have declined to answer the direct version.
Be a bit disbelieving. “There’s no way that whole trip went smoothly.” And off they go, listing everything that went wrong. A doubtful statement pulls detail out in a way an open question doesn’t.
How it sounds in practice#
Two openers carry most of it: so and I bet.
- “So you’ve been doing this about three years.”
- “I bet there were still some rough patches in that.”
- “I bet you had to get through a lot to get here.”
Then recap what they said back. “So — no creamer, no sugar. You’re very particular about coffee.” And they’ll expand on it, unprompted. You’ve not asked a single question the whole time.
The rule of thumb#
The more sensitive the thing, the fewer questions you should ask. Statements feel like conversation. Questions start feeling like an interview, and people get careful in interviews.
Worth being careful with#
This is genuinely useful and it does have an edge to it, so it’s worth being clear about how it should be used.
Used well, it’s a way around a defensive reflex that gets in the way of ordinary honest conversation — the guardedness that shows up even when nobody has anything to hide. That’s a real problem and this genuinely helps with it.
Used badly, it’s extracting things from someone that they’d have chosen not to give you had you asked straight. The test I’d apply: would you be comfortable if they knew exactly what you were doing? If yes, fine. If not, ask the question instead and let them decline.
A few small things to try#
- Swap one question today for a slightly-wrong statement and see what comes back
- Use a bracket instead of asking for a number
- Recap what someone said back to them and let the silence do the rest
- Before using any of it on something sensitive, check you’d be fine explaining the method