Directory · C
Not sure this is the right entry? Run the check · New here? Start with the premise
Communication
2 min read · 485 words
What you send is never quite what arrives — the other person rebuilds it through their own filters. Most of the work is sending the information rather than the weather.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Communication is the attempt to transfer information from one control room to another through a channel that distorts everything it carries.
The Relationships entry established the core problem: the transmitter sends behavior (words, tone, timing, expression); the receiver processes that behavior through their own filters (projection templates, threat detection, confirmation bias, bonding protocol) and produces an interpretation. The interpretation feels like receiving. It is manufacturing. What arrives in the receiving control room is never exactly what was transmitted.
This is the permanent condition. The channel cannot be made lossless. The work is to minimize the distortion.
FROM THE TRANSMITTING END
The most common transmission error is sending the weather instead of the information.
The system produces an emotional response to a situation. The emotional response and the situation are different data. The anger signal fires because a boundary was crossed. The boundary crossing is the information. The anger is the system’s response to it. An organism that transmits the anger (you always do this) produces a different effect than one that transmits the information (this specific thing happened and it’s not workable).
Both channels are honest. One gives the receiving system something to work with. The other gives them something to defend against.
To transmit from the control room: identify what the system is responding to — the event, the condition, the behavior — and separate it from what the system is producing in response. Transmit the event. Let the response be visible (suppression is not the goal) but not the primary content.
FROM THE RECEIVING END
The most common reception error is processing the transmission through the projection template instead of through the actual data.
The incoming signal — the words, the tone — enters the hardware and immediately gets filtered through whatever model the receiver has built of the transmitter. If the model says this person is critical, neutral statements get processed as criticism. If the model says this person will leave, distance gets processed as abandonment signal. The filter runs before the conscious processing layer, which means the receiver is responding to the filtered version before they’ve had a chance to evaluate the raw data.
To receive from the control room: notice the interpretation and check it against the actual transmission. What was literally said? What was the actual behavior? Before the filter processed it, before the model interpreted it — what was the data? If the interpretation and the data don’t match, the filter is contributing content. The filter may be right. It may be running old code. The check is worth making.
The goal is not perfect fidelity. The channel will always distort. But two operators who know their own filters — who transmit information rather than weather, and who check their reception against the raw data before responding to the processed version — produce communication that is substantially less distorted than the default.
Send the information, not the weather
The channel distorts everything it carries. You transmit behaviour — words, tone, timing, expression — and they rebuild meaning out of it through their own filters, their own threat detection, and their own assumptions about what you probably meant. What arrives is always a reconstruction. That's the permanent condition; the work is reducing the distortion rather than eliminating it.
The most common transmission error is sending the emotional response instead of the thing it's responding to. Your anger fired because something got crossed. The crossing is the information. The anger is your system's reaction to it — and those are different data.
Compare you always do this with this specific thing happened and it isn't workable. Both are honest. One hands them something to work with; the other hands them something to defend against, and defending is what they'll do, because the first one is a characterisation and characterisations fire the defence before anything gets evaluated.
The other half is on the receiving end, and it's the half most people skip entirely: being told is not the same event as being heard. Saying back what you understood, before responding, catches the reconstruction while it can still be corrected — and people are wrong on the first attempt far more often than they'd predict.
What to actually say
Specific beats emphatic. Nearly everything here works by separating what happened from how it landed, which gives the other person something to act on instead of something to deny.
- Instead of a characterisation
When this happened, the effect on me was this. I'd like it to be different.
- Checking what actually arrived
Let me say back what I think you mean, and you tell me what I've got wrong.
- When you can tell it's landing badly
That came out worse than I meant it. Let me try again.
- Asking for something directly
I'm not hinting at this — I'm asking. Would you be willing to?
- When you need them to just listen
I don't need this solved. I need you to hear it. Is that alright?
- When you don't know what you want yet
I haven't worked out what I'm asking for. Can I think out loud for a minute?
Separate the event from the response
For one thing you need to say and have been saying badly. Written down first, because the separation is almost impossible to hear in your own head.
Real questions
Why do people misunderstand what I say?
Because they aren't receiving your words, they're rebuilding meaning from them using their own filters, assumptions and threat detection — so some distortion is structural rather than a failure of your phrasing. What reduces it: being specific rather than emphatic, separating what happened from how you felt about it, and asking them to say back what they understood before either of you responds. That last one catches the reconstruction while it's still correctable.
How do I say something difficult without starting a fight?
Lead with the specific event and the effect, not with a characterisation of them. “When this happened, it cost me this” gives them something to work with. “You always do this” gives them something to defend, and defending is what will happen, because their defence fires before any evaluation of whether you're right. Then say what you're asking for, and stop talking — the pause is where their actual response lives.
Why does being specific work better than being emphatic?
Because emphasis is easy to dispute and specifics aren't. You never help invites a counter-example, and now you're arguing about the evidence instead of the problem. I did the washing up every night this week can't be argued with in the same way. The general version also reads as a judgement about character, which is what triggers the defence — and once the defence is running, nothing you say is being evaluated on its merits.
How do I actually listen rather than waiting to talk?
Give yourself a job that makes it impossible to be composing your reply — the job is being able to say their position back well enough that they agree you've got it. That's a genuinely different activity from waiting, and people can feel the difference immediately. You'll also discover how often your first attempt is wrong, which is useful: it means a good proportion of the arguments you've had were about something they didn't say.
Why do I go silent instead of saying what I need?
Usually because saying it directly feels like exposure — a request can be refused, and a hint can be retracted. So the need goes out as tone, or as a mood, or as nothing, and then goes unmet, which confirms that asking is pointless. The way out is unglamorous: ask explicitly, and name that you're doing it. “I'm not hinting at this, I'm asking” costs one sentence and removes the ambiguity that was doing the damage.
Can you ever communicate perfectly?
No, and aiming at it causes its own problems — over-explaining, pre-empting every misreading, exhausting conversations that still land wrong. The channel distorts by design, so some loss is permanent. What's available is reducing it: specifics over emphasis, the event separated from the response, the request stated rather than implied, and checking what arrived. That's a considerable improvement over most conversations, and it's reachable.