Too Formal, Too Blunt, or Just Right: Calibrating Tone in English

Grammar has rules. Register has conventions, and conventions are learned by exposure rather than instruction. That is why the last thing to arrive when you learn a language is the ability to sound like you meant to sound.

You can be entirely fluent and still miss by a wide margin, in one of three directions.

Direction 1: too formal

The most common miss, and the one people are least aware of, because formality feels like safety.

If your first language is German, French, Spanish, Portuguese, Italian, Japanese or Korean, your business register genuinely is more formal than English business register. Carrying it across is not a mistake in your English. It is an accurate translation of the wrong thing.

• Overshot: "Please find attached the requested document for your kind consideration."
• Calibrated: "Here is the doc you asked for."

• Overshot: "I would like to take this opportunity to express my gratitude for your assistance."
• Calibrated: "Thanks for the help with this."

The cost is not that you sound rude. It is that you sound distant, and in a flat organisation distance reads as either coldness or inexperience.

Direction 2: too direct

If your first language is Hebrew, Dutch, Russian, German or one of the Nordic languages, the softening layer English wraps around requests and criticism is thinner or absent in yours.

• Overshot: "This is wrong."
• Calibrated: "I think this might not be right - can we check?"

• Overshot: "Send me the file."
• Calibrated: "Could you send me the file when you get a chance?"

This miss is more expensive than the first, because readers attribute it to personality rather than to language. Nobody thinks "that is a Dutch sentence structure." They think "that person is abrupt."

There is an asymmetry worth noticing: fluency makes this one worse. If your spoken English has an accent, listeners discount bluntness automatically. Written English carries no accent, so it gets no discount.

Direction 3: too hedged

If your first language encodes deference grammatically - Japanese and Korean especially - English forces you to express it with words instead, and words are countable in a way that grammar is not.

• Overshot: "I think maybe it might be possible that we could perhaps consider changing this, but I am not sure."
• Calibrated: "I think we should change this. Worth discussing?"

Every hedge in English costs you a little authority. One signals appropriate humility. Four signals that you do not believe your own sentence.

Why translation does not fix register

A translator's job is to preserve meaning. Register is not meaning - it is the social frame around meaning, and it is specific to a culture rather than to a language.

Translate a polite Japanese request into English faithfully and you get an English sentence far more deferential than the situation calls for, because you preserved the politeness level instead of converting it. The output is correct and still wrong. The same happens in reverse: a faithful translation of an ordinary Hebrew request produces an English imperative.

What you want is not translation but transposition - same intent, register recalculated for the target culture.

Calibrating to the room

Three practical rules that cover most cases:

• Match the length of the person you are replying to. If they wrote one line, do not write six. Length is a register signal in English, and matching it is the fastest way to sound like you belong.
• Put the ask in the first two sentences. English professional writing front-loads. Building up to the request the way you would in Japanese or Arabic reads as evasive rather than considerate.
• Count your hedges before sending. Aim for one at most. Deleting the rest will not make the sentence rude, it will make it confident.

Making it repeatable

The problem with a calibration checklist is that you have to run it every time, on every message, forever. That is fine for the email that matters and unsustainable for the forty Slack replies in between.

The way out is to encode the calibration once instead of applying it forty times. In Echoo you write your own command - your own prompt, your own keyboard shortcut - so "make this sound like a normal English Slack message, not a formal letter" becomes one keypress rather than a judgement call you keep making.

On the Pro and Max plans, Memory gives each command its execution history, so results drift toward the way you actually write rather than toward a generic assistant voice.

You can start with the 10 credits included, with no API key and no card, or connect your own provider key and run in BYOK mode. Where your text goes depends on the mode you pick: local models process on your Mac, and cloud modes send each request to the provider you selected, under that provider's data policy.

Related reading: Why Your English Sounds Translated (opens in new tab) for the diagnostic patterns, and The Five Moments English Costs You Most at Work (opens in new tab) for the situations where register matters most.