The Meaning of Communication Is the Response You Get
July 26, 20267 min read1,507 words
I gave a technically perfect briefing to a hospital leadership team and watched every face go blank. I blamed the room. It took an NLP presupposition to show me the room was the scoreboard, not the problem.

The takeaways
- 01
The response you get is the actual meaning of what you said, no matter what you intended to say.
What to do nextReview your last meeting that went nowhere and write down what the room must have heard.
- 02
Blaming the audience protects your identity and guarantees nothing changes.
What to do nextTake full responsibility for one recent miscommunication and re-send the message differently.
- 03
Length is usually fear. Caveats, jargon, and long buildups are insurance against being judged.
What to do nextTake your next update and cut it in half before you deliver it.
- 04
Real confidence comes from reps, and reps let you drop the hedging that makes you long-winded.
What to do nextDeliver one three sentence version of something you would normally explain for ten minutes.
- 05
Silence after a short answer is the confidence tell. It invites the response instead of avoiding it.
What to do nextStop talking one beat earlier than feels comfortable in your next conversation and wait.
- 06
Confirming comprehension out loud beats assuming it. Ask what they will do next.
What to do nextEnd your next meeting by asking each person to say back the one action they own.
“The meaning of communication is the response you get” is an NLP presupposition that treats the listener’s response as feedback about your message. I use it to check understanding and adjust my explanation. It is a practical lens, not a scientific law or a claim that speakers control every response.
I remember the exact moment the room went flat.
Alpine Security days. A hospital leadership team, a conference table, my slides on the screen. I had the findings cold: segmentation gaps, a device fleet running firmware nobody had touched in years, an authentication path that would embarrass a vending machine. I walked them through all of it in careful technical order, forty minutes of accurate work.
When I finished, the CFO asked one question. "So are we okay or not?"
Forty minutes. That was the response I got.
I drove back annoyed, and here is the honest part: I was annoyed at them. They were not technical enough. They did not appreciate the depth. Somebody should have prepped them better. Everything I told myself put the failure on the other side of the table, which is a very comfortable place to put it, because then nothing about me has to change.
Communication Is More Than Sending Accurate Information
I believed communication was transmission.
My job was to send the message accurately. Their job was to receive it. If I said something true, clearly worded, well organized, and backed by evidence, I had communicated. What happened after that was on them.
That belief is extremely convenient for smart people. It means you can be right and ineffective at the same time and still keep the identity intact. I ran on it for years. I could leave a meeting where nothing changed and tell myself I had done my part, because I had transmitted correctly.
More than that, I used volume as armor. The longer I talked, the more competent I sounded to myself. Every qualifier, every caveat, every "it depends on the threat model" was insurance against being caught not knowing something. I was not briefing. I was covering.
A Clear Message Must Address the Listener’s Decision
The wall was that nothing moved.
I could deliver an assessment that named a real patient safety risk and watch the report get filed. No budget, no remediation, no urgency. Meanwhile someone with half my technical depth would say one sentence in a hallway and the hospital would fund the fix.
For a while I filed that under office politics. It is not politics. That person got a response. I got a nod.
And the pattern was not just at work. I could feel it in arguments with people I cared about, where I would win the exchange on the facts and lose the actual thing I wanted, which was to be understood. Same mechanism. I was measuring my output instead of their response.
What the NLP Communication Presupposition Means
In Neuro-Linguistic Programming there is a presupposition that reads like a slap the first time you actually hear it: the meaning of communication is the response you get.
Not what you intended. Not what you said. Not what a reasonable person should have understood. The response is the meaning. If the room heard "everything is on fire and I have no plan," then that is what I said, regardless of the words that left my mouth.
The first thing that shifts when you take that seriously is where the responsibility sits. There is no more blaming the audience. The listener is not failing your message. The listener is the readout on your instrument panel. Blank faces are not rudeness, they are data. "Are we okay or not" is not a dumb question, it is a precise report that I never answered the only question they came in with.
The second thing that shifts is your definition of a good meeting. It stops being "I explained it well" and becomes "they did something differently afterward."
How Competence Supports Concise Communication
Here is the part I did not expect.
Once I started measuring by response, my sentences got shorter, and the reason had nothing to do with communication technique. It was confidence, and confidence in the real sense: evidence from reps, not a feeling I manufactured before walking in.
For me, unnecessary length sometimes became fear wearing a suit. We add words when we are protecting something. The caveats protect us from being wrong. The jargon protects us from looking basic. The long buildup protects us from a verdict. Every extra clause is a tiny insurance policy against judgment, and the audience feels the hedging even when they cannot name it.
When you have enough relevant practice and feedback, you stop needing the insurance. You know what matters and what does not, so you can drop nine tenths of it without anxiety. You can say "you have a real problem in three places, here is the one to fix first, it costs about this much, and I will show you the rest if you want it" and then be quiet.
That silence at the end is the tell. Insecure communication cannot stop talking, because stopping invites a response and the response might be judgment. Confident communication stops on purpose, because the response is the whole point.
So the loop runs both directions. Competence produces confidence, confidence produces brevity, brevity produces a cleaner response, and a cleaner response tells you fast whether you actually landed it. The feedback gets sharper the shorter you get.
What Changed at Blue Goat
These days a device manufacturer does not get my forty minutes.
They get: here is what could hurt a patient, here is what the FDA will stop you on, here is what we do about it. Three lines. If they want the packet capture and the CVE chain, it is in the report and I will happily go there, but it is pull, not push. The technical depth did not go anywhere. It just stopped being the opening move.
The response changed accordingly. Fewer nods. More decisions.
And when a room does go blank on me now, which still happens, I do not drive home annoyed. I go back and look at what I actually said, because the blank face already told me the answer.
How to Check Understanding and Adapt Your Message
Name the response you want before you speak. Not the information you want to convey, the thing you want the other person to do or feel. If you cannot say it in one sentence, you are not ready to open your mouth.
Watch the person, not your notes. The confusion shows up two sentences before they interrupt you. Most of us are too busy executing our plan to catch it.
Cut the sentence in half and see if the meaning survives. It usually does. What dies is the hedging.
When you get a bad response, run it as data. Ask what a reasonable person would have to have heard to react that way. That answer is what you said.
Ask them to say it back. "What are you walking out of here going to do?" is an uncomfortable question that ends the guessing. It is also the fastest way to find out you were unclear while you can still fix it.
Stop talking earlier than feels safe. This one is a confidence rep. Say the short version, then hold the silence. The response you get is the meaning, and you cannot collect it while you are still talking.
Put the Feedback Back Into the Loop
Before you choose the next attempt, weigh the gains and losses of acting and staying put. Decision clarity is not a replacement for the rep. Decision clarity helps you choose a rep worth taking, then use the result as evidence.
The Reframe
I used to think the mark of expertise was how much I could say about something.
It is the opposite. The mark of expertise is how little you need to say to get the thing to move. Depth earns you the right to be brief, and brevity is what lets you find out whether the depth was worth anything.
The room is not your audience. It is your scoreboard.
Continue the Confidence Series
My building confidence guide and reading path brings together competence, gain/loss decisions, trigger awareness and communication. Use it to choose where to start or return to the next part of the loop.
Concise Communication Is Not Certainty or Control
A longer explanation may be necessary for accuracy, accessibility or a complex decision. I remove repetition, not essential caveats. Communication is shared: context, language, distraction and the listener’s choices also affect the response. My responsibility is to explain honestly, listen and clarify, not to guarantee agreement.
Sit with this
- Where are you being technically right and practically ignored?
- Which words in your standard explanation exist to protect you rather than to help the listener?
- What response would tell you the message actually landed, and are you measuring for it?
Frequently asked
Keep reading
Make Tough Decisions With the Four-Box Gain/Loss Framework
Choose the next confidence-building rep by weighing the gains and losses of acting and staying put.
Read essay →True Confidence Comes From Competence
Where the confidence that lets you speak in fewer words actually comes from.
Read essay →NLP Presuppositions for Leaders
The other thirteen presuppositions I use to lead myself and other people.
Read essay →The Secure Methodology Step Four: Communication
The step in my methodology built entirely around this problem in technical teams.
Read essay →Noticing My Triggers and Changing the Behavior
What fires in you right before you start over-explaining.
Read essay →