1.4Instant messaging (Teams) & short communication
The essentials in 30 seconds
- IM = short and fast: it complements email, doesn't replace it — choose the right channel.
- Self-contained: one message = one idea, context + question in a single send.
- Asynchronous: channel for shared, private for targeted, presence status respected.
Running mini-case — Yasmine and her five messages for one question
Yasmine sends "Hello", "got 2 min?", "it's about file X", "I have a question", then finally the real question: five notifications for one answer. She adopts the self-contained message — "Hello, quick question on file X: can you confirm the delivery date? Thanks!" — and gets an immediate reply in a single exchange.
Final episode of cases 1.1-1.3 — Yasmine moves from email to instant messaging.
1. A tool for short and fast
Instant messaging (Teams, Slack…) has taken over daily work: ideal for short and fast exchanges, it becomes counterproductive when used for everything, including topics that would be better suited to an email or a call.
The key skill is knowing how to choose the right channel: a message for a quick question, an email for a formal record, a call for a complex or sensitive topic.
2. Different codes from email
Its codes differ from email: maximum conciseness, one message = one idea, rather than five successive messages ("hi… got a minute?… actually…"). A self-contained message, with context included, beats several fragments.
The distinction between a team channel (visible to everyone) and a private message structures proper use: shared information goes in the channel, a targeted topic stays private.
3. Respecting everyone's pace
Asynchronous communication doesn't require an immediate reply: everyone answers when they can, which preserves focus. Presence status (available, busy, away) signals availability without needing to say it explicitly.
Well used, instant messaging streamlines teamwork; poorly used — too many notifications, expecting an instant reply — it fragments everyone's attention.
🔎 Concrete example — Five messages instead of one
Message 1: "Hi". Message 2: "got a minute?". Message 3: "it's about file X". Message 4: "I have a question". Message 5: the actual question, finally asked.
Self-contained alternative: "Hi, a quick question about file X: can you confirm the delivery date? Thanks!"
Gain: one notification, an immediate reply is possible, less fragmentation for both parties.
Section vocabulary
- Instant messaging
- A tool for short, near real-time exchanges (Teams, Slack). Complements email, doesn't replace it.
Simple example: Yasmine asks a quick question on Teams instead of a formal email.
What it is not: handling a sensitive dispute entirely in short messages.
Reflex: short and fast = IM, record and formal = email.
- Channel vs private message
- A team channel is visible to the group (shared info); a private message stays between two people (targeted topic).
Simple example: Yasmine announces the delivery date in the channel, and follows up a delay privately.
What it is not: settling a sensitive individual matter in the team channel.
Reflex: info useful to all = channel, targeted topic = private.
- Channel choice
- Deciding on the right medium based on stakes: IM (fast), email (record), call (complex/sensitive), meeting (group decision).
Simple example: Yasmine switches to a call when the exchange exceeds four back-and-forths.
What it is not: doing everything in IM out of habit, even decisions to record.
Reflex: stuck topic = "shall I call you?".
- Presence status
- An indicator (available, busy, away) that signals your availability: respect it in others, keep yours up to date.
Simple example: Yasmine doesn't follow up a colleague showing "busy" in a meeting.
What it is not: demanding an immediate reply despite an away status.
Reflex: busy status = deferred reply accepted.
- Asynchronous
- Communication with no expected immediate reply: everyone answers when they can, preserving focus.
Simple example: Yasmine writes "not urgent, reply this afternoon" to set the expectation.
What it is not: following up after 5 minutes of silence on a non-urgent message.
Reflex: state the expected reply time.
In practice — Choosing the right channel, writing short
- List your last 5 work exchanges: for each, was the channel right (IM / email / call / meeting)?
- Phrase a typical question as one clear, self-contained message (context + question), rather than 5 messages like "hi… got a minute?…".
- Distinguish: does this info serve the whole team (channel) or one person (private message)?
- When a topic drags on in messages, switch to a call: "this will be simpler by voice, mind if I call?".
Ready-to-use script — self-contained Teams message
"Hello, quick question on file X: can you confirm the expected delivery date? Not urgent, a reply this afternoon is enough. Thanks!"
Send in a single message: greeting + context + precise question + reply time, without fragmenting.
Copy-paste template — self-contained short message
GREETING + CONTEXT (file / topic): _______________
PRECISE QUESTION (1 idea): _______________
EXPECTED REPLY TIME: _______________
CHANNEL (team / private): _______________
SWITCH IF STUCK ("shall I call you?" yes / no): _______________Small business / tight budget
Without Teams: apply the same rule on business WhatsApp — one single complete message with context, not five fragments, and silence respected in the evening.
Algerian SME
With dropouts, travel and staggered hours: write async by default ("reply when you can, before Thursday") and team channel for shared info.
Notification-flooded team
Mute group notifications, keep direct mentions: one self-contained message with @name replaces ten follow-ups.
Slipping topic
After three back-and-forths with no agreement: stop writing, suggest a 5-minute call then summarize the decision by email for the record.
✓ Best practices
- Write your full question (context + ask) before sending, rather than in several fragmented messages.
- Respect others' presence status: a "busy" status doesn't call for an immediate follow-up.
- Switch to a call as soon as an exchange goes beyond three or four back-and-forths without clarity.
✗ Common pitfalls
- Sending "got a minute?" with no topic, forcing the other person to answer before even knowing the request.
- Handling a complex or sensitive topic entirely through short messages, risking cascading misunderstandings.
- Expecting an instant reply to a message sent outside working hours or during a marked-busy meeting.
Key takeaways
- Instant messaging serves short and fast, not everything.
- Choose the channel: IM (fast), email (record), call (complex/sensitive).
- Team channel = shared info; private message = targeted topic.
- A self-contained message beats ten "got a minute?" pings.
48h Challenge — apply tomorrow
Rephrase your next 3 Teams questions as 1 self-contained message (context + question + time) with the template above. Count the notifications saved.
- I can name the right channel by stakes (IM / email / call).
- I can write a self-contained message in a single send.
- I've moved a stuck exchange to a call + summary.
Frequently asked questions
Should I reply immediately to an instant message?
No, unless it's a real emergency. Instant doesn't mean immediate: replying when you can preserves your focus. Use presence statuses and, if needed, reply "I'll look at this this afternoon" to set a clear expectation.
When is email better than a Teams message?
As soon as you need a record (a decision, a commitment, reference information), there are several recipients at different times, or the content is long/structured. Messaging, on the other hand, excels at brief, informal, in-the-moment exchanges.
Which instant message is most effective?