0.4Adapting your message to your audience
The essentials in 30 seconds
- Start from the other person, not yourself: what do they know, expect, worry about?
- 3 expectations: leadership = summary and impact, technical = precision, client = reassurance and clarity.
- Translate without betraying: adapt form and detail, never the substance.
Running mini-case — Yasmine and the delay, in three versions
A service runs two weeks late. Yasmine delivers the same fact in three versions: to the manager, the impact and the decision ("no extra cost, keep the announced date?"); to the technician, the cause and plan B; to the client, the new guaranteed date and the quality commitment. Same substance, three forms — and three satisfied counterparts.
Final episode of cases 0.1-0.3 — Yasmine adapts to the audience.
1. Start from the other person, not yourself
The same content isn't delivered the same way to a client, a technical expert, or an executive. Adapting your message — vocabulary, level of detail, angle, channel — isn't manipulation: it's respect and effectiveness.
The right reflex is to start from the other person ("what do they know? what do they expect? what worries them?") rather than from yourself and your own priorities as a communicator.
2. Three profiles, three expectations
An executive wants the essentials and the impact ("what benefit, what risk?"): they have neither the time nor the need for technical detail. A technical expert, on the contrary, wants precision: over-simplifying frustrates them and undermines credibility.
A client wants to be reassured and understood: they expect clear language, focused on what concerns them, not on the company's internal workings. Knowing how to adjust your register to these three audiences is what sets seasoned communicators apart.
3. Translating without betraying
Jargon, useful among experts, becomes noise for a non-specialist: it needs to be translated, not stripped of meaning. Presenting information from the audience-oriented benefit — what they gain, what problem gets solved — makes the message instantly relevant.
Adapting the form never means betraying the substance: the facts and the honesty stay identical, only the way they're presented changes depending on who's listening.
🔎 Concrete example — A project delay, three versions
A project runs two weeks behind schedule. The same fact must be communicated to three different audiences on the same day.
Leadership: "Project X will be 2 weeks late; limited schedule impact, no extra cost. Decision needed: keep the announced launch date?"
Technical team: "The delay comes from component Y not being delivered; we're switching to backup plan B tested last week, detailed actions below."
Client: "Your delivery is pushed back by two weeks to guarantee quality; new confirmed date: the 15th."
Section vocabulary
- Adaptation (register)
- Adjusting vocabulary, tone and level of detail to the profile and expectations of the recipient.
Simple example: Yasmine tells the manager "no extra cost" and the technician "we switch to plan B".
What it is not: sending the same generic email to all three audiences without changing anything.
Reflex: before writing: "what does this person know, what do they expect from me?".
- Target audience
- The person or group the message is addressed to. All preparation starts by identifying them.
Simple example: For the delay: manager, technician and client — three targets, three versions.
What it is not: writing first then wondering afterwards "by the way, who was this for?".
Reflex: name the target at the top of every message.
- Level of detail
- The amount of information suited to the audience: a summary for a decision-maker, precision for an operational role.
Simple example: Two sentences and a decision for the manager; causes and actions for the technician.
What it is not: drowning the executive in detail or frustrating the technician with a fuzzy summary.
Reflex: decision-maker = impact + decision; operational = causes + actions.
- Jargon
- Specialist vocabulary. Useful among experts, it becomes noise for a non-initiate: translate it.
Simple example: "Component Y" becomes "a part of your file" for the client.
What it is not: keeping internal acronyms with a client to "look professional".
Reflex: define or translate every trade term for a non-initiate.
- Audience-oriented benefit
- Presenting information from the angle of what interests the other person (their gain, their problem solved).
Simple example: To the client: "delivery pushed back to guarantee quality, confirmed date the 15th".
What it is not: telling them about internal workings instead of answering the client's need.
Reflex: end every client message with "what this changes for you".
In practice — Adapting one message for three audiences
- Pick a piece of information to communicate (e.g. a project delay). Write it "raw" first.
- Write the LEADERSHIP version: 2 sentences, the impact and the decision expected, no technical detail.
- Write the TECHNICAL TEAM version: precise causes, concrete actions, professional vocabulary.
- Write the CLIENT version: reassuring, focused on what concerns them (new deadline, commitment made).
Ready-to-use script — announcing a delay to a client (30s)
"I'd rather tell you frankly: your delivery is pushed back by two weeks, to the 15th, to guarantee the quality we promised. Here's what we're doing until then, and I'll keep you posted every Tuesday."
Say aloud for a sensitive topic: identical facts, reassuring form focused on the client.
Copy-paste template — same info, three versions
RAW INFO: _______________
LEADERSHIP VERSION (impact + decision): _______________
TECHNICAL VERSION (causes + actions): _______________
CLIENT VERSION (new deadline + commitment): _______________
COMMON SUBSTANCE CHECKED (identical?): _______________Small business / tight budget
With two or three people: one base message, then two sentences of adaptation per recipient — no need for three separate documents.
Algerian SME
Manager often traveling (supplier, bank, wilaya): ultra-short leadership version by voice message, technical detail kept for the team at the office.
Mixed audience in a meeting
Aim for a summary everyone can understand, then offer detail "on request" (an appendix, a Q&A slot) so no one is excluded.
Non-specialist client
Translate each trade term in passing ("component Y is the part that…") without weighing things down, and end on the client benefit.
✓ Best practices
- Before writing, always ask yourself: "what does this person already know, what do they expect from me?"
- Keep the same factual foundation for all audiences; only vary the form and level of detail.
- Offer technical detail "in an appendix" or "on request" rather than imposing it on everyone.
✗ Common pitfalls
- Talking "technical" to a busy executive, or "strategy" to an operational person who wants concrete instructions.
- Using the same generic email for leadership, the team, and the client with no adaptation at all.
- Confusing adaptation with dishonesty: changing the substance depending on the audience, not just the form.
Key takeaways
- Adapting your message means starting from the other person, not yourself.
- Leadership = summary and impact; technical = precision; client = reassurance.
- Jargon clarifies among experts and confuses non-initiates.
- Present information from the angle of the benefit for the listener.
48h Challenge — apply tomorrow
Take 1 real piece of info to communicate and write 2 versions (e.g. leadership + client) with the template above. Send the right version to the right person.
- I can name the 3 expectations (leadership, technical, client).
- I can translate jargon without betraying the substance.
- I've adapted 1 message into 2 versions.
Frequently asked questions
Isn't adapting my message just being dishonest?
Not at all: the substance (the facts, the honesty) stays identical; only the form changes to be understood. Talking "technical" to a busy executive or "strategy" to an operational person is, on the contrary, ineffective and a bit self-centered. Adapting means serving the other person's understanding.
How do I adapt when addressing a mixed audience?
Aim for the highest level of summary that everyone can understand, then offer detail "on request" (an appendix, a Q&A slot, a supporting document). You can also briefly explain a technical term in passing, without weighing things down, so no one is excluded.
Yasmine must announce a two-week delay to the rushed manager, the technician and the client. What does she do?