You will be able to spot and fix the parts of a written message that read as cold, curt or passive aggressive.
You send your manager a draft at 6pm and ask for comments. At 9.40pm a reply arrives: "Ok." You spend the evening wondering. Ok, it's fine? Ok, I'll look later? Ok, I'm annoyed you sent this so late? The next morning your manager mentions the draft in passing and says it was good. The "ok" meant nothing at all, but it cost you an evening.
Now turn it round. How many of your own messages have landed like that on someone else's phone?
When you speak, your voice, face and timing carry a lot of the meaning. "Can you redo this?" said with a smile and a shrug is a small request. The same words typed into a chat, with nothing around them, can read as a complaint.
In writing, the reader has to supply the tone themselves, and they fill the gap with whatever they bring to it: their mood, how busy they are, how they feel about you, and what has happened between you before. When they're tired, anxious or new to the team, they often choose the less generous reading. A short message from someone senior gets read as displeasure. A short message from a stranger gets read as rudeness.
You can't control the reader's mood, but you can leave less of the tone for them to guess.
One-word replies are the most common cause of accidental coldness at work. "Ok." "Noted." "Fine." "K." From a peer you know well, they're efficient. From someone more senior, or someone the reader hasn't met, they can read as irritation or as a brush-off.
"Noted" deserves a special mention because it's so common in Singapore offices, where it's meant as a neutral acknowledgement. Many people read it that way. Some, especially those newer to local workplaces, read it as "I have heard you and I don't care". If you use it, a few more words remove the doubt: "Noted, thanks. I'll update the schedule by tomorrow."
The fix is rarely more than one clause. "Ok" becomes "Ok, thanks, looks good." "Fine" becomes "Fine by me, go ahead." The extra words take two seconds and tell the reader what you meant.
Some phrases look courteous on the surface but are widely read as irritation, whatever the writer intended.
"As per my last email" usually comes across as "you didn't read what I sent". "Gentle reminder" is meant to soften a chaser, but the word "gentle" often makes it sound pointed. "Please revert ASAP" can read as a demand, and "revert" in the sense of "reply" puzzles some readers from outside the region. "Kindly note" and "please be informed" sound stiff to many people. "Thanks in advance" can sound as if you've already decided they'll say yes.
None of these phrases is banned, and in some offices they're simply the house style. The point is that you can't control how they land. When you have a clearer alternative, use it.
Before: "Hi Ben, gentle reminder as per my last email, please revert on the budget figures ASAP."
After: "Hi Ben, I'm following up on the budget figures from my email on Monday. Could you send them by Thursday noon? I need them for the finance review on Friday. Let me know if anything's holding them up."
The second version is longer, but it does the work the first one only implies. It names the email, gives a deadline and a reason, and offers help. Ben has nothing to feel defensive about.
You don't need to pad every message. With a colleague you message ten times a day, short is fine, because you already have a shared history that fills the gap. Two situations call for more.
The first is a new relationship: someone you've never worked with, a new team, a client, a colleague in another country. They have no history to read your tone against, so give them one line of context or warmth. "Hope your first week is going well" or "Thanks for picking this up at short notice" costs nothing.
The second is bad news or a correction. "There are errors in your report" is accurate, and on its own it lands hard. "Thanks for turning this round so fast. I spotted two figures in section 3 that don't match the source file. Could you check them before it goes out?" says the same thing and keeps the relationship intact.
The habit that catches most of this is a single reread, done as if you were the recipient. Read it as someone having a bad day, from someone they don't know well. Does any line sound like a complaint? Is there a one-word reply that could be read two ways? Is there a phrase you picked up from someone else's emails that you wouldn't say out loud?
This matters more in a mixed team. A message read in a second language, or by someone from a culture that expects more indirect requests, has even less tone to go on. Module 8 goes into that in detail.
You have almost certainly received messages that felt rude when the sender probably meant nothing by them. Those are useful raw material, because you can see exactly which words caused the reaction. Pick two of them for the activity below.
Find two messages you received that felt rude, rewrite each so the same request reads neutral, and note what you changed.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).