← BlogFor non-native-english

The careful version of yourself

On a call, Maria is sharp. Presence. She holds a room of enterprise buyers, moves through objections cleanly, closes the deal. Her VP mentions it every review. Then she drafts a Slack message to her own team and reads it four times before sending. The grammar is correct. The vocabulary is fine. But the version of Maria that comes through the screen feels smaller than the version on the call. Muted. Careful. It's not intentional. It happens automatically, every time.

The call versus the message

Maria doesn't need permission to speak. On calls, she doesn't ask for it. She interrupts when she needs to, makes her point in one sentence, moves on. Her accent is there, but it doesn't matter. What matters is that she sounds like someone who knows what she's talking about, because she does.

The same Maria in Slack sounds like someone requesting approval.

Call: "Here's the problem with that approach. We need to fix the data model first."

Slack: "I was thinking, and maybe I could suggest, I wonder if there's a possibility we might want to look at the data model? Just a thought."

The information is the same. The confidence is not.

She's not pretending. There's no conscious code-switch happening. Written English in a second language triggers something automatic: a hedging reflex, a reach for qualifiers, a version of herself that sounds smaller. She doesn't choose it. It just emerges.

Her performance reviews confirm it. "Executive presence on calls" is always a strength. "Could be more concise in writing" is always the gap. She knows the gap isn't real. It's not that she's worse at written English than spoken English. It's that written English, async, permanent, reviewable, wrong to edit after sending in some contexts, activates a specific kind of anxiety that calls don't.

Why Grammarly isn't the fix

Maria has Grammarly. It's fine. When she writes "I was thinking, and maybe I could suggest," Grammarly marks it green. The grammar is correct. The sentence is fine.

But Grammarly doesn't see the actual problem. The problem isn't a comma splice or a misplaced modifier. The problem is that she spent 30 minutes writing a 12-line Slack message because the first version didn't sound like her, the second version sounded defensive, and the third version sounded like she was apologizing for having an opinion.

That's not a typo that a grammar checker can fix. That's identity erosion, one rewrite at a time.

Translation tools make it worse. They're marketed as confidence boosters for non-native speakers. What they actually do is erase whatever voice survived the accent in the first place. They iron everything into safety. Maria doesn't need safety. She's closed millions of dollars in enterprise sales. She needs speed. She needs to sound like the person who closes deals, not the person who's worried about whether her English is good enough.

Every tool she's tried treats this as a vocabulary problem or a grammar problem. They assume she's at the beginning of learning English, trying to get the basics right. She's not. She's eight years into selling to US enterprise, and her actual problem is that her writing doesn't carry the same weight as her voice. The medium is doing something to her that doesn't match reality.

The rewrite loop

Here's what actually happens. Maria drafts a message. She reads it back. It sounds small. She highlights a phrase and changes it to something more direct. Reads again. Still small. The logic is there, but the voice isn't. She makes another pass. Adds a period. Removes a qualifier. Reads it again.

By the fourth pass, she's been on the message for 25 minutes. She's changed the content maybe three times. Nothing's wrong with it anymore. It's just smaller than she is.

She sends it anyway because she has three other emails waiting and her manager is about to call.

That's not proofreading. That's the invisible tax of identity gap. She doesn't talk about it because it's not a real problem, anyone can write, right? But multiply 25 minutes by five Slack messages a day, and suddenly she's losing two hours a week to the confidence cost of async writing in English.

Her colleagues who write in their first language don't have this tax. They draft, they send. Three seconds.

What transcription and translation tools actually do

Transcription tools capture words. They're good at that. Otter captures what you say and gives you text. Wispr Flow does the same. Dragon NaturallySpeaking was doing this in the 1990s.

The problem is the output. You speak naturally. The tool types your natural speech directly into the medium. Natural speech is rough. It has fillers, restarts, corrections, the architecture of thinking out loud. Transcription tools clean some of that up, but not all of it. They give you a raw draft that still needs work.

So you end up spending 40 minutes editing the transcript to make it presentable. Which is almost as slow as writing from scratch in the first place. Faster by maybe 10 minutes. Not fast enough to actually use every day.

Translation tools like DeepL or Claude are different. They're trying to improve your voice, not capture it. The problem is they improve it toward a generic "professional English" standard. They strip the personality. Maria speaks with a specific cadence, a specific directness, a specific kind of humor that comes from her background. Translation tools erase that. She gets something grammatically perfect that doesn't sound like her at all. It's worse than before.

The structural issue

The real problem is that non-native English speakers are being asked to carry identity anxiety into writing that native speakers simply don't experience.

A native English speaker in a Slack channel doesn't wonder if her voice will sound credible. She doesn't reread messages to make sure she's not coming across as too uncertain. She writes like she talks, and no one marks her down for it.

Non-native speakers, especially senior ones, especially ones who are sharp on calls, experience a gap between the confidence of speech and the vulnerability of writing. On a call, your accent is just part of how you communicate. People get used to it in 30 seconds. In writing, every word sits there, permanent and reviewable. That's when the hedging starts.

It's not a language problem. It's a medium problem. And medium problems need medium solutions, not language solutions.

What actually helps

What Maria needs is something that captures her real voice, the fast, direct, present version, and renders it clean without losing her. Something that doesn't slow her down further with editing.

Recitey does this. She speaks the way she'd explain something to someone across a table. The tool captures it with Whisper, the same speech engine that runs in production at scale. No word limits, no metering, no per-minute costs. It runs on her device, local, with no cloud processing. She gets clean, structured written English back in under two seconds. Not perfect, but fast enough that she actually uses it instead of opening a blank text editor and spending 30 minutes in the rewrite loop.

The difference is immediate. A Slack message that used to take 25 minutes to not feel small is now something she can fire off in 90 seconds. Still polish it if it matters. Usually it doesn't need it.

What changes is subtle. She's not writing more, she's writing faster. She's not writing better, she's writing more like herself. The performance review probably still says the same thing about conciseness in writing until she changes the medium she's using to write.

But the deals keep closing, and the hours spent rewriting Slack are hours spent actually selling.

The identity frame

This is what all the other solutions miss. They frame the problem as "non-native English speakers need better writing tools."

The actual problem is simpler: voice writing gives non-native speakers the same medium that native speakers have always had in speaking. Fast. Direct. Confident. Exactly how you think.

Non-native English anxiety lives in the transition between thinking (which is fast and confident) and writing (which is slow and careful). Voice bridges that gap. She doesn't have to translate her thought into correct English. She just speaks. The tool translates the voice into text, not the thought into "better" language.

The gap she experiences isn't a language gap. It's a medium gap.

And medium gaps need medium solutions.

More posts