Why your message sounded ruder than you meant

Spot the parts of a written message that read as cold, curt or passive aggressive, and fix them.

At 6pm you email a draft to your manager and ask what they think (an invented example). Their reply comes in at 9.40pm and says only "Ok."

You spend the rest of the evening trying to work out what it meant. Perhaps the draft is fine. Perhaps they'll read it properly later. Perhaps they're annoyed you sent it so late in the day. The next morning your manager mentions the draft in passing and tells you it was good. The "Ok" carried no meaning at all, and you lost an evening to it. Some of the messages you send will have reached other people the same way, and you are unlikely to know which ones.

How tone goes missing between screen and reader

When you say a sentence out loud, your voice, your expression and your timing carry much of its meaning. Said with a smile and a shrug, a sentence can be a small request. The same words typed alone into a chat window can read as a complaint. On the page, it is the reader who decides what tone a message has.

They decide using whatever they have on hand: their mood, how busy the day is, what they think of you, and anything that has happened between you before. People who are tired, anxious or new to a team often settle on the less generous reading. Brief messages from senior people are usually taken as displeasure. Brief messages from people the reader doesn't know are usually taken as rudeness. You can't control the reader's mood, but you can write so they have less tone to guess at.

Short replies, "Noted" and the one-clause fix

At work, the most common source of accidental coldness is the one-word answer: "Ok.", "Noted.", "Fine.", "K." Accidental coldness means a reply that sounds cold although the writer meant nothing by it. From a peer the reader knows well, these replies read as efficient. From someone more senior, or someone the reader has never met, they can come across as irritation or a brush-off.

Noted needs its own mention. Singapore offices use it all the time as a neutral acknowledgement, and plenty of readers take it as neutral. Others, particularly people who haven't worked in local offices for long, read it as "I have heard you and I don't care". A few more words settle it: "Noted, thanks. I'll update the schedule by tomorrow."

A one-word reply seldom needs more than a single extra clause to fix it. The clause states what you actually meant, such as thanks, approval, or the next thing you'll do and when. "Ok" becomes "Ok, thanks, looks good." "Fine" becomes "Fine by me, go ahead." The extra words take about two seconds to type, and the reader no longer has to guess your meaning.

Polite-sounding phrases that land badly

Some familiar phrases look courteous but are commonly read as irritation, whatever the writer intended:

"As per my last email" tends to be read as "you didn't read what I sent". "Gentle reminder" is meant to soften a chaser, yet the word "gentle" often makes it sound pointed. "Please revert ASAP" can come across as a demand. Using revert to mean "reply" is normal in this region, but it confuses some readers from elsewhere. "Kindly note" and "please be informed" strike many people as stiff. "Thanks in advance" can suggest you've already decided the reader will agree.

None of these is banned, and some offices use them as their standard house style. You have no say over how they're received, though, so choose a clearer wording whenever one is available.

Ben is a colleague who still owes you the budget figures. A chaser put together from stock phrases might read: "Hi Ben, gentle reminder as per my last email, please revert on the budget figures ASAP."

Here it is rewritten: "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 rewrite is longer. It points to the specific earlier email and the day it was sent, asks for the figures by a set deadline, explains why that deadline matters, and invites Ben to mention anything that is blocking him. That leaves Ben no reason to get defensive. When you catch yourself about to type a stock phrase, build the message from those four parts instead.

When a message needs extra warmth

Plenty of messages are fine short. If you message a colleague ten times a day, your history together supplies the tone.

Two cases call for extra warmth. The first is a new relationship: someone you haven't worked with before, a new team, a client, or a colleague based in another country. They have no history to judge 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" are examples, and they cost you nothing.

The second case is bad news or a correction. "There are errors in your report" is accurate, but sent on its own it lands hard. A gentler version carries the same information and keeps the working relationship intact: "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?" It opens with appreciation, names exactly what is wrong, and ends with a clear request.

Reading it once as the recipient

One habit catches most of these problems. Before you send, read the message once from the recipient's side, as someone having a bad day who doesn't know you well. Check three things: whether any line sounds like a complaint, whether a one-word reply could be read two ways, and whether you've borrowed a phrase from other people's emails that you would never say out loud.

This reread 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 covers in detail how messages are read in mixed teams, including by readers working in a second language and readers from cultures that expect more indirect requests.

You have almost certainly received messages that felt rude when the sender most likely meant nothing by them. These are useful raw material, because you can see exactly which words caused your 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.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).