Understanding Cultural Dimensions

Warm-up: The meeting where nobody said no

2 warm-up questions

• Have you ever heard a colleague say 'that might be difficult' or 'we'll consider it' — and only discovered weeks later that it meant 'no'? What did it cost?
• First try: I'm a colleague from a very indirect culture. You ask whether my team can meet the launch date, and I answer: 'The timeline is… ambitious.' Respond to me — 30 seconds, go.

Reading: What's really at stake

Read a 213-word text about What's really at stake

What's really at stake A project team agrees a deadline. Everyone nods. Six weeks later the work is late — and it turns out one member signalled the problem in the very first meeting. They said the timeline was “ambitious”. The chair heard a compliment. In a meeting that mixes direct and indirect communicators, the chair is being judged from two directions at once. The direct colleague is asking: is this person clear and decisive, or do they let things drift? The indirect colleague is asking: does this person give me a safe way to disagree, or will I have to say everything in public, bluntly, like an accusation? Fail the first test and you lose respect; fail the second and you lose information — the room simply stops telling you the truth. The expensive failure is almost always the second one. Phrases like “we'll consider it”, “that might be difficult” or a long silence are not small talk — in much of the world they are the answer. A chair who records them as agreement isn't being decisive; they're signing off on a risk nobody dared to repeat. Today you'll learn a four-move method for hearing the soft 'no', opening it up gently, and still leaving the meeting with a real decision.

Vocabulary: Cross-Cultural Communication Vocabulary

7 items

Framework: The Chair's Bridge

The Chair's Bridge, 4 steps

The Chair's Bridge: A four-move method for chairing any discussion where communication styles clash: give the indirect voice the floor, decode the softeners, credit both sides, and land a decision with specifics in writing. Works in meetings, calls and email threads alike.

Reading: Three model performances

Read a 350-word text about Three model performances

Three model performances The same four moves — invite, probe, bridge, land — in three situations where a soft 'no' was about to be recorded as a 'yes'. The 'we'll consider it' client (sales follow-up call) “Before I go on — I'd really value your honest reaction so far. … You'll consider it; thank you. Just so I'm sure I've understood: is the hesitation more about the price, or about the timing of the rollout? … That's very helpful — so timing is the issue. What if we kept the price as agreed but moved go-live to January, after your busy season? … Then here's what I'll do: I'll send a revised proposal with the January dates by Friday, and you can share it with your team. Would that be useful?” The 'that might be difficult' supplier (production deadline) “I'd like to hear your team's view first — we depend on your read of the schedule. … You said meeting March 'might be difficult'. Could you help me understand which step creates the difficulty — materials, or capacity? … So the materials lead time is the real constraint. Your caution is exactly why we work with you — and we do have a hard launch date. What if we split the order: sixty per cent for March, the rest in April? … Agreed. I'll confirm the split quantities in writing today — and please flag anything that still feels tight.” The colleague who flattened the room (internal review) “Thank you, Marta — that's a clear position, and the cost figures are important. I noticed we haven't heard from everyone yet, and I'd like Anh's perspective before we settle this — Anh, you've run this process longest. … So if I'm hearing you right, the saving is real but the handover risk lands on your team. Both points can be true. What if we approved the change but piloted it on one product line first? … Good. I'll write up the pilot scope tonight — Marta, you'll have the numbers framing; Anh, nothing moves to your team until the pilot review.”

Practice: Direct vs. Indirect Communication

Matching exercise, 6 items

• That might be difficult to implement.
• No, I don't think that will work.
• We'll need to consider all options carefully.
• The deadline is Friday. Can you commit to that?
• Perhaps we could explore an alternative approach?
• I completely disagree. Here's why.

Practice: Fix Culturally Inappropriate Phrases

Error-correction exercise, 4 items

• Your proposal is wrong. Here's what we should do instead.
• Why didn't you finish this on time? This is unacceptable.
• I kind of maybe think we should possibly consider looking at the data sometime.
• We need a decision now. Everyone needs to commit right here.

Dialogue: Navigating a Cross-Cultural Meeting

Role-play: You're leading a virtual meeting with team members from Germany (direct) and Japan (indirect). You need to navigate both communication styles. (10 lines)

• Team Lead (You): Good morning, everyone. Thank you for joining. I'd like to get your perspectives on the proposed timeline. Kenji, would you like to share your thoughts first?
• Japanese Colleague: Thank you. The timeline is... ambitious. We may need to consider some adjustments.
• Team Lead (You): Thank you, Kenji. When you say adjustments, could you help me understand which areas you feel need more time?
• Japanese Colleague: The testing phase might benefit from additional time. Quality is very important for our clients.
• German Colleague: I disagree. The timeline is fine. We just need to be more efficient in the development phase. Two weeks for testing is enough.
• Team Lead (You): Both perspectives are valuable. Stefan, I appreciate the efficiency focus—that's important. And Kenji raises a good point about quality expectations. What if we kept the overall timeline but added a buffer specifically for the testing phase?
• German Colleague: That works for me, as long as we define exactly how many days we're adding.
• Team Lead (You): Absolutely, I'll put specific numbers in the revised plan. Kenji, would a three-day buffer for testing work for your team?
• Japanese Colleague: That would be very helpful. Thank you for considering this.
• Team Lead (You): Great. I'll send a revised timeline to everyone by tomorrow so we can all review it. Thank you both for your input.

Discussion: Your mission: chair the clash

3 discussion questions

• Mission: chair a meeting from YOUR working life — a real decision your team faces, with one very direct and one very indirect participant. Run all four moves: invite the quiet voice first, probe the softener, bridge, land it twice. Success = the indirect person's real concern is on the table in their own words, the direct person leaves with a specific commitment, and you close with a promise in writing. (Tutor: play both colleagues — switch styles mid-meeting.)
• Second take: this time your probe gets another softener back — 'we will do our best.' Probe once more without cornering the speaker. What language keeps the door open?
• Replay the warm-up: I tell you the timeline is 'ambitious'. Answer me now, with the full method — then compare it with your first answer from the start. What do you hear in that word that you didn't hear forty minutes ago?