0.3When to use what? (email vs chat vs meeting)
The essentials in 30 seconds
- Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
- The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
- Favoring asynchronous (message, email) preserves everyone's concentration.
Nassim thread — When to use what? (email vs chat vs meeting)
A customer asks for a quote, a colleague asks a quick question and three people have to decide on a schedule. Nassim must choose between email, chat and meetings without multiplying channels.
Continuation of the common thread: a digital services SME in Algiers structures its exchanges.
1. Understand
The question that resolves 80% of communication overload: which channel for which message? An e-mail for a formal or external request; a Teams chat for a quick question between colleagues; a meeting for what requires a real exchange; a team channel for what concerns everyone and must remain accessible. The wrong channel is the colleague drowned in 40 emails that should have been 3 chat messages — or the other way around.
You will build your personal rule of choice based on four criteria: formal or informal? urgent or deferred? a recipient or a team? trace necessary or not? It is the compass that makes the entire guide suite effective instead of noisy.
2. Key points
Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
Favoring asynchronous (message, email) preserves everyone's concentration.
The right channel is not a question of taste: it is respect for collective time.
🔎 Concrete example — Concrete example — When to use what? (email vs chat vs meeting)
Look back at your last 10 communications (emails, chats, meetings): how many were in the RIGHT channel? (be honest).
For each, apply the 4 questions: formal/informal? urgent/delayed? individual/team? trace necessary?
Spot the error that comes up: too many emails that should have been chats? too many meetings that should have been a message?
Write your rule in one sentence (e.g. “chat for < 2 lines between us, email for anything involving, meeting only to decide together”).A simple compass that immediately lightens your load — and that of your colleagues.
Section vocabulary
- The formal, asynchronous, traceable channel: official requests, external communication, messages which must leave a lasting listenable trace.
Simple example: Nassim uses “E-mail” in his daily life for when to use what? (email vs chat vs meeting).
What it is not: Confusing “E-mail” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Teams chat (private)
- Rapid, informal exchange between people: short questions, immediate coordination — not for decisions to be archived.
Simple example: Nassim uses “Chat Teams (private)” in his daily life for when to use what? (email vs chat vs meeting).
What it is not: Confusing “Chat Teams (private)” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Teams Channel
- The TEAM conversation, visible to all its members and persistent: what concerns the collective and must remain consultable.
Simple example: Nassim uses “Canal Teams (team)” in his daily life for when to use what? (email vs chat vs meeting).
What it is not: Confusing “Canal Teams (team)” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Meeting
- Synchronous exchange should be reserved for the real need for discussion/decision: neither to inform (a message is enough), nor for what is written.
Simple example: Nassim uses “Reunion” in his daily life for when to use what? (email vs chat vs meeting).
What it is not: Confusing “Meeting” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
- Asynchronous vs. Synchronous
- Asynchronous (email, message) = everyone responds at their own pace; synchronous (meeting, call) = everyone at the same time — expensive, to be measured.
Simple example: Nassim uses “Asynchronous vs. synchronous” in his daily life for when to use what? (email vs chat vs meeting).
What it is not: Confusing “Asynchronous vs. synchronous” with a setting that has no effect on the organization of work.
Reflex: Does this clarify who does what, where and when?
In practice — Building your communication compass
- Look back at your last 10 communications (emails, chats, meetings): how many were in the RIGHT channel? (be honest).
- For each, apply the 4 questions: formal/informal? urgent/delayed? individual/team? trace necessary?
- Spot the error that comes up: too many emails that should have been chats? too many meetings that should have been a message?
- Write your rule in one sentence (e.g. “chat for < 2 lines between us, email for anything involving, meeting only to decide together”).
Script ready to say — When to use what? (email vs chat vs meeting) (25 sec)
“Choose the right channel: email (formal/asynchronous), Teams chat (quick), meeting (exchange), channel (team). I rely on this key point: e-mail = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.”
Short formulation, to be adapted to the recipient and the context.
Copy and paste template — checklist “When to use what?” (email vs chat vs meeting)”
CHECKLIST — When to use what? (email vs chat vs meeting)
1. Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
2. The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
3. Favoring asynchrony (message, email) preserves everyone's concentration.
4. The right channel is not a question of taste: it is respect for collective time.
EXPECTED RESULT: A simple compass that immediately lightens your load — and that of your colleagues.Express version
Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
As a team
The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
Point of vigilance
Favoring asynchronous (message, email) preserves everyone's concentration.
Control before distribution
A simple compass that immediately lightens your load — and that of your colleagues.
✓ Best practices
- Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
- The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
- Favoring asynchronous (message, email) preserves everyone's concentration.
✗ Common pitfalls
- Treat “When to use what?” (email vs chat vs meeting)” by intuition without checking the context.
- Multiply channels and notifications for the same subject.
- Send or share without rereading recipients and rights.
Key takeaways
- Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
- The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
- Favoring asynchronous (message, email) preserves everyone's concentration.
- The right channel is not a question of taste: it is respect for collective time.
48 hour challenge — apply tomorrow
Put “Building your communication compass” into practice in a real case of Nassim’s SME: Look back at your last 10 communications (emails, chats, meetings): how many were in the RIGHT channel? (be honest). Time it for 20 minutes and note what has changed.
- I can explain and apply: Email = formal/external/traceable; chat = fast/internal; channel = team/persistent; meeting = decide together.
- I can explain and apply: The meeting is the most expensive channel (time × participants): to be reserved for the real need for exchange.
- I can explain and apply: Favoring asynchrony (message, email) preserves everyone's concentration.
Frequently asked questions
Could a meeting have been an email?
Simple test: if the objective is to INFORM or collect opinions without debate, a message/email is enough. The meeting is justified when it is necessary to discuss, arbitrate or co-construct directly. Many recurring meetings do not pass this test.
Private chat or team channel: how to decide?
If the information could be useful to other members of the team (now or later), it is a channel — the private buries the knowledge. Private chat is reserved for truly personal or trivial 1-to-1 meetings.
What reflex to adopt for “When to use what?” (email vs chat vs meeting)”?