Most attention in executive English goes to spoken communication: pitches, presentations, negotiations. Written English is treated as a background skill — something that either works or doesn't, something you learned at school and have used every day since.
That assumption is costly.
For executives working in English as a second language, written communication is often where authority quietly erodes. The email that doesn't quite land. The message that prompts a clarifying reply you didn't expect. The report section that reads as tentative. These are not language failures. They are register failures — and they're invisible to the person writing them.
Spoken English and Written English Are Different Languages
This sounds obvious. The implication is less obvious.
When you speak, you get real-time feedback: you can see whether the listener is following, you can adjust, you can recover. The relationship between what you say and what is heard is dynamic and correctable.
When you write, none of that exists. The reader brings their own context, their own reading speed, their own patience. What you wrote at 7pm after a long day will be read at 9am by someone who wants to know the key point in thirty seconds. The words carry everything. There is no tone of voice, no physical presence, no ability to course-correct.
This makes written English significantly harder, particularly for the elements that matter most at executive level: authority, clarity, and concision.
The Most Common Patterns
Hedging that reads as uncertainty
In speech, hedging can soften a direct message without undermining it — tone of voice carries the signal that you're confident despite the qualifiers. In writing, the tone of voice is gone, and the qualifiers stand alone.
"I think perhaps we might want to consider whether it would be possible to..."
In writing, this reads as someone who is unsure of their own position. The likely author intended caution or diplomacy. The likely reader hears uncertainty.
The fix is to identify which hedges are doing genuine epistemic work ("this is uncertain") versus which are stylistic habits ("this is how I soften things"), and remove the latter.
"I'd recommend we move on this. The main consideration is..."
Same meaning. Entirely different authority signal.
Burying the headline
A very common pattern, particularly among professionals from educational and cultural backgrounds that value thoroughness, is to front-load with context and arrive at the point late.
Structure one: "Given the performance data from Q3, the analysis we conducted in November, and the feedback from the client calls in December, it seems like the right direction might be to..."
Structure two: "We should change the pricing structure. Here's why."
For an executive reading on a phone between meetings, structure two gets absorbed. Structure one often gets skimmed, and the point gets lost.
This is called "bottom-up" versus "top-down" writing. Top-down (conclusion first) is the default for effective executive communication. It's also not natural for everyone, particularly speakers whose native language rewards a more discursive structure.
Over-formality that creates distance
There is a version of written business English — inherited partly from older models of formal correspondence — that sounds respectful but reads as stiff and slow.
"I am writing to follow up on our previous discussion regarding the aforementioned matter, and to enquire as to whether any progress has been made..."
Versus:
"Following up on our call Tuesday — has anything moved on the partnership question?"
The first is technically correct. The second is what a senior English-speaking executive would actually send. The gap between them is not just style — it creates a perception of lower seniority, not greater respect.
Over-formality is a very common pattern in non-native business English, often because formal written language was the model in educational settings. In contemporary executive communication, it signals that you're more comfortable performing professionalism than exercising it.
Passive voice as evasion
Passive construction has legitimate uses. It also serves as unconscious evasion of accountability or directness.
"A decision was made to delay the launch" versus "We delayed the launch."
"It has been determined that the budget cannot be approved" versus "I'm not approving the budget."
Native readers notice the difference. The passive communicates, at some level, that you're not willing to own what you're describing. In executive communication, ownership signals authority.
A Framework for Written Clarity
| Question | What to check |
|---|---|
| What is the one thing this needs to communicate? | Put that first. Everything else is support. |
| Who is reading this, and how? | On a phone, in three minutes? Then it needs to be shorter than you think. |
| Is anything hedged that shouldn't be? | Remove qualifiers that soften certainty you actually have. |
| Is the person/action named? | Replace passive with active wherever you're making a claim or assigning ownership. |
| Does the opening earn the reader's attention? | The first sentence should tell them why to read the rest. |
Email Specifically
Email is the highest-volume written communication channel and the one most people treat as least important to optimise. It is also where the compounding effect of weak written English is most visible, because it happens hundreds of times.
A few principles that apply specifically to executive email:
Subject lines should inform, not tease. "Quick question about the Q4 targets" is useful. "Following up" tells the reader almost nothing. When you're senior, the clarity of your subject line signals that your time and theirs is being respected.
One email, one ask. Emails with multiple requests frequently produce partial responses. If you need three decisions, send three emails or number the questions explicitly. Otherwise the reader will answer the first one and move on.
End with the next step, not a pleasantry. "Hope this helps!" as an email close is filler. "Let me know by Thursday" is useful.
The test for any piece of executive writing: After the reader finishes, do they know precisely what you meant and precisely what, if anything, they need to do? If yes, it's working. If there's any ambiguity, it isn't.
Frequently Asked Questions
Should I be writing emails in English or in my native language?
For communications with English-speaking counterparts, English. The cost of translation is that you lose some control over register and nuance. If the relationship matters, it's worth spending more time on the English than you might in your native tongue.
How do I improve written English when I'm too busy to take a course?
The most effective method is reading high-quality English writing in the same register you need to produce: good business journalism, well-regarded non-fiction, published executive communications. Exposure to how effective writers structure arguments calibrates your instincts faster than instruction.
I write clearly in my first language. Why does it come out differently in English?
Because you're translating a first-language structure into English words, and those structures don't always transfer. English executive writing has its own logic — direct, front-loaded, low on ceremony — that may be quite different from the norms in your native written tradition. The issue is often structural, not linguistic.
What about Slack and messaging apps — does the same standard apply?
A lower standard applies, but not zero standard. The most important principle — clarity on the ask — transfers fully. Short messages are fine. Ambiguous ones create work.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.