In the previous article (Cross-Cultural Management #3), I wrote about Cultural Intelligence (CQ) and why excellence doesn’t protect you from cross-cultural failure.
This time, I’ll dig deeper into the hardest part of CQ — behavioral CQ, or the art of adjusting your actions — through a different case study.
She embraced the culture — and still lost trust
Another case study featured a North American manager assigned to an Asian country.
From day one, she actively worked to integrate. She studied the local language, learned business etiquette, joined team dinners and social activities. She was practicing the first stage of mindfulness — “suspend judgment, observe” — at a high level.
When I first read the case, I thought, “She’s doing everything right.” Most expats don’t put in this kind of effort. She surely would succeed.
But the story took an unexpected turn. In several critical moments, she fundamentally damaged trust:
- She publicly stopped a local manager’s proposal during a meeting
- She intervened when the interpreter stopped translating
- She escalated a problem directly to headquarters
In a North American workplace, every one of these would be “the right thing to do.” Problems should be discussed openly. Information should be shared transparently. Serious issues should be escalated. That was her “justice.”
But in the host culture, things worked differently.
What was happening in a high-context culture
The host country was a high-context culture — a communication style where meaning is conveyed not through words alone, but through the atmosphere, relationships, and unspoken signals.
In this cultural context:
- Publicly overruling a superior is the ultimate taboo. If you need to challenge a proposal, do it privately after the meeting
- The interpreter stopped translating for a reason. The local team members were sharing emotions in their own language — an in-group moment that outsiders shouldn’t interrupt
- Reporting directly to headquarters signals “loss of control.” In collectivist cultures, problems are resolved internally before being shared externally
She did “the right thing.” But she got the context wrong.
Class discussion on this case was heated. Some classmates insisted: “Problems should be shared openly — she was right.” Others argued: “Right or wrong isn’t the point — she lost trust, and that’s the problem.” I could see both sides. In IT, escalating incident information immediately is a cardinal rule. Sitting on a problem until it’s too late is far worse. But that’s the rule in my cultural operating system — and recognizing it as just that, not as universal truth, was the shift this course produced.
The discussion about the interpreter was particularly revealing. Classmates from low-context cultures (direct, explicit communication) felt “not translating is dishonest.” But those with high-context experience explained: “That was a moment not meant to be translated. The team was processing emotions together — an in-group activity.” Same scene, completely different interpretations. We were experiencing cross-cultural walls right there in the classroom.
Different operating systems for “justice”
Listening to this, I found a useful analogy in my own field: operating systems.
North American OS: Transparency, speed, direct communication = justice
Asian OS: Harmony, face-saving, indirect communication = justice
Run the same application (a business decision) on different operating systems, and you get different outputs. What registers as “appropriate escalation” on the North American OS becomes “destruction of trust” on the Asian OS. And the user (the person affected) thinks it’s an app bug, when it’s actually an OS compatibility issue. You can’t fix it by patching the app — you need to understand the underlying OS.
The key insight: it’s not about which OS is “correct.” It’s about understanding which OS the other person is running and adjusting your behavior accordingly — ensuring compatibility. That is the essence of behavioral CQ.
This “OS analogy” was the framework I connected with most viscerally. As an IT engineer who deals with operating systems daily, “culture = OS” and “behavior = application” made immediate sense. And just like in IT, OS-level issues don’t show up in surface-level error messages. You have to dig into deeper layers to find the root cause. Cultural collisions work the same way.
“OS differences” exist in every workplace
This applies directly to domestic workplaces too.
Consider a mid-career hire from a foreign-owned company joining a traditional Japanese firm. At her previous employer, “share problems immediately and openly” was the norm. Doing the same at the new company earns her the label “can’t read the room.”
The reverse is equally true. Someone steeped in Japanese “nemawashi” (behind-the-scenes consensus-building) joins a foreign firm and stays silent in meetings — only to be evaluated as “has no opinion.”
Neither is “wrong.” It’s an OS difference. Simply recognizing this changes how you see the other person.
In my own IT career, I experience this “OS difference” daily. In meetings with our Indian headquarters, the style is “state the conclusion first, discuss afterward.” In meetings with Japanese clients, you start with background context and build consensus gradually toward a conclusion. Same “meeting” application, entirely different OS.
Once, during a call with India, our Japanese team began a careful background explanation, and the Indian side cut in: “What’s the conclusion?” The Japanese team felt “that was rude — we’re still explaining.” The Indian side felt “they’re taking forever to get to the point.” Zero malice on either side. Just different operating systems. Connecting that experience to this case discussion, it finally clicked: “That was an OS incompatibility.”
Three steps for behavioral adjustment
Based on what I learned, here’s how to approach behavioral adjustment:
- Observe: Understand the cultural context. Read not just words, but silence, expressions, and atmosphere
- Recognize your own assumptions: Ask “Why do I believe this is how it should be done?”
- Adjust your behavior: Choose methods that fit the context — deliver feedback while preserving face, hold sensitive conversations privately
Step three is the hardest. It’s not about betraying your beliefs — it’s about changing how you deliver them. The goal stays the same; the approach adapts to the culture.
For example, if you need to say “this proposal has a problem”: in a low-context culture, you’d raise it directly in the meeting — that’s honesty. In a high-context culture, you’d share it privately afterward, framing it to preserve the other person’s dignity — that’s respect. Different delivery, same substance.
This isn’t just a foreign-relations skill. Even within Japan, it comes up constantly. When you need to flag a technical issue in front of a client’s senior executives, blunt facts might mark you as “tone-deaf,” while staying silent risks a bigger problem later. Choosing words carefully, timing delivery right, reading the room — this delicate work is the Japanese version of behavioral CQ.
One more realization from the course: behavioral adjustment is a strategic choice, not a compromise. The manager in the case wasn’t wrong to escalate to headquarters. The problem was bypassing the local team in the process. If she had first shared the issue with the local team and suggested “let’s report to HQ together,” the outcome might have been very different. Same goal, different route. That is behavioral adjustment — fundamentally different from “just going along.”
Have you recently felt, “I’m doing the right thing, so why doesn’t the message land”? If so, it might be an opportunity for behavioral adjustment. You don’t need to change the substance. Just try changing how you deliver it. The results can be surprisingly different.
The instructor closed with a line I keep coming back to: “Discomfort ≠ error.” Discomfort is simply a signal that a different cultural premise is at work. Converting that signal into “wrong” is cruise control. Receiving it as a signal and asking “why?” is mindfulness. That single distinction may be the most practical takeaway from this entire course.
Recommended reading
For foundational understanding of cross-cultural communication
Edward T. Hall, Beyond Culture (Anchor Books)
The classic work that introduced the concepts of high-context and low-context cultures. Hall’s framework explains why the same words can carry different weights depending on cultural context — essential background for understanding why “doing the right thing” can go so wrong.
→ Next: [Cross-Cultural Management #5] examines what happens when a team of 68 people from 27 countries collapses — and how to rebuild a multicultural team.
