You're sharp on calls. Your manager's review said so. But every Slack message is a version of you that sounds more careful, smaller, less like how you actually think. This isn't a grammar problem. It's a medium problem.
The morning you lose to rewriting
Maria, a senior account executive at a European SaaS company, finished a sales call with a US prospect at 10:15am. She had been sharp. She'd answered a difficult objection without hedging. She'd made a connection about the prospect's use case that the prospect hadn't articulated themselves.
At 10:16am, she opened Slack to write the follow-up message to her sales director: "Hey [name], had a good call with [company]. They pushed back on ROI assumption but I walked them through the actual payback model. I think we're in the running."
She read it. It sounded small. Corporate. Not like her. She rewrote it.
Second attempt: "Just got off with [company]. They questioned our ROI calc, totally fair. Showed them the model and the gap closes in year two. I think we have a real shot here."
Better. Still not right. The pause before sending stretched to five minutes, then fifteen, then thirty. She'd spent more time polishing that one message than she'd spent on the call itself.
This is the hidden tax of writing in a second language at a senior level. It isn't vocabulary. You know the words. It's the identity tax, the time it takes to find a written voice that sounds like the version of you that people trust on calls.
Why Grammarly and translation tools make it worse
Grammarly will fix the semicolon. Wispr Flow will expand your contractions. Translation layers will make your word choice neutral and safe.
None of these give you back the time. None of them give you back the authority you have when speaking.
A non-native speaker who's excellent in English on calls isn't struggling with English. You're struggling with the asymmetry: your spoken English carries confidence your written English erases.
Grammarly assumes you're a beginner. You're not. Translation tools erase your voice to protect you from errors. But that erasure is exactly what makes your written voice sound watered-down.
The call-to-writing gap
Here's what a senior PM in Stockholm or Berlin actually experiences:
- On a call, you think in English at near-native speed.
- Your accent doesn't reduce your credibility; it authenticates your international perspective.
- You adapt your pacing. You check in. You're present.
In Slack, you have no accent to authenticate you. You have no rhythm to carry you. You have only words. So you choose them with extreme caution.
The gap between your call voice and your written voice isn't a gap in English. It's a gap in confidence because writing doesn't give you the feedback channels that speaking does.
What changes when the medium stops fighting you
When you can write the way you think, quickly, without a rewrite loop, something shifts.
You stop sounding like a careful version of yourself. You sound like yourself.
Maria's last performance review mentioned "exec presence on calls" and "could be more concise in writing." She knew both statements were about the same person in two different media. She wasn't less concise in writing. She was more tentative. The tentativeness wasn't her English. It was the friction of forcing her voice through a medium that didn't carry the same confidence signals that a call does.
When the rewrite tax disappears, the voice comes back.
How this actually works for non-native speakers
The default approach assumes translation: hear-it, translate-it, write-it. That adds latency and erases voice.
A different approach assumes transcription plus polishing; speak-your-thought-as-you-would-on-a-call, then let the system clean the rough edges into written form.
This works because your voice is already close to professional English on calls. You don't need translation. You need transcription that runs locally on your Windows machine with no cloud latency, and a light polish layer that cleans tense and articles without rewriting your actual voice.
The rest is about where this works: Slack, email, your browser, every place you currently draft and redraft.
The PM who spends 30 minutes writing what took 3 minutes to say isn't struggling with English. They're struggling with a medium that doesn't carry the signals that make them sound like themselves. The solution isn't better translation. It's writing that doesn't force you to translate yourself.