5 exercises — how different cultures express disagreement, requests, and feedback in tech teams. German directness vs. British hedging vs. US casual framing vs. Japanese implicit communication.
0 / 5 completed
1 / 5
During a code review on a distributed team, a German engineer writes: "This approach is not optimal. I suggest refactoring the service boundary here." A Ukrainian developer reads this as harsh criticism. A British teammate reads it as a neutral suggestion. Who is correct?
Low-context vs. high-context communication — the core concept:
Anthropologist Edward Hall described communication styles on a spectrum:
Low-context cultures (Germany, Netherlands, Scandinavia, Israel) value: • Directness — say exactly what you mean • Bluntness is not rude — ambiguity is • "No" means no; "I think you should reconsider" is also a strong no • Criticism is about the work, not the person
High-context cultures (Japan, Korea, many Middle Eastern, parts of Latin America) value: • Indirectness — meaning is implied, not stated • Maintaining face/harmony is important • Disagreement is expressed indirectly • "That's an interesting approach" may mean "I disagree strongly"
Mixed-context cultures (UK, India, Brazil) use politeness strategies but still communicate indirectly in conflict situations.
For international IT teams, this creates real friction: • A German engineer's "This is wrong" = "your code has a bug, please fix it" (not an attack) • A Japanese teammate's silence after a proposal may mean strong disagreement • An Indian developer saying "I'll try my best" may signal they think the deadline is unachievable
Practical vocabulary for navigating this: • "Direct communication style" — explicit, literal, low-context • "Indirect communication style" — implicit, read-between-the-lines, high-context • "Face-saving" — avoiding statements that would embarrass someone publicly • "Reading the room" — perceiving unstated group sentiment
2 / 5
A Slack message from a US-based tech lead to an Eastern European team: "Hey, just wanted to circle back on this PR — would love to get your thoughts before EOD!" The developer is unsure: is this a friendly suggestion or a firm deadline? What is happening?
American professional communication patterns in tech:
US tech culture often pairs direct, fast-paced work expectations with casual, friendly-sounding language. This creates a gap: the language sounds optional, but the expectation is urgent.
Common US tech softened-request patterns: • "Would love to get your thoughts" = "Please review this" (not optional) • "Circle back" = "Follow up on" (neutral; not criticism) • "Just checking in" = "I need a status update" • "When you get a chance" = "Low priority but please do this" • "EOD" = "End of day" — usually the sender's timezone; ask if unclear • "Does that make sense?" = "Do you agree / have questions?" • "No worries" = "It's fine" — genuinely reassuring, not passive-aggressive
US tech vocabulary you will encounter daily: • sync up — have a meeting or check-in • touch base — contact someone briefly • take this offline — move the discussion out of the current meeting • bandwidth — capacity to take on more work ("Do you have bandwidth for this?") • leverage — use ("Let's leverage the existing API") • visibility — awareness of progress ("Give me visibility on this") • actionable — concrete enough to act on
Navigating this as a non-native speaker: When in doubt, restate: "Just to confirm — this is needed by your EOD, correct?" Plain clarification is always professionally appropriate.
3 / 5
At a sprint retrospective, the team discusses what could improve. A British team lead says: "I wonder if we might want to think about perhaps improving our PR review turnaround?" A Dutch developer responds with a crisp "Yes, we take too long." Why might the British team lead be bothered by this response?
British communication — hedging, understatement, and politeness strategies:
British English (especially in professional settings) uses several distinct patterns:
1. Hedging to soften force: • "I wonder if..." / "Perhaps we might..." / "It could be worth..." • These are not uncertain — they are strong suggestions packaged as tentative questions • The hedging performs modesty and invites (rather than demands) agreement
2. Understatement: • "Not ideal" = serious problem • "Slightly concerning" = very alarming • "It might be worth revisiting" = this needs to change • "That's an interesting approach" = I disagree with this approach
3. Politeness conventions in British workplace writing: • "As per my last email" = "I already said this — please read it" (can be passive-aggressive) • "Going forward" = "Stop doing what you've been doing" • "With all due respect" = "I disagree and here is why"
4. Key contrast — British vs. Dutch directness: The Netherlands consistently scores as one of the most direct cultures in cross-cultural research. In Dutch business culture, saying "Yes, we take too long" is helpful and efficient. In UK culture, it can feel blunt in a group setting where more supportive framing is expected.
For non-native speakers: Understanding hedging helps you not underestimate the weight of British feedback. "This approach has some limitations" from a British review is equivalent to "This is wrong" from a more direct culture.
4 / 5
An engineering team in a Japanese-American startup has daily standups. The US engineers talk freely, interrupt to add information, and build on each other's ideas. The Japanese engineers are mostly silent unless directly asked, even when they have important information. What is most likely happening?
Silence, turn-taking, and participation in cross-cultural meetings:
Different cultures have fundamentally different meeting norms:
US / Western tech meeting culture: • Thinking out loud is normal and valued • Interruption is often seen as engagement ("Yes, and...") • Silence = nothing to say, agreement, or disengagement • "If you don't speak up, we assume you're okay with it" • Speed and energy signal competence
East Asian meeting culture (Japan, Korea, China): • Speak when you have something final to say — not to brainstorm • Listening is active and respectful; silence is not passive • Interruption is rude, even if well-intentioned • Speaking less but with precision is valued • Group harmony matters; contradicting publicly is uncomfortable • Decisions may be made before the meeting (nemawashi in Japanese — building consensus informally)
What helps: • Go around the room explicitly: "Yuki, what do you think?" • Add async channels: let people respond in Slack after the meeting • Frame silence as fine: "Take a moment to think before answering" • Ask: "Does anyone have concerns they haven't had a chance to raise?"
Vocabulary: • turn-taking — the implicit rules about when each speaker may speak • floor — having the floor = your turn to speak • round-robin — going around to ask each person in sequence • nemawashi (Japanese) — building consensus informally before a formal meeting
5 / 5
A tech lead writes in a team retrospective document: "We should consider being more proactive about surfacing blockers earlier." Which of the following is the most culturally inclusive rewrite of this feedback?
Writing inclusive, culturally neutral team norms:
Why the original feedback fails cross-culturally: "Be more proactive about surfacing blockers" assumes: • Everyone defines "proactive" the same way • Everyone is comfortable volunteering information in group meetings (not true for high-context cultures) • The issue is attitude or willingness — not structure
Why option B is best: ✅ Gives a concrete, specific behaviour: "blocked for 2+ hours → post in #blockers" ✅ Explains the purpose: "visibility, keeps sprint on track" ✅ Accepts multiple communication styles: "whether you prefer direct real-time or async" ✅ Creates a shared team norm rather than blaming individuals ✅ Removes ambiguity: no cultural interpretation required
Why option A ("must be fixed immediately") is worse: • Blame language ("not communicating") puts individuals on the defensive • "Immediately" creates urgency that may cause face-loss in some cultures
Why option C is worse: • Names behaviour as a personal skill deficiency • "Engineers who did not" implies blame and may make people from face-saving cultures shut down entirely
Why option D is worse: • "We expect" is top-down command framing • "More vocal during standups" reinforces the cultural default of verbal, real-time participation — exclusionary for async/indirect communicators
Key principle for writing cross-cultural team norms: Describe the system and expected behaviour, not the person's deficiency. Give multiple valid paths to the same goal.