Direct is not rude: writing across cultures

Directness is a dialect, not a character flaw. When you write across cultures, the message should stay direct; what changes is the ritual around it, the greeting, the framing, the amount of relationship on the page. Muddying the actual content is not cultural sensitivity. It is fog with good manners.

This distinction gets lost because we use one word, "direct", for two different things: how plainly the information is stated, and how much social cushioning surrounds it. Cultures differ enormously on the second. On the first, every reader on earth wants the same thing: to understand you on the first pass.

Separate the message from the ritual

Every message has a payload and an envelope, and cross-cultural writing goes wrong when people adjust the wrong one.

The payload is the fact, the ask, the decision: "The shipment is late. We need a revised date by Thursday." The envelope is everything around it: how you open, whether you ask about the weekend, how much apology precedes the point, how the sign-off lands.

Writers afraid of seeming rude tend to leave the envelope untouched and blur the payload instead. "There may be some timing considerations worth aligning on" is how a shipment stays late for two more weeks. The reader in Tokyo or Berlin or São Paulo did not need the fact softened. They needed the fact, inside whatever envelope their working culture finds respectful.

So the honest adaptation runs the other way:

• Keep the payload plain: one fact, one ask, one date, findable in seconds.
• Spend your adaptation budget on the envelope: greeting, warmth, order, sign-off.
• When unsure, mirror the envelope your counterpart uses with you.

Over-softening is its own insult

Softening the content for a reader from a "polite" culture quietly assumes they cannot handle information, and readers notice.

This is the part I would argue about at dinner. The advice industry treats indirection as the safe default: hedge everything, wrap every request in three layers, and no one can be offended. But a hedge is not free. Every "perhaps we might consider" transfers work to the reader, who must now excavate what you want, and second-language readers pay that cost double. The kindest sentence for someone reading in their third language is a short one with the verb where they expect it.

Working on Unvent keeps this in front of me constantly: a Chrome extension gets used everywhere, so the words on the page are read by people from working cultures I know nothing about. Writing for that audience taught me that plain and blunt are not neighbors. "The export failed" is plain everywhere. "This is broken, obviously" is blunt everywhere. No culture on the list confuses the two.

What actually varies is the envelope's thickness, and learning that per person is cheaper than fogging every payload for everyone.

Learn the person, not the passport

Culture predicts the average, and you never write to the average; you write to Priya, or Lars, or Ken.

The country-guide approach, where you memorize that one nationality is blunt and another circles, fails at the individual level constantly. People are shaped by their industry, their last boss, their years abroad, and their own temperament, and any one of those can outweigh the flag. Treating a person as their country's median is its own quiet rudeness.

The better instrument is attention:

• Read their messages as a style sample. Length, greeting, how they say no.
• Notice what they do with your style. Mirroring back? Adding formality? Trimming it?
• When the stakes are high, ask once, plainly: "Do you prefer the short version or the full context?"

People love that question. Nobody in the history of email has been offended by being asked how they like to be written to.

When the meaning bends, name it

The dangerous cross-cultural moments are not rudeness; they are sentences that mean different things in two inboxes.

"That would be difficult" is a flat no in some working cultures and an invitation to negotiate in others. "Interesting idea" ranges from praise to burial. Silence after a proposal means consent in one team and veto in the next. None of this is fixed by politeness, because both readers think the sentence is clear.

The repair is to close the loop in words too plain to bend: "Reading your reply as: the current date does not work and we should propose a new one. Correct me if I have that wrong." Clunky? Slightly. But clunky and shared beats elegant and private, and across time zones a misread sits for a full day before anyone catches it.

Do the same in reverse when your own no needs to travel: state it, then cushion it. "We can't take this on. I wish we could, and I'm glad you asked us first." The no arrives intact; the relationship gets its envelope.

One version, written for the furthest reader

Write one message aimed at the reader with the least shared context, and every other reader is covered free.

The furthest reader is reading in a second language, in another timezone, without the hallway context, possibly forwarding your words to a boss you will never meet. Writing for them enforces habits that turn out to be universal courtesy: short sentences, no idioms, dates with month names instead of ambiguous numbers, the ask in its own line.

Notice that this is just good writing wearing a passport. The average reader in your own office also skims, also misreads "12/06", also bails on long paragraphs. The furthest reader is not a special case. They are your actual reader, with the tolerances turned down, and a message built to their spec works in every inbox it lands in.

Direct, in the end, is a gift you give the reader: the gift of not having to guess. Wrap it however their culture likes. Just never replace the gift with the wrapping.