Navigating international teams through case studies and debate
Pick the scenario that resonates most with your experience working across cultures. This will anchor our discussion in real professional contexts.
"During a code review, your German colleague writes 'This approach is wrong. You need to refactor completely.' Your Brazilian teammate is visibly upset and disengaged for days. Your US-based manager asks you to mediate. How do you navigate this cultural clash between direct and indirect communication styles?"
"Your team spans San Francisco, London, and Singapore. Every meeting time inconveniences someone. The SF team complains about 6 AM calls, London is always stuck in the middle, and Singapore developers rarely get face time with leadership. How do you design collaboration that doesn't burn people out?"
"You're presenting a technical proposal to Japanese stakeholders. They listen silently, nod occasionally, ask no questions. The meeting ends with 'We will consider this.' Weeks pass with no decision. Your Western colleagues think it's a rejection. Is it? How do you interpret and navigate high-context communication?"
| Phrase | Example |
|---|---|
| In [culture], it's common to... | "In German business culture, it's common to be very direct with criticism." |
| I've noticed that [group] tends to... | "I've noticed that Asian colleagues tend to use more indirect language when disagreeing." |
| The cultural expectation is that... | "The cultural expectation is that you save face and avoid public disagreement." |
| To bridge this gap, I... | "To bridge this gap, I explicitly ask for feedback rather than expecting them to volunteer it." |
| A common misunderstanding is... | "A common misunderstanding is interpreting silence as agreement when it might just be politeness." |
Situation: A US tech lead asks their Indian developer: "Can you finish this feature by Friday?" The developer responds "Yes, I will try my best." Friday comes—no feature. Monday—still not done. The tech lead is frustrated: "Why did you say yes if you couldn't deliver?"
The developer's perspective: "I said I would TRY. I didn't promise. In my culture, saying 'no' directly to a superior is disrespectful. I thought he understood there were blockers."
The tech lead's perspective: "In the US, 'I'll try my best' means 'yes' unless you explicitly state concerns. If there are blockers, you're expected to raise them immediately, not discover them silently."
Question: Who is "wrong" here? What system or communication norms could prevent this?
Explore how power distance affects communication. Discuss:
Examine assumptions about directness and equality. Discuss:
Design systems that work across cultures. Discuss:
Debate: "Remote-first global teams should adopt a single 'company culture' and communication style. Asking people to adapt to Western-style directness is not cultural imperialism—it's necessary for efficient async work."
Probe: "You said 'Asians are indirect.' Can you be more specific? Are Japanese and Israeli communication styles the same? What about individual variation within cultures? When does a cultural observation become a stereotype?"
Reframe: "You said the Indian developer 'should have just been honest.' From his cultural framework, he WAS being honest—'I'll try' signaled uncertainty. What would need to change on BOTH sides to prevent this?"
Ground it: "Even within your country, have you noticed regional or generational communication differences? What about communication style differences between tech and non-tech companies? Cultural differences exist at many levels—let's start there."
Concrete pivot: "Let's role-play. You're managing a developer from [culture]. They've missed two deadlines but never mentioned blockers. What exact words would you use in your next 1-on-1? Let's practice."
"Tell me about a time you completely misread someone's communication because of different cultural or contextual expectations. What did you learn? How did you adjust?"