Most of us learned to write for teachers. You were marked on grammar, structure, and whether the argument held together, and your reader was a person paid to read carefully all the way to the end.

Work is nothing like that. Your reader is busy, half-distracted, reading on a phone between two meetings, and under no obligation to reach your final paragraph. They may be in another country, working in their second or third language, and they will decide within a few lines whether this deserves their attention now, later, or never.

So the people who write well at work are rarely the ones with the tidiest grammar. They are the ones who understand the person on the other end. That understanding is a soft skill, and like every soft skill it can be practised.

Audience Awareness Does Most of the Work

Before the wording, before the structure, there is a question worth asking. Who is reading this, and what do they already know?

Get that wrong and no amount of polish saves you. Write to a specialist as though they were a beginner and you sound patronising. Write to a newcomer as though they were a specialist and they quietly give up somewhere in paragraph two, then ask a colleague to explain it later, which costs two people's time instead of one.

You can feel the difference when you read two versions of the same update. One assumes you know the background. The other spends a single sentence establishing it. The second version is longer and takes considerably less effort to read.

A few questions tend to sharpen this:

• What does this person already know, and what will they have to look up?
• What do they need from me: a decision, an action, an opinion, or just awareness?
• What are they likely to be worried about that I have not mentioned?
• If they read only the first two lines, would they still get the essential part?

That last question changes how people write more than any other piece of advice, because many workplace messages are read in fragments rather than start to finish.

Knowing What the Message Is Actually For

A surprising number of work messages have no clear purpose. They report activity without asking for anything, or they ask for something without quite saying so, or they raise a concern while carefully avoiding the word concern.

Being clear about intent is partly a writing skill and mostly a thinking one. If you cannot say in one sentence what you want the reader to do, know, or decide, the message is not ready to send.

Politeness sometimes works against clarity here. Softening a request until it reads as a gentle observation is a common habit and a well-meant one, but it leaves the reader guessing whether they have been asked to act. You can be warm and unambiguous at the same time. Say what you need, then say it kindly.

Restraint, and the Discipline of Cutting

Good workplace writing is mostly deleting.

The first draft of anything contains your thinking process. The context you gathered, the options you weighed, the caveats you want on record. Your reader needs the conclusion and enough of the reasoning to trust it. The rest belongs in your notes.

Cutting your own words takes a small act of ego management, which is why it sits closer to a soft skill than a technical one. The paragraph you are proudest of is often the one holding the message back.

Length also signals importance in ways people never intend. A three-line message reads as routine. A thousand-word one reads as a crisis, whatever the words themselves say.

Tone Travels Further Than You Think

Text strips out almost everything you rely on in person. No face, no voice, no pause before the difficult part. What survives gets interpreted by a reader who fills in the missing signals from their own mood, their own culture, and whatever else happened to them that morning.

Brevity reads as efficiency to one person and coldness to another. Directness that is entirely normal in one working culture lands as rudeness in a second, and the indirectness that counts as courtesy in a third can read as evasiveness somewhere else. None of those styles is the correct one. They are conventions, and any international team holds several of them at once.

Which is why the strongest writers overstate warmth slightly and understate certainty slightly. A short acknowledgement before a correction. A reason attached to a deadline. A quick "I might be missing something" before a challenge. These cost a few seconds each and prevent a surprising amount of friction.

The problem compounds across time zones, where a misread message can sit unanswered for a full working day before anyone is awake to clear it up. Much of the practical guidance on keeping a distributed team aligned arrives at the same point: when colleagues cannot check a meaning quickly, the writing has to carry more of the relationship than it ever would in a shared office.

A Quick Check Before You Send

Question four catches most of the messages people go on to regret. Question five improves nearly everything else.

Disagreeing in Writing Without Doing Damage

Written disagreement is where communication skill shows most clearly, largely because the format works against you. There is no tone of voice to soften anything, the message can be forwarded to people you did not choose, and it stays on the record indefinitely.

A few habits help. Separate the idea from the person, so that you are questioning an approach rather than someone's judgement. State what you agree with first, honestly rather than as a formula, because readers can tell the difference. Ask a question where you would otherwise make an accusation, since "what happens if the numbers come in lower?" opens a conversation that "this forecast is unrealistic" closes.

And know when to stop writing. If a thread has gone three rounds without moving, the format has failed and a conversation is the answer. Recognising that moment is a skill in itself, and a more valuable one than most people give it credit for.

Writing for People Who Are Skimming

It is wise to assume your reader is scanning, because they usually are.

That assumption changes the shape of what you produce rather than the quality of it. The request moves to the top instead of arriving as a conclusion. Headings say what the section contains rather than teasing it. Dense blocks get broken up, and anything with steps becomes a list.

None of that is dumbing anything down. It is arranging the same content so a busy person can find the part they need, which is a courtesy rather than a compromise.

---

How the Skill Actually Develops

Nobody improves at this by reading about it, including here.

What works is narrower and slower. Reread your own messages a week later, once you have lost the context you had while writing them, and notice what no longer makes sense without it. Pay attention to which messages get quick, clean answers and which produce three clarifying questions, because that pattern is honest feedback arriving for free. Notice the colleagues whose writing you find effortless to read, then work out what they are actually doing.

Then ask someone you trust to tell you how you come across in writing. Most people have never once been told, and the answer tends to be mildly surprising.

None of this is about becoming a better writer in the literary sense. It is about becoming easier to work with, which is the thing written communication has been measuring all along.

---