Skills
Most work writing fails in the first two lines
A workplace reader is deciding whether to keep reading and what they are being asked to do, and the conventions of essay writing actively obstruct both.
By Tara Mukherjee3 min read

The reader is not the one you were trained for
Almost everyone arrives at work having learned to write for an examiner — someone obliged to read the whole thing, in order, who rewards a build-up and a conclusion at the end. Workplace readers are the opposite in every respect. They are not obliged to read it, they will scan rather than read, they are interrupted, and they are looking for one thing: what does this mean for me.
That single difference explains most bad work writing. The context-first structure that earned marks at school buries the point under three paragraphs of background, and the reader who abandons it after ten seconds leaves with nothing. It is not that the writing is unclear. It is correctly ordered for a reader who does not exist here.
Put the conclusion where the attention is
The fix is to lead with the outcome and the ask, then supply the reasoning underneath for whoever wants it. The launch is delayed by a week; here is why and what I need from you. We should choose the second option; the analysis follows. This feels wrong at first, as though you are giving away the ending, and that reaction is exactly the training that has to be unlearned.
The reason it works is that it lets every reader stop at the point where they have what they need. A senior person reads the first two lines and moves on. Someone who has to act reads the next paragraph. Someone who wants to check the reasoning reads to the bottom. One document serves three audiences, which is what a document circulated widely has to do.
It also protects you when the message is forwarded, which happens constantly and without warning. A message whose point is in the final line arrives at the next reader as a wall of context with no evident purpose.
Make the ask unmissable
A great deal of workplace writing fails not because it was unread but because the reader could not tell what was wanted. Requests get embedded in the middle of a paragraph, softened into near-invisibility, or left implied because it seemed obvious. Ambiguity resolves toward inaction, every time.
So state it separately, at the top or in its own line, with the person and the date attached. "Priya — can you confirm by Thursday whether the licence covers this?" is unmissable. "It would be good to understand the licence position" is a sentence that will be read, agreed with and forgotten by four people simultaneously, each assuming one of the others has it.
Length and the things that go unread
Length is not the enemy exactly, but unearned length is. Every sentence that restates the previous one, apologises, or explains why you are writing costs you attention you will want later for the part that matters. Cutting the opening paragraph entirely is the single most reliable edit in workplace writing, because it is nearly always throat-clearing.
A few mechanical things do most of the remaining work. Subject lines that state the outcome rather than the topic, so the message is findable in six months. Short paragraphs, because dense blocks get skipped on a phone. One subject per message, since a second topic buried in a long email is functionally invisible. Concrete nouns rather than abstractions, which is what makes writing sound like a person rather than a policy document.
Where it is worth spending real effort
Not everything deserves care. A quick coordinating message should take a minute. But three categories repay disproportionate effort: anything that will be read by someone senior enough that this is one of the few times they encounter your work, anything that will still be referred to in a year, and anything that has to persuade rather than inform.
Those are also the pieces that travel. A well-made document gets forwarded, and it carries your name into rooms you will never enter, which is one of the very few ways that work done by a junior person becomes visible at a distance. That is a real and slightly cynical reason to write well, alongside the honest one.
The honest one is that writing is how thinking gets tested. Vague understanding survives a conversation easily and does not survive being written down, because the act of ordering an argument on a page exposes the parts you were skating over. People who write regularly tend to find the holes in their own reasoning earlier than people who do not, and that is worth more over five years than any stylistic improvement.
Common questions
Is it rude to be that blunt in an email?
Directness and rudeness are different variables, and you can be extremely direct while remaining warm. Norms vary a great deal by culture and by organisation, so calibrate the greeting and the softening language to what you see around you, but do not let politeness push the actual point into the fourth paragraph.
How do I know if my writing is working?
Watch what happens after you send it. Replies that answer a question you did not ask, or that ask something you already covered, indicate structure problems rather than reader carelessness. If people consistently miss your requests, the request is not visible enough, whatever you think you wrote.
Should I use bullet points for everything?
Bullets are excellent for lists of parallel items and poor for arguments, because they hide the connections between ideas — which is often precisely the thinking you were meant to supply. A document that is entirely bullets frequently signals that the reasoning was never actually done.
Senior writer, After the First Job
Tara writes the explanatory pieces on first months, managing up, money at work and reads the small print so you do not have to.





