Ask an AI to summarise a meeting and it will hand you a clean, defensible list of who said what. Ask it to have caught the moment a stakeholder said something confident, vague and impossible to argue with, in real time, while you were also trying to keep the room on side, and it has nothing. That moment belongs to you, and most technical professionals walk straight past it because nobody ever taught them what they were actually hearing.
There is a specific pattern behind almost every objection that sounds unanswerable in the room. I call it a Distortion in my book ENGAGE, drawn from the linguistic Meta Model I trained in as a Certified NLP Trainer and simplified down to four types you can use without a psychology degree. Learn to hear these four, and you have a one line question for each that opens the objection back up, calmly, without turning the room against you.
What a Distortion actually is
A Distortion is what happens when someone twists the meaning of something into a version it was never meant to carry, usually without meaning to. It sounds like certainty. It rarely is. The person saying it has often built a small story in their head and jumped straight to the ending, and because they said it with confidence, everyone in the room, you included, tends to accept the ending along with them.
Technical professionals are trained to spot a broken argument on a whiteboard or in a test suite. The same rigour rarely gets pointed at the sentence someone just said out loud in a steering committee, because pointing it out feels confrontational. It does not have to be. The method here is to ask a genuinely curious question, not to win an argument, and each of the four types below comes with the specific question that does it.
The four Distortions, and the question that opens each one
1. Mind Read. This is someone claiming to know what is going on inside another person’s head. “I know why the board knocked this back.” “She only said that because she doesn’t rate the team.” Nobody has that access, including the person saying it. The destroyer question is simple: “How do you know that?” It is not aggressive. It is a genuine request for the evidence behind the claim, and there usually isn’t much.
2. Says Who. This is a judgement stated as though it were a fact, with no source attached. “It’s not a good look to push back on this in front of the client.” Says who? The destroyer question, asked with real curiosity rather than sarcasm, is exactly that: “According to whom?” or “What makes that true?” Once the source has to be named out loud, the judgement usually gets smaller.
3. Cause and Effect. This is someone claiming that one thing forces another thing to happen. “That stakeholder makes this project impossible.” Nobody makes anyone feel or do anything without a decision sitting somewhere in the middle. The destroyer question puts the cause back where it belongs: “What is it about that stakeholder that leads you to choose that response?” It sounds almost too polite to work. It works because it is genuinely hard to argue with.
4. This Means That. This is two unrelated things that happened at the same time being treated as connected. “Engineering blew the last deadline, so this estimate is soft too.” One data point has just been turned into a rule. The destroyer question needs only one counter example: “Has this team ever delivered on time before?” One yes and the rule is gone.
Using this without sounding like a cross-examination
None of these questions work if they land as a challenge. Ask with a genuinely curious tone, sometimes even a light one, because the goal is to reopen a conversation, not score a point off someone. This is the half of the skill that gets missed constantly by technical people, who are often excellent at spotting the logical gap and terrible at asking about it without sounding like they are cross-examining a witness. Competence spots the Distortion. Warmth is what lets you ask about it and still get invited back to the next meeting.
Where this actually shows up
A vague, confident objection is the moment most technical professionals lose a room, not because their argument was wrong, but because they either swallowed the objection whole or argued back too hard and looked defensive doing it. “The business will never accept that” is a Says Who wearing a suit. “This always happens when we ship on a Friday” is a This Means That with one data point doing the work of ten. Neither survives one calm, curious question, and asking it well is the difference between a technical expert who gets talked over and one who is trusted to run the room.
Try this
Pick one of the four Distortions and listen for it specifically across your next few meetings, rather than trying to catch all four at once. When you hear it, do not respond immediately. Ask the destroyer question slowly, then stay quiet. The gap where the other person actually has to answer is where the real conversation starts, and it is a gap a summary written after the meeting can never open for you.
This is one of a set of named techniques in the Guide section of my book ENGAGE, alongside the Rapport Triangle and the technique behind breaking through the technical ceiling. Every one of them is a skill you can practise this week, not a personality trait you either have or don’t.