← BlogFor non-native-english

Sharp on the call, careful in Slack: Why written English becomes a different ...

Sharp on the call, careful in Slack: Why written English becomes a different language

You're sharp on a sales call, confident, asking the right questions. Then you Slack your team a follow-up and rewrite it three times, four times, thirty minutes on what should have taken five, and you end up sounding smaller than you actually are. This isn't vocabulary or grammar. This is identity.

The 30-minute Slack message

Maria is a senior account executive at a European B2B SaaS company. She's been selling to American enterprise teams for eight years. On video calls, she's sharp. She reads the room. She knows when to ask a tough question and when to back off. Her last two performance reviews called out her "executive presence on calls."

But here's what they also said: "could be more concise in writing."

Maria knows this feedback is wrong. She isn't less concise on calls. She just sounds different. Written English is where she feels exposed in a way speaking doesn't. On a call, her accent doesn't matter. Her rhythm carries the thought. On Slack, she second-guesses every word. Is this too formal? Too casual? Too many commas? Not enough? Will the team think I'm unsure?

She re-reads the message three times. Four times. By the time she sends it, she's erased half of what made her sound like herself.

Why translation tools make this worse

The obvious fix is Grammarly. Grammarly is good at fixing grammar. It catches missing articles, verb tense, comma placement. Maria uses it sometimes. But Grammarly doesn't solve the real problem. Grammarly makes you sound more correct. It doesn't make you sound like yourself.

In fact, it does the opposite.

The voice that survives your accent, your phrasing, the way you naturally lead thoughts, the way you make decisions out loud, that voice gets flattened by the time it reaches Slack. Translation tools erase it further. They assume you need to sound more native. They assume more formal is better. But that's the opposite of what you actually need.

You need to sound like you. Just faster.

The rewriting trap

The hidden cost of writing in your second language isn't time. It's momentum.

You lose the thread between what you said on the call and what you're trying to write down. You interrupt yourself to check if "this" or "that" is the right word. You pause because you're not sure if the sentence sounds the way you meant it. And with every pause, every re-read, every deletion, you lose the thought that felt so clear when you were saying it out loud.

By the time you hit send, you're no longer writing what you wanted to say. You're writing what you think is safe to say. That's the gap your performance review caught, even though it called it a writing problem. It's not a writing problem. It's a medium problem.

What changes when you can write as you speak

The moment you can draft in voice and get clean writing without rewriting, something shifts. The thought stays intact. The decision-making process survives the medium change. You're no longer translating yourself through a writing filter.

Maria drafted a Slack message by voice in 90 seconds. One pass, no revisions. The message captured the sharpness that exists on her calls but had been disappearing in async. "This," she said, "sounds like the careful version of myself. But also like myself."

Voice writing isn't new, but it usually breaks things

Apple's dictation has been built into macOS since 2012. Google Docs has voice typing. Microsoft has voice input. Otter.ai transcribes meetings. But most voice tools share a problem: they're either too literal (you get every um and uh), or they're too aggressive (they "correct" you into formality).

The other pattern is metering. Wispr Flow caps you at 2000 words per day on the free tier. Otter charges per minute. Most tools assume voice transcription is a premium feature you'll pay for. This creates the same friction as before: you have to choose between speed and cost.

What actually works is something simpler. Run Whisper locally on your machine. Don't meter it. Let it work in Slack, email, your browser, terminal, everywhere. Polish the rough draft into clean writing in under two seconds, without erasing how you actually sound. That's the piece that changes the behavior.

The actual difference

The consultant who lost her thought between voice memo and Notion. The product manager who sounds sharp on standups but careful in async updates. The account executive whose performance reviews praise her on calls but flag her writing. They're not worse writers. They're experiencing the cost of translating themselves.

When you can capture that thought in your voice and have it arrive in Slack as clean writing, you're no longer paying the 30-minute tax. You're not rewriting. You're not second-guessing. The version that arrives is the version you actually meant.

That's not a writing tool. That's getting your actual self back.

More posts
Keep reading

More like this.

  1. For non native english

    Sounded like the careful version of yourself

    You're sharp on calls. Your manager knows it. Your clients hear it. Then you move to Slack and you rewrite the message three...

  2. For non native english

    The 30-minute Slack problem nobody talks about

    You're sharp on the call; your manager noticed it. Your last review said "executive presence." Then you write the follow-up in...

  3. For non native english

    The Slack message you spent 30 minutes on still sounds careful.

    Maria's performance review this year mentioned what it always does: sharp on calls, could be more direct in writing. She'd heard...

All posts →