Written Communication: Email and Chat

Text carries no tone and no facial expression. The reader gets exactly what you wrote and nothing else. Written clearly, one message saves everyone's time; written vaguely, it generates three rounds of clarification. Over a year that gap becomes a reputation.

1. Email: structure is the whole game

The subject line should let someone triage from the inbox list:

• Weak: "Some questions about the project"
• Strong: "[Action needed] Q3 channel budget — please confirm by Thursday"

Tagging the action type ([Action needed], [FYI], [Done]) and putting the deadline in the subject is a high-return habit.

The body

1. Lead with the ask or the conclusion: "Could you approve the budget below by Thursday?"
2. Then the context, three to five lines.
3. List what you need, one action per bullet.
4. Describe attachments rather than leaving them to be discovered: "Attached is the detail sheet; the second tab has the channel split."

To, Cc, Bcc

• To = people who must act. If several people are in To, nobody owns it — name them: "Wang to approve the budget, Li to check section two."
• Cc = people who need to know but not act. Cc'ing someone's manager to apply pressure is visible for what it is.
• Bcc is for protecting recipient privacy on external sends. Using it to let a third party silently read a thread costs you a great deal of trust when discovered.
• Pause before Reply All. Does everyone need your "Got it"?

Tone. Keep courtesy to one line and get to the point. Useful patterns:

• Opening: Hi Sarah, / Dear Dr. Chen, (formal)
• Ask: Could you confirm the Q3 budget by Thursday?
• Close: Thanks, / Best regards,
• Nudge: Following up on my note below — is there anything you need from me to move this forward? (much softer than "As I mentioned earlier")

2. Chat: Slack, Teams, WeChat

The core tension: chat is cheapest for the sender and most disruptive for the receiver. Most of the etiquette exists to correct that asymmetry.

• Never send just "hi" and wait. Put the question in the first message: "Hi Wang — checking the integration slot for Wednesday: does morning or afternoon work for you?"
• One message per thought. Splitting a paragraph across seven sends means seven notifications.
• Be careful with voice notes. Fastest for you, slowest for the listener — not searchable, not skimmable, unusable in a meeting. Type for managers and clients. If you must, keep it under twenty seconds and add a text summary.
• @-mention precisely. Use @channel only when it genuinely concerns everyone.
• Match emoji to the room. Relaxed on your team channel, restrained with clients. Note that some symbols read differently across generations and regions — when unsure, use words.

Time boundaries

• Send non-urgent messages during working hours; almost every tool supports scheduled send, so use it.
• If you must write after hours, say so: "Not urgent — tomorrow is fine."
• Conversely, you are not obliged to answer instantly outside working hours unless your role carries an on-call expectation. Clarify which it is when you join.

When to stop typing and call: more than three rounds without resolution, anything involving emotion or disagreement, or genuine urgency. Re-explaining in text something that would take three minutes by voice is the most common time sink in remote work.

3. Habits that prevent a lot of trouble

• Put decisions in writing. After a call: "Confirming: option B, delivery Friday, I'll own the handoff. Correct me if I've got that wrong." This is standard practice, not distrust.
• Reread before sending — recipients, amounts, dates and attachments are where mistakes cost most.
• Never send angry. Save the draft, look again in twenty minutes. You will change it nearly every time.
• Assume anything you write may be forwarded. It often is. This single assumption fixes your wording, your claims and your urge to vent about a colleague.
• Acknowledge receipt. "Got it — you'll have it Thursday" costs nothing and stops the other person from having to track you.

Common mistakes

• Red, bold, all caps for urgency. All caps reads as shouting. If it's genuinely urgent, call.
• Pasting a long document into the body. Attach or link; keep the body to the summary and the ask.
• Escalating by Cc. It may work once; after that people route around you.
• Forwarding content — especially screenshots — without permission. Ask first. It is basic trust maintenance.

---

One line to remember: the only test for written communication is whether the reader finishes it knowing what they need to do and by when.