← BlogFor non-native-english

The version of yourself you hear on the call isn't the version Slack sees

Maria's sharp on calls. Her review proved it: "exec presence." But the same review flagged her writing, and she's not ignorant of what that means. The email to her CEO took 30 minutes. The Slack message got four rewrites. The deal notes? She didn't send them.

The gap isn't her ability. It's the medium.

The rhythm difference between speech and writing

On a call, Maria thinks and speaks at the same speed. Ideas flow. She corrects herself mid-sentence and no one's marking it down as a flaw. Conversation tolerates fluency in real time.

Slack's different. It's frozen. A message sent at 2pm is still there at 4pm, visible to five people, rewritable until send. The self-monitoring that's optional on a call becomes mandatory in writing. So Maria does what most non-native English speakers at her level do: she writes, reads, rewrites, reads again, changes two words, and still doesn't send.

This isn't a language problem. It's a medium problem.

Why alternatives like Microsoft Voice Typing and Grammarly miss the point

Microsoft Voice Typing captures what you say, sure. But it doesn't solve the rewrite tax. Grammarly corrects grammar, but it doesn't give you back 30 minutes. Translation tools go further, they erase the voice that's survived your accent, leaving you with something technically correct but flattened.

What Maria wants isn't perfect English. She's looking for her own voice back. The one that's present on every call but goes dormant the moment she types.

The async English tax nobody measures

Non-native speakers at Maria's level aren't beginners. They've got eight years of sales conversations under their belt. They understand enterprise software, read earnings reports, code-switch between technical and executive audiences. But the moment they move from real-time speech to async text, they're taxing themselves with re-reads they wouldn't tolerate on a call.

Native English speakers typically spend 2-3 minutes on a professional Slack message. Non-native speakers in senior roles often spend 8-15 minutes on the same one. Multiply that across a day of deal updates, feedback, and alignment, and it's overhead nobody sees.

The performance review doesn't capture it. It just says "concise."

When the gap is the medium, not the person

Maria discovered what she actually needed wasn't better English. It's a tool that understands the difference between speech and writing.

She started speaking her drafts aloud, her deal updates, her feedback, her proposals. The tool captured the rough version in real time. It ran locally on her Windows machine, so there's no variable cost, no word limit, no metering. Then it polished what she'd said into clean writing in under 2 seconds, the same voice that lands on calls, now preserved in text.

The Slack messages that used to take 30 minutes? They're taking three now.

What changes when you stop rewriting

Speed, accuracy, and confidence emerge. You're writing like you talk. You send. You move on.

More posts
The version of yourself you hear on the call isn't the version Slack sees | Recitey