The Five Moments English Costs You Most at Work

You are fluent. You do the job in English every day. And you still rewrote that Slack reply three times before sending it.

That gap - between being able to write English and being able to write it without friction - is where most of the cost sits. It does not show up in a performance review. It shows up as fifteen minutes spread across forty small decisions, every day.

The population paying it is not small. The US Bureau of Labor Statistics put the foreign born at 19.1 percent of the civilian labor force in 2025, and that counts only the United States. In a remote-first company with engineers in Krakow, Sao Paulo and Tel Aviv, the share of the team writing in a second language is often the majority.

Here are the five moments that cost the most.

1. The code review comment

Why it is hard: you have to be critical without being personal, in a medium with no tone. Wrong in one direction and the comment reads as an attack. Wrong in the other and your objection does not land at all.

What goes wrong: over-hedging until the concern disappears. "Maybe I am wrong but I think perhaps this could possibly cause an issue?" leaves the author free to ignore you.

What to write instead: state the observation, then the ask.

This will throw if items is empty. Can we add a guard?

Two sentences, no hedge, no accusation. The subject of the sentence is the code, not the person - that is what makes it safe to be direct.

2. Replying to someone senior

Why it is hard: you are calibrating deference in a language whose deference markers you did not grow up with, to someone whose opinion of you matters.

What goes wrong: two opposite failures. Speakers of languages with grammatical politeness, like Japanese and Korean, tend to over-formalise into stiffness. Speakers of direct languages, like Hebrew, Dutch and Russian, under-soften and land as curt.

What to write instead: English seniority register is mostly brevity plus a warm opener. It is not elaborate.

Thanks for flagging this. I looked into it - the root cause is the retry config. Fix is up in PR 4412.

3. The customer-facing email

Why it is hard: it is public, permanent, and attributed to the company rather than to you. The stakes justify the rewriting, which is exactly why it consumes the most time.

What goes wrong: formality inflation. Under pressure, most second-language writers reach for the most formal construction available, which produces "Please be informed that we are currently investigating the aforementioned issue."

What to write instead: customers read plain English as competence.

We are looking into this now. I will update you by Thursday.

4. Disagreeing without sounding rude

Why it is hard: disagreement is the highest-risk thing you can do in any language, and English does it with a specific set of softeners that do not translate.

What goes wrong: either translating your own language's disagreement forms directly, which lands too blunt, or padding so heavily that the disagreement becomes invisible.

What to write instead: English convention is to acknowledge, then pivot.

That makes sense for the batch job. For the live path I think the latency would be a problem - could we keep the current approach there?

"That makes sense for X. For Y..." is a reusable frame. It concedes something real, which buys you the right to disagree about the rest.

5. The status update

Why it is hard: you are describing incomplete work, and the language of incompleteness is where hedging accumulates fastest.

What goes wrong: uncertainty about the work bleeds into uncertainty about the writing, and the update reads as though you are not on top of it.

What to write instead: separate what you know from what you do not.

Auth flow is done and merged. The SSO piece is blocked on a cert from IT - I have asked, no ETA yet.

Both facts, including the bad one, stated flatly. Flatness is what confidence sounds like in English.

The pattern underneath all five

Every one of these is the same problem. English professional register rewards short, direct and specific. Most other business cultures reward some combination of formal, elaborate or indirect. You are not translating words, you are translating conventions, in real time, dozens of times a day.

Research here is thinner than you would expect, and worth being honest about. The clearest academic framing I have found is WordDecipher, by Yuexi Chen and Zhicheng Liu at the University of Maryland (2024), which designs a system for exactly this problem in digital workspaces. It is a system-design paper built around a usage scenario rather than an empirical study, so it does not put a number on the cost. It does make the core observation well: in text-based workplace communication the absence of non-verbal cues raises the risk of misinterpretation, and that risk falls unevenly on people writing in a second language.

What actually reduces it

Editing afterwards is the expensive path, because you are correcting a draft your first language already shaped. The cheaper path is to not build the draft in English at all - write the thought in whatever language you think in, and convert it where you are already typing.

That is what Echoo does. One keyboard shortcut, inside most Mac apps, after granting macOS Accessibility permission. The result replaces what you wrote, in place, so there is no browser tab and no copy-paste between you and the message.

Your first 10 credits are included, with no API key and no card. You can also connect your own provider key and run in BYOK mode.

For the diagnostic side - which specific patterns in your writing give away your first language - see Why Your English Sounds Translated (opens in new tab).