Case Study 1 — The Nudge That Cost a Quarter

A composite case, assembled from the common experiences of Western managers running email-heavy projects with Japanese teams. Names and details are illustrative.

The situation

Sarah leads product at a mid-sized European software company. Six months ago her firm acquired a small, excellent engineering team in Osaka, and Sarah now coordinates a shared roadmap with them — almost entirely by email and a weekly video call, across a nine-hour gap. Her main counterpart is Hiroshi, a thoughtful senior engineer who, by every signal, is sharp, conscientious, and well-respected by his team.

Sarah is a fast, friendly communicator. Back home this is a strength: she fires off quick questions, gets quick answers, keeps threads tight and light, and prides herself on a warm, low-ceremony style — first names, "thx," the occasional emoji. She treats her Osaka colleagues exactly the same way she'd treat her Berlin ones, which feels to her like the fair, egalitarian thing to do.

Three months in, the relationship is quietly fraying and Sarah doesn't fully know why. Hiroshi's team is delivering, but the warmth has drained out of the exchanges. Replies have gotten shorter and more formal, not less. Sarah has started to feel she's "pulling teeth" to get information, and has written in her notes: Osaka team is slow to respond and a bit closed off — need to push harder for updates. She is about to push harder. That instinct is the mistake.

The 'before': how it felt through Sarah's operating system

Run the last three months through Sarah's home-culture software and her read seems reasonable.

She sends Hiroshi a simple question on a Monday afternoon her time. By Tuesday morning — her morning — there's no reply, which by her instincts means roughly nineteen hours of silence on a one-line question. Back home that would signal "swamped" or "ignoring you," so she sends a light nudge: "Hi — just bumping this, did you get my note? 🙂" When the answer finally comes, it's thorough but oddly stiff, and signed "Best regards, Hiroshi Tanaka" — which Sarah reads as cooling-off, maybe even mild annoyance, and can't account for. To keep threads efficient she's also been trimming the CC line down to just her and Hiroshi, dropping the local manager who used to be copied, because in her world looping in someone's boss on routine stuff feels like needless escalation. And on the weekly call, when she asks "any concerns?", she gets the now-familiar polite silence, which she's started reading as "they have nothing to add."

Every one of those reads is fluent — in the wrong language. And the nudges, the trimmed CC line, the push for faster updates are all about to make it worse.

The 'after': what was actually happening

Nothing was wrong with Hiroshi or his team. Several things were happening below the waterline that Sarah's system couldn't see:

• A written answer is a commitment. For Hiroshi, replying to even a "simple" question means replying correctly — which often means checking a detail or confirming with a colleague first, because being wrong in writing costs face (Chapters 3, 16). The nineteen-hour "silence" was him intending to answer properly at his next morning, after consulting. Sarah's "just bumping this" landed as he was doing exactly that, and read as a senior overseas colleague chasing him before he'd had the chance to do it right. The little smiley didn't soften it; it made the chase feel oddly flippant about something he was treating seriously.
• The clock, not neglect. A "19-hour silence" was frequently one business afternoon on his side. Sarah sent things as Osaka was logging off and felt ignored by morning — her morning — when nothing had gone wrong at all.
• Casualness wasn't reading as warmth. Sarah's "thx" and emoji, meant as friendliness, didn't translate as warmth to a more formal counterpart early in a relationship; they read as a slightly-too-familiar register she hadn't earned. Hiroshi's increasingly formal replies weren't him warming up or cooling off at random — they were him quietly re-establishing the respectful distance her casualness kept collapsing. The stiffening "Best regards, Hiroshi Tanaka" was a polite correction she couldn't read.
• The dropped CC was a small insult. Trimming the local manager off the thread didn't read as efficiency. In Hiroshi's world, his manager having visibility into the work is normal and respectful; quietly cutting him out felt like being asked to go around his own boss (Chapter 6). It made Hiroshi subtly uncomfortable every time.
• The silence on calls was full. As in Chapter 1's Shanghai team, "any concerns?" into a group video grid, with seniors present, is not a question a careful Japanese engineer answers by volunteering a challenge live. The concerns were real — and were going unspoken precisely because Sarah kept asking for them in the one format guaranteed to suppress them.

Sarah had been grading conscientious, respectful behavior as "slow and closed off" — and was about to respond by pushing harder, which would deepen every single one of these problems.

The deeper point

This case is the whole chapter in one relationship. Sarah's trouble had nothing to do with ignorance of Japan — she could have recited facts about Japan. It lived one level below that, in the invisibility of her own communication defaults (theme #5). She experienced "fast acknowledgments are polite," "casual is friendly," "tight CC lists are efficient," and "engaged people speak up" not as cultural choices but as plain professional good sense — neutral, default, cultureless. Because those defaults were invisible to her, she couldn't switch them off, and so she ran them at full strength through email and video, the two media least able to catch or repair the resulting misreads.

And notice the compounding nature of the medium. Face-to-face, Hiroshi's stiffening tone, the manager's absence, the team's swallowed concerns might have surfaced and been repaired in a hallway. In writing, across nine hours, each small misfire just accreted silently into "the Osaka team is slow and closed off" — a conclusion that was about to trigger exactly the wrong fix.

The better approach

Sarah doesn't need to stop being warm or fast. She needs to make her defaults visible to herself and adjust the interface so Hiroshi's team can give her what she actually wants:

• Start formal; let Hiroshi set the pace. Mirror his register — if he signs "Best regards, Hiroshi Tanaka," she's not at "thx, Sarah 😄" yet. Let him wave her down the formality ladder.
• State real deadlines; separate "confirm" from "answer." "No rush — I need this by Thursday your time" and "just a quick 'got it' is plenty for now" remove the guesswork that drove the anxious nudges.
• Account for the clock before feeling ignored, and stop nudging into the void. A glance at Osaka's time turns most "silences" into "it's 3 a.m. there."
• Put the manager back on CC. Restore the visibility she trimmed, and match how the team copies.
• Gather concerns off the live call. Instead of "any concerns?" into the grid, ask Hiroshi privately and in writing beforehand, then bring the synthesized points to the group herself — the nemawashi logic from Chapter 15.
• Send the face-safe written recap. After decisions, "to confirm I've got this right — please correct me if I'm wrong," giving quiet disagreement a graceful written channel.

Scripts she could use: - (stating the need, calmly) "No rush at all on this — I genuinely just need it by Thursday your time. And a quick 'got it' now is plenty; the full answer can wait." - (repairing the CC) "I trimmed our threads to keep them tight, but I should keep Tanaka-san's manager copied for visibility — putting him back on. Let me know if there's anyone else who should be in the loop." - (getting real input, privately) "Before Thursday's call — what are you actually worried about on this timeline? I'd far rather hear it from you directly than have it surface late. I'll raise it as the team's view, not pin it on you."*

Within a quarter of changing the interface rather than pushing the people, managers in Sarah's position typically find their "slow, closed-off" team was conscientious and full of candid views all along — just waiting for a register, a deadline, a CC line, and a channel that let them give it without anyone losing face.

Discussion questions

1. Identify the exact moment Sarah's own communication style became invisible to her. Which habit did she most mistake for neutral good sense?
2. Hiroshi's replies got more formal as the relationship strained. Why is that counterintuitive to a Western reader, and what was it actually communicating?
3. Sarah's "just bumping this 🙂" was meant to be light and friendly. Walk through why the medium (instant written nudge, across nine hours, from a senior person) overrode the friendly words.
4. The case says pushing harder would have deepened every problem. Pick two of Sarah's planned "fixes" (nudge harder, push for faster updates) and trace exactly how each would have backfired.
5. Where in your own email habits — formality, CC, deadlines, nudging — might you be running an invisible default that an Eastern colleague is quietly correcting you on?

Portfolio link. In your Cultural Intelligence Portfolio, under "Behaviors I might misread," add three entries from this case: increasingly formal replies may be a polite re-setting of respectful distance, not coolness; a long silence may be diligence or the clock, not neglect; a colleague keeping their manager CC'd is visibility, not escalation. Beside each, note the interface change you'd make. This page is becoming your early-warning system for the daily medium.