Get this delivered to your inbox
Real problems, practical fixes for leaders of international teams. Published weekly.
✓ You’re subscribed. Check your inbox to confirm.
The Email That Offended Half the Team
You wrote one email. Half the team thought it was clear and professional. The other half thought it was rude, cold, or bizarrely blunt. Nobody told you. The misread just sat there — shaping how people responded to you for weeks.
This is what happens when high context and low context communication styles collide in the same team. And it happens constantly — in emails, in meetings, in feedback conversations, in Slack messages. Every single day.
The problem isn’t language. Everyone speaks English. The problem is that people from different cultural backgrounds read completely different things into the same words — and neither side knows the other is reading it differently.
What high context and low context communication actually means
The distinction comes from anthropologist Edward T. Hall, and it’s one of the most practically useful frameworks in cross-cultural communication styles.
In low context cultures — the US, Germany, the Netherlands, Scandinavia, Australia — communication is explicit. The meaning is in the words. If you want someone to know something, you say it directly. Good communication means being clear, specific, and unambiguous. “Just say what you mean” is a compliment.
In high context cultures — Japan, Korea, China, much of the Arab world, India, many African and Latin American cultures — communication is layered. The meaning is partly in the words, but significantly in the context: who is speaking, to whom, in what setting, with what tone, at what time. What is not said matters as much as what is said. Good communication means reading the situation, not just the sentence.
Neither style is better. Both work beautifully inside their own cultural context. The friction starts when they meet — which, in any international team, is every day.
Where high context low context communication damage actually happens
The collision between high context vs low context communication produces three predictable failure patterns in international teams. Once you know what to look for, you’ll see them everywhere.
The email problem. A Dutch manager sends a project update to a mixed team: direct, factual, no softening. The German and American team members read it as efficient. The Japanese and Indian team members read it as cold, possibly hostile. Nobody says anything. The Dutch manager has no idea there’s a problem — because in their communication style, there isn’t one. The damage isn’t in the email. It’s in the relationship erosion that follows, invisibly, over weeks.
The meeting problem. The leader asks: “Does everyone agree with this approach?” Low context team members who disagree will say so. High context team members who disagree will say nothing — or say “That could work” or “Let me think about it,” which in their communication style means significant reservation. The leader, coming from a low context background, hears agreement. It isn’t. This is the same dynamic described in the article on conflict avoidance in international teams — silence that gets mistaken for alignment.
The feedback problem. A British manager gives feedback to a Thai team member: “This is quite good, but there are a few areas we might want to look at.” In British high context communication, “quite good” with a “but” means there are serious problems. The Thai team member, also from a high context culture, may hear the indirectness accurately — but a German colleague overhearing the same conversation would think the work was largely fine. The article on direct and indirect feedback covers this feedback gap in detail.
In each case, the cultural friction isn’t visible. There’s no argument. No complaint. Just a slow, quiet accumulation of misread signals that degrades trust, delays decisions, and makes collaboration harder than it needs to be.
Why this matters more than language
Most organisations invest in language training for their international teams. Almost none invest in communication style awareness. This is a mistake.
A team where everyone speaks fluent English but half the members are from high context cultures and half from low context cultures will miscommunicate more frequently — and more consequentially — than a team with actual language barriers. Language barriers are obvious. People notice them, compensate for them, ask for clarification. High context low context communication gaps are invisible. People don’t realise they’re miscommunicating because both sides think the message was clear.
What to do about it: the Communication Style Audit
The fix isn’t asking high context communicators to be more direct or low context communicators to be more subtle. Both of those approaches fail because they ask people to abandon deeply held cultural instincts about what good communication looks like.
What works is making the communication style gap visible and building team agreements around it.
Identify where each team member sits on the high context / low context spectrum. This isn’t about stereotyping — it’s about awareness. Meyer’s Culture Map is a practical tool for this. The goal is for the team to see the gap collectively, not for individuals to be labelled.
Create a team reference document — even an informal one — that captures how different cross-cultural communication styles show up in practice. “When [name] says ‘that might be difficult,’ it means significant concern.” “When [name] sends a direct email, it’s their communication style, not hostility.” The article on conflict avoidance describes a similar approach with a cultural understatement glossary — the same principle applies here.
Different communication channels create different context levels. Video calls carry more context (tone, expression, body language) than emails. In-person carries the most. For teams with a significant high context vs low context mix, default to higher-context channels for sensitive topics. Don’t deliver critical feedback by email to a team member from a high context culture. Don’t run alignment discussions in Slack.
The most effective leaders I work with have learned to say, in the moment: “I want to make sure I’m reading this right — when you say ‘that could work,’ do you mean you’re on board, or do you have concerns you’d prefer to share offline?” That one sentence — said without judgement — closes the context gap instantly.
The fix is visibility
Make the gap visible and the team can close it together. Leave it invisible and it will quietly erode trust, slow decisions, and cost performance in ways nobody can quite name.
That’s cultural friction. And it’s fixable.
If this sounds like your team, the Multicultural Teams Workshop is built for exactly this — surfacing the communication style gaps that sit below the surface and building shared norms that make collaboration actually work. And if you want a deeper diagnostic, the Cultural Friction Sprint starts with mapping exactly where the friction sits before designing the intervention. Book a discovery call.
Hall, E. T. (1976). Beyond Culture. Anchor Books.
Meyer, E. (2014). The Culture Map: Decoding How People Think, Lead, and Get Things Done in a Global World. PublicAffairs.
Hibbert, E. & Hibbert, R. (2021). Leading Multicultural Teams. William Carey Publishing.
Is miscommunication costing your international team?
If your team speaks the same language but keeps misreading each other’s signals, the problem isn’t language — it’s communication style. Let’s spend 30 minutes mapping where the gaps actually sit.
Book a discovery call View multicultural teams workshopListen & Subscribe
Cultural Friction is now a podcast
The same real problems and practical fixes for leaders of international teams — now in your ears. Follow the show wherever you listen.


