Elicitation is the strategic use of conversation to obtain information without directly asking questions. It’s not about interrogation—it’s about guiding people to voluntarily reveal insights they may not realize they’re sharing. While often used in intelligence circles, the techniques are rooted in universal psychological behaviors.
According to the FBI, elicitation leverages common human tendencies like:
- The desire to appear competent, especially in professional settings
- The tendency to be helpful and polite
- The need to feel appreciated or heard
- The urge to correct others when they’re wrong
These instincts are well-documented by researchers like Robert Cialdini and Daniel Kahneman, grounded in concepts such as reciprocity, social desirability, and impression management.
Core Rule: The More Sensitive the Information, the Fewer Questions You Should Ask
Elicitation is built on making statements, not asking questions. One of the simplest and most effective tactics is deliberate misinformation to trigger correction.
Example:
You’re at a networking mixer at a tech conference. You’re speaking to a developer from a well-known startup and you want to know what she earns—but you’re not allowed to ask directly.
Instead, you casually say:
“I heard all the engineers at your company just got bumped up to $160K starting salary. That’s wild.”
She replies:
“What? I wish. I’m still stuck at $118K.”
Without asking a single question, you now have a precise answer—because she felt a natural need to correct the record.
Three Core Elicitation Techniques
- Correcting the Record (Deliberate False Statements)
State something inaccurate to provoke correction.
Example: “I heard your company’s launching the new platform in October, right?”
“No, actually it’s being pushed back to January.” - Bracketing
Offer a range to make the other person feel safe narrowing it down.
Example: “You’ve been there what, five to seven years?”
“No, just a little over six.” - Disbelief
Show disbelief to invite clarification or contradiction.
Example: “You seem like you just came back from a long vacation.”
“I wish—I’ve been putting in 80-hour weeks since Q1.” Then follow up with a neutral challenge: “Wow, and it all ran smoothly? No hiccups?”
“Actually, we had a server crash last month, and it was chaos.”
Supporting Techniques
- Flattery:
“You probably have a dozen war stories from scaling that infrastructure.” - Macro to Micro:
Begin broad, then narrow: “Sounds like you’ve been involved in every stage of that product.”
“So when did the compliance issues start?” - Soft Lead-Ins:
Use phrases like “So…” or “I bet…” to set the stage.
Examples:- “So, you’ve been in DevOps for a few years or so.”
- “I bet the last deployment came with a few surprises.”
- “I bet you had to jump through a lot of hoops to get that feature approved.”
These subtle, conversational statements disarm resistance and make people feel like they’re simply sharing—not being interrogated.
