Chapter 18 — Exercises

These exercises take the principles from the chapter and drag them into your actual inbox, calendar, and chat tools — because cross-cultural communication is a skill of doing, not knowing. Several ask you to look at real messages you've sent and read them through a second operating system. That's the work. Do it with a pen and, ideally, with one or two real threads from your own files open beside you.

Selected answers and sample responses appear in Appendix: Answers to Selected Exercises. Exercises marked with ✍️ feed your Cultural Intelligence Portfolio.

Part A — Check Your Understanding

Short answers in your own words. If one stumps you, reread the matching section.

  1. The chapter argues email "feels neutral" and that this neutrality is a trap. Explain the trap in two sentences.
  2. Describe the "email formality ladder." With a new Eastern colleague, where do you start, and what's the one rule about descending it?
  3. Why is keeping a manager CC'd often read as respect rather than escalation in a hierarchical Eastern workplace? Give the underlying logic, not just the rule.
  4. On a video call, why does the Western "open floor, whoever speaks up wins" model systematically fail a mixed East–West team — and who does it advantage?
  5. Explain the timezone-equity problem in your own words. Why is it more than just an inconvenience — what does who takes the midnight call signal?
  6. Why does high-context communication make written documentation more important across a cultural gap, not less?
  7. What does "just ping me anytime" often mean to a Western colleague, and how can the same phrase land differently for a hierarchical or high-context colleague?

Part B — Check Your Assumptions

For each statement, decide whether it describes a universal workplace truth or a WEIRD/low-context cultural preference. Then write one sentence describing a colleague or context that would see it differently.

  1. "If someone doesn't reply to my email within a few hours, it's polite to fire back at least a quick acknowledgment."
  2. "Copying someone's manager on a routine message is mild escalation — a little passive-aggressive."
  3. "On a video call, cameras off means you're disengaged."
  4. "If it wasn't said explicitly, it wasn't agreed."
  5. "Informal, emoji-friendly messages make you seem warm and approachable."
  6. "Saying 'no rush' genuinely removes the pressure to reply quickly."

The point isn't that the Western view is wrong. Each statement feels like plain professional good sense and is in fact a specific, low-context, often flat-hierarchy position. Catching the feeling — "but that's just obviously true" — is the skill.

Part C — Decode This

Each item is a small cross-cultural moment in the daily medium. Write (i) what the Western reader probably assumes it means, and (ii) a plausible alternative meaning inside a high-context, hierarchical operating system.

  1. You send a three-line question to your Tokyo colleague at 4 p.m. your time. Nineteen hours later, still nothing — then a careful, thorough, slightly formal reply that clearly took effort.
  2. Your new counterpart in Seoul signs every email "Best regards, Min-jun Park," even after you've signed yours "Thanks! – Dave 😄" three times.
  3. On a group video call, you ask "any concerns about the timeline?" Your four Japanese colleagues are silent; the three Americans jump in immediately.
  4. A junior colleague in India copies their own manager — and yours — on a routine project thread that had been just the two of you.
  5. You message a colleague in Manila at 6 a.m. their time with "no rush, just thinking out loud," and get a thorough reply fifteen minutes later.
  6. Midway through a tense email thread, your counterpart suddenly moves their division head into the To: line. Up to now it had been peer-to-peer. (Consider: what two "tells" from the chapter would help you decide whether this is routine visibility or a pointed escalation?)

Part D — What Would You Do?

Real situations, several responses each. Pick the one closest to your instinct, then write why a culturally intelligent colleague might choose differently.

1. The unanswered email. You sent a Japanese counterpart a simple question yesterday afternoon your time; it's now your next morning and there's no reply. Do you (a) send a "just bumping this 🙂" nudge; (b) wait — it's still the same business day on their side; (c) message their manager to check it didn't fall through; (d) re-send the original with "URGENT" in the subject? What does each signal, and which respects both the clock and the "writing is a commitment" norm?

2. The silent grid. You run a weekly call with a mixed U.S./Korea/Japan team. The Asian colleagues never volunteer, and you suspect they see risks you don't. Do you (a) cold-call them live — "Yuki, you're quiet, thoughts?"; (b) accept the silence as their choice; (c) send a pre-call note asking each person for one risk, then raise the list yourself; (d) switch to a round-robin format? Which options create a pre-warned, face-safe runway, and which risk an ambush?

3. The midnight call. Your team spans San Francisco (HQ, where you sit) and Singapore. The recurring weekly sync is at 9 a.m. Pacific — midnight in Singapore — and the Singapore team has never complained. Do you (a) leave it, since no one objected; (b) rotate the time so the early/late burden alternates; (c) move it permanently to a slot that's bad for you instead; (d) ask the Singapore team privately whether it's hurting their evenings, and fix it based on the answer? What does "no one complained" most likely mean in this cultural context, and what's the strongest combination of moves?

4. The vague agreement. A video call ends with everyone nodding to "let's aim to wrap the first phase soon." You're worried "soon" means different things to different people. Do you (a) trust the shared nod and move on; (b) pin a hard date live, on the call, on the spot; (c) send a written recap afterward: "to confirm, here's what I understood — please correct me if I'm wrong"; (d) privately ask each person what they think "soon" means? Which protects face and surfaces a hidden mismatch?

Part E — Cultural Translation

Rewrite each message twice: once as you'd naturally fire it to a Western peer, and once recalibrated for a senior or new Eastern colleague (right formality rung, deadline made explicit, CC handled thoughtfully, emoji dialed appropriately, face protected). Note what changes and why.

  1. "Hey — did you get my last email? Need an answer today. Thx!"
  2. "This design won't work, we need to rethink it. Let's discuss on the call." (You're contradicting a colleague's proposal.)
  3. "Looping in your boss so we can move faster." (You need a manager's help unblocking something.)
  4. "No rush, just ping me whenever you get a sec." (Sent at the colleague's 6 a.m.)

Part G — Try This / Draft It

Hands-on drills. These produce real artifacts you can keep and reuse — the point is to leave the chapter with working language, not just understanding.

  1. The confirmation recap. Take the most recent meeting or call you had with cross-cultural colleagues. Draft the short, face-safe written recap from the chapter: a numbered list of "what I understood we agreed," opened or closed with "please correct me if I got any of this wrong." Keep it to under 120 words. Notice how the "I might be the mistaken one" framing changes the feel versus a flat "as agreed, you will…".

  2. De-vague three phrases. Find three elastic time/scope phrases you actually use — candidates: "end of day," "next week," "ASAP," "a small change," "soon," "early," "circle back." Rewrite each as something a colleague nine time zones away in a second language could not misread (e.g., "end of day" → "by 17:00 Friday, Tokyo time"). Keep the list; paste it into your team's norms doc.

  3. The schedule-send rule. Write the one-paragraph async norm you'd post to your team — the explicit version of "no rush" that's structural, not just stated. It should tell people, in plain language, what off-hours messages do and don't require, and what you'll do if something is genuinely urgent. Read it aloud; if it sounds like a real human said it, it's right.

  4. The face-safe escalation. You need a manager's help unblocking something stuck with a colleague. Draft the two-sentence heads-up you'd send that colleague before you add their boss to the thread — the one sentence the chapter says costs you almost nothing and saves the relationship.

Part F — Reflection & Extension

  1. Your own defaults, audited. Open your Sent folder and find one email you sent to an Eastern colleague. Read it as they might have. Were you a rung too casual? Was a deadline left to "soon"? Did an emoji ride on a serious message? Did you strip a CC line you should have kept? Write a short, honest paragraph — not to flagellate yourself, but to surface a habit you can now see.

  2. The clock as a power statement. Map the actual timezone gap between you and your most important overseas colleague. Who, by current default, takes the unsociable-hour calls? If it's always them, write one concrete change you could propose this month — and the script you'd use to raise it. If it's genuinely shared already, write what makes it work.

  3. A reverse mirror. The chapter mostly asks you to adapt toward Eastern norms. Turn it around: describe one Western communication habit (fast acknowledgments, tight CC lists, cameras-on, "just ping me," radical written transparency) that has a genuine strength your high-context colleagues might benefit from — and how you'd offer that strength without imposing it. (Theme: this is a two-way bridge, not a one-way assimilation.)

✍️ Portfolio Builder. In your Cultural Intelligence Portfolio, build the "Communication contract" section for your chosen culture (this mirrors the chapter's Portfolio Prompt). Fill four buckets — Email, Video, Timezone, Chat — with the specific defaults you'll run with colleagues from this culture: the formality rung you'll start on, your CC rule, how you'll state deadlines, your camera phrasing, one way you'll draw out quiet voices, the real time gap and one burden-sharing move, and your async rule written as you'd say it aloud to the team. Then paste in one real thread and annotate a single place you'd now handle differently. You'll reread this at Chapter 40 and find it's become a working playbook, not a list of ideas.