0.1The communication model (sender → receiver)
The essentials in 30 seconds
- One single chain: sender → message → channel → receiver → feedback — the analysis grid for every misunderstanding.
- Understood counts, said is not enough: what matters is not what you say, but what is understood.
- 3 noises: physical, semantic (jargon, ambiguity) and psychological — only feedback proves it got through.
Running mini-case — Yasmine and the too-brief quote
Yasmine, sales assistant in a 12-person service SME in Algiers, sends a two-line quote with no greeting between two calls. The client reads coldness into it and is slow to reply. Rereading her message with the model, Yasmine spots the breakdown: encoding "efficiency", decoding "reproach", a written channel with no tone, zero feedback requested.
This same case runs through the course, the diagram, the script and the 48h challenge — and continues in 0.2, 0.3 and 0.4.
1. One model for every communication
From a simple email to a major presentation, every communication follows the same model: a sender encodes a message, sends it through a channel to a receiver, who decodes it and returns feedback. This isn't abstract theory — it's a universal analysis grid you can apply to any professional misunderstanding.
Any link can fail: a sender who encodes poorly (jargon, ambiguity), a mismatched channel (a sensitive topic sent by email), a distracted receiver, or a total absence of feedback. Spotting where the chain broke is already knowing how to fix it.
2. Feedback, the only real judge
A good communicator doesn't ask "did I speak well?" but "was my message understood the way I intended?" — that's the whole point of feedback. Without it, you communicate blindly: you assume the message got through without ever checking.
Feedback can be verbal (a rephrase, a question) or nonverbal (a nod, an uncomfortable silence). Actively asking for it ("is that clear?", "what will you take away from this?") turns a monologue into a real exchange.
3. The noise that distorts a message
Between what the sender wants to say and what the receiver understands, noise creeps in. It can be physical (a noisy environment, a bad connection), semantic (jargon, ambiguous words, unfamiliar acronyms) or psychological (emotion, bias, fatigue, distraction).
An experienced sender anticipates likely noise: choosing a calm channel for a sensitive topic, defining jargon up front, and staying alert to signals (a closed face, repeated questions) that show noise is blurring the message.
🔎 Concrete example — A brief email mistaken for coldness
A manager sends a two-line email with no greeting, trying to move fast between two meetings. The employee who receives it reads an implicit reproach and spends the afternoon anxious.
Analysis: the sender encoded "efficiency"; the receiver decoded "coldness" — the written channel, without tone or facial expression, amplified the ambiguity.
Fix: one line of context ("quick note between meetings, but...") or an oral channel for sensitive topics would have avoided the psychological noise.
Section vocabulary
- Sender / receiver
- The sender produces and sends the message; the receiver gets it and interprets it. Roles constantly swap in a dialogue.
Simple example: Yasmine (sender) sends the quote; the client (receiver) interprets it, then replies and becomes the sender.
What it is not: believing the sender talks and the receiver merely obeys without ever responding.
Reflex: before sending, ask "who is receiving, and what will they understand?".
- Message
- The information being conveyed, as it is encoded (words, tone, gestures) — not necessarily as it is received.
Simple example: The two-line quote meant "done quickly"; it was received as "curt".
What it is not: confusing the intention ("I meant to be efficient") with the message received.
Reflex: reread every important message through the recipient's eyes.
- Channel
- The medium of transmission: face-to-face speech, phone, email, video call, writing. Each channel has its own strengths and limits.
Simple example: Yasmine chooses a call rather than email to announce a sensitive extra cost.
What it is not: sending a sensitive topic by email out of habit, because "it's faster".
Reflex: sensitive or emotional topic → prefer speaking.
- Feedback
- The receiver's response that proves — or not — proper understanding. Without feedback, you don't know if the message got through.
Simple example: "What will you take away from this?" — the client restates the date and amount, Yasmine confirms.
What it is not: ending with "is that clear?" without leaving time to answer.
Reflex: ask for active feedback after every important message.
- Noise
- Any disturbance that distorts the message: physical noise (environment), semantic (jargon, ambiguity), psychological (emotion, bias).
Simple example: An unexplained internal acronym blocks the client: semantic noise.
What it is not: reducing noise to a mere background sound or voice volume.
Reflex: faced with a misunderstanding, name the noise before blaming the person.
In practice — Analyzing a failed communication
- Think back to a recent professional misunderstanding (an email taken the wrong way, a misunderstood instruction).
- Break it down using the model: who was the sender, the receiver? What was the intended message? Through which channel?
- Identify the noise: jargon? the wrong channel (a sensitive topic sent by email)? emotion? no feedback?
- Mentally replay the scene removing the main source of noise: which channel or wording would have avoided the misunderstanding?
Ready-to-use script — locking in understanding (30s)
"Let me sum up in one sentence, and you tell me if that's right: we go with quote B, starting Sunday, 30% deposit. What will you take away from this?"
Say at the end of a call or an important email: a requested rephrase beats a polite "is that clear?".
Copy-paste template — model check before sending
INTENDED MESSAGE (1 sentence): _______________
RECIPIENT (what do they know? what do they fear?): _______________
CHOSEN CHANNEL (and why): _______________
LIKELY NOISE (jargon? emotion?): _______________
ADDED ANTI-NOISE LINE: _______________
FEEDBACK REQUESTED: _______________Small business / tight budget
With no tools or budget: add one line of context to every brief message and ask "what will you take away from this?" before hanging up.
Algerian SME
Clients mixing French, Arabic and technical acronyms: define each acronym the first time you use it and confirm dates and amounts in figures and words.
Sensitive message
Delicate news (delay, extra cost, refusal): ban the curt email, switch to voice or video and allow time for feedback.
Noisy environment
Workshop, open space, bad connection: move the exchange, mute notifications, restate in writing after speaking.
✓ Best practices
- Before an important message, ask yourself which channel minimizes the risk of noise for THIS specific topic.
- Actively ask for feedback ("is that clear to you?") rather than assuming it's a given.
- Define any technical term or acronym the first time you use it with a non-specialist audience.
✗ Common pitfalls
- Confusing "having spoken" with "having been understood": these are two radically different things.
- Choosing a channel out of habit rather than fit for the message (a sensitive topic sent by email).
- Ignoring weak signals of noise (an uneasy silence, a recurring question) that indicate a misunderstanding.
Key takeaways
- Communicating = sender → message → channel → receiver → feedback.
- What matters isn't what you say, but what is understood.
- "Noise" (jargon, emotion, the wrong channel) distorts the message.
- Feedback is the only way to verify the message got through.
48h Challenge — apply tomorrow
Take 1 important message to send tomorrow and run it through the model check (template above): channel, likely noise, feedback requested. Note the reply you get: clearer than usual?
- I can name the 5 links of the model without hesitation.
- I can name the 3 families of noise with an example.
- I've asked for active feedback on a real message.
Frequently asked questions
Why are my messages so often misread in writing?
Writing removes para-verbal (tone) and nonverbal (facial expression) cues, which carry much of the meaning and intent. Without them, the reader fills in the blanks with their own mood. That's why choosing the right channel matters: for a sensitive or emotional topic, speaking is often better than email.
Isn't feedback just for managers?
No: here, "feedback" means any sign of understanding — a nod, a rephrase, a relevant reply. Asking for it ("is that clear?", "what will you take away?") is a good communicator's reflex at every level.
Yasmine sends a curt two-line quote; the offended client stops replying. Where did the chain break first?