Why the Clearest Writer in the Room Usually Has the Most Clout
There is a particular look that crosses a UK office when someone sends a short, clear email. It is half surprise, half suspicion. Is that it? Did they really think about this? The longer version — the one with workstreams, alignment and a paragraph about socialising the draft — somehow feels more serious. That is the plain-English penalty: clear writing gets mistaken for simple thinking.
It is a daft trade-off. We mistake length for effort, jargon for expertise and fog for sophistication. Then we wonder why nobody reads past the second paragraph.
The jargon tax nobody invoices for
Every unclear sentence makes the reader do unpaid work. If your email says we need to socialise a proposed approach to optimise the customer journey, the reader has to translate it before they can decide anything. That is not a neutral style choice. It is a cost.
In UK workplaces, we are often polite about this. We say things like 'I just wanted to circle back' or 'I am keen to align on next steps' because they sound professional. But professional should mean easy to act on, not hard to decode. A train announcement that said the service was experiencing a temporary platform allocation issue would not be more expert than 'the train is late'. It would just be worse.
What plain English actually looks like
Before: 'Following our recent cross-functional deep dive, we are seeking to socialise a proposed approach to the optimisation of the customer refunds process, with a view to aligning stakeholders ahead of implementation.'
After: 'We want to change how we handle customer refunds. The proposal is attached. We need a decision by Friday.'
Same facts. Same request. One version respects the reader's time. The other makes them feel like they have wandered into a consultant's slide deck.
Here is another, from meeting notes.
Before: 'Attendees acknowledged the need for greater alignment around ownership of the forthcoming deliverable and agreed to revisit the matter at the next available opportunity.'
After: 'We agreed three things: Sam owns the report, Priya will check the figures, and we meet again on Thursday.'
That is not dumbing down. It is choosing the useful detail. It is also harder than it looks. Anyone can hide behind a long sentence. It takes judgement to decide what the reader actually needs.
Why we confuse length with expertise
Part of it is culture. In many organisations, complexity is a status signal. Long words suggest you have been in the room where the important things happen. Short words can feel exposed. If you write 'we need to decide by Friday', someone might ask what you have left out. If you write three paragraphs of fog, nobody can find the decision to challenge.
But senior people are usually busy. They do not reward the longest email. They reward the one that tells them what to do. The clearest writer in the room often has the most clout because they can make the next step obvious. That is not a junior skill. It is a leadership skill.
There is also a quiet snobbery in the idea that plain English is for people who cannot cope with the technical version. Good technical writing still uses technical terms when they are precise. The difference is that it defines them, uses them once and does not use them as decoration. Jargon is useful when it saves time. It is harmful when it exists to prove you belong.
Language to defend a short message
If you work somewhere that rewards length, you may need a few phrases that make brevity sound like the professional choice it is. Try these.
- 'I have kept this brief so the decision is easy to find. Happy to add detail where it helps.'
- 'The headline is X. The background is in the appendix.'
- 'Would a shorter version help, or do you need the full context?'
- 'I can expand any section — which part needs more?'
- 'This is the plain-English version. The technical detail is attached.'
Notice what these phrases do. They do not apologise for being clear. They frame clarity as a service to the reader. That is much stronger than 'Sorry for the quick email' or 'Just a short one'.
A quick test before you hit send
Ask three questions. Could a busy colleague read this once and know what to do? Could you cut a fifth of it without losing meaning? Are you using a long phrase because it is precise, or because it sounds impressive?
If the answer to the last question is 'impressive', cut it. If a technical term is genuinely needed, keep it and explain it once. Then move on.
Plain English is not the junior option. It is the confident one. In 2026, with inboxes full and Teams chats blinking, the person who can say the thing clearly is the person others trust to lead the conversation. If someone mistakes your brevity for simple thinking, let the decision do the talking.
