Writing & Expression: Cross-Cultural WritingHigh vs low context · Direct vs indirect · International English · Cultural taboos

Cross-cultural communication often fails not because too little was said, but because the two sides disagree on where the meaning belongs. High-context cultures keep meaning outside the words — in the relationship, the setting, the tone, the unsaid. Low-context cultures put all of it into the words. Step one is to spot the lowest-context reader in the room and write for them.

Hall gave us the single most useful cultural axis there is: how much of the message rides in the words themselves versus in everything around them.

Chinese and Japanese lean high-context, where "leaving it unsaid" and "you know what I mean" are marks of tact; German and American business English lean low-context, where "spell it out, write it down, don't make me guess" is what counts as responsible. The same hedged email reads to a Chinese colleague as "he doesn't really approve," and to a German colleague as a plain "OK." The misfire isn't in the language — it's in the mismatch of context level. Writing for a mixed audience, default toward low context: drag the subtext out of the air and put it on the page. Not to talk down to anyone, but to keep understanding from depending on a background you don't actually share.

• ✓ Cross-border email, global announcements, remote async work — writing for people whose faces you can't see
• ✗ Assuming "I was perfectly clear" — clear only inside your own context
• ✗ The reverse: being so blunt with a high-context reader that you come off as rude; direction depends on who's across from you
• ✗ Leaving the key decision in the "between the lines," hoping they'll infer it

When you give feedback, "how direct is appropriate" is set by culture, not universal. Some cultures amp criticism up with words like absolutely and totally; others soften it with a little and sort of. You speak on your scale, they hear on theirs, and the error opens up right there. The craft of cross-cultural feedback is to mark your intensity explicitly.

Meyer draws this as a full axis running from direct to indirect — and warns that where you sit on it is nearly invisible to you and glaring to everyone else.

A Dutch or German leader saying "this doesn't work" is usually just addressing the work; a British, Chinese, or Japanese leader saying "that's interesting, maybe take another look" may already be a heavy no. The danger fires in both directions: direct people wound indirect readers without noticing, and indirect people are so soft that direct readers never register "this is a problem." The fix isn't picking a side — it's separating "how serious this is" from "how I say it." The tone can be gentle; the severity must be nailed down.

• ✓ Cross-cultural code review, feedback to global reports, performance conversations
• ✗ Treating "direct = honest, indirect = insincere" as universal truth — that's just your cultural preference
• ✗ Downgrading a blocker to a nit to save face; they don't fix it, and that's on you
• ✗ Adjusting only the tone, never the severity: so polite they can't tell it's a must-fix

Most readers in a global audience speak English as a second language. Writing "international" English isn't writing more childishly — it's cutting the things only native speakers get instantly: idioms, slang, sports and pop-culture references, roundabout phrasal verbs, so the meaning doesn't lean on a shared background you don't have.

Twenty-five centuries early, that line is the yardstick for international English: the goal is to convey, not to show off. Orwell's sixth-sense rule agrees — if there's an everyday word, never reach for the fancy foreign one.

Native speakers routinely overestimate shared context. "Let's touch base and circle back once we move the needle" is a triple obstacle for a non-native reader: touch base (baseball), circle back (business jargon), move the needle (a gauge metaphor). Clear international English isn't dumbing down — it's lifting the cognitive load off the reader: short sentences, common words, explicit subjects, one word one meaning, and spell out an acronym on first use. It reads better for native speakers too — nobody ever complained a sentence was too clear. (Jean-Paul Nerrière nicknamed this stripped-down English "Globish.")

• ✓ Global RFCs, cross-border Slack, docs and talks for multilingual readers, international pitches
• ✗ Showing off with idioms, puns, and sports references — native speakers laugh, everyone else goes blank
• ✗ Mistaking "international English" for broken English: it wants clarity, not damage
• ✗ Leaving acronyms and inside jargon unexplained, assuming the world knows your team's shorthand

The most dangerous cultural assumptions are the ones you never registered as assumptions — a joke, a metaphor, a holiday "everyone" celebrates, a gesture, a color. Before writing for a cross-cultural audience, ask one thing: right here, am I treating "common sense where I'm from" as "common sense for humans"?

Your own culture is the water — the thing you're swimming in and can't see. The taboo you'd never notice is the one someone else spots on the first read.

Taboos come in two kinds. One offends: jokes about religion, politics, a "happy holidays" that assumes Christmas, color symbolism (white is mourning in East Asia, weddings in the West). The other doesn't offend but simply fails: local sports and TV references, historical analogies only your country gets, defaulting to Fahrenheit, miles, your currency, your date format. The fix isn't memorizing a taboo list — you can't finish it — but building the reflex of "is this my water?", and, when you can, having one outsider read it first. The defaults you can't see, others catch instantly.

• ✓ Global announcements, cross-border pitches, talks and training material for diverse readers
• ✗ Using references and analogies only your own country gets, and thinking they're vivid
• ✗ Opening "light" with religion, politics, or body humor
• ✗ Defaulting units, date formats (US MM/DD vs. the rest's DD/MM), and name order