A project lead in Bangalore watches her German counterpart challenge the plan in front of thirty people on an all-hands call, without softening a word of it. The Indian team's read afterward:

“He was disrespectful, maybe even trying to undermine us in front of leadership.”

The German team's read:

“Obviously you flag a flawed plan in the room — staying quiet would have been the dishonest move.”

Nobody in that call was wrong.

They were running different operating systems, and neither side knew it.

THE GLOBAL WORKPLACE HAS SOLVED THE DISTANCE PROBLEM

This scene, or a version of it, plays out constantly in captive centers, shared services hubs, and distributed engineering teams — anywhere an organization has decided that talent doesn't need to sit in one building anymore. The infrastructure for global operations has gotten genuinely good. Video latency isn't the problem it used to be a decade ago. Time-zone overlap tools exist. English has become the default working language almost everywhere.

What hasn't caught up is the assumption that culture will sort itself out once the logistics are solved.

It doesn't. It compounds.

When people interpret the same behaviour through different cultural operating systems, small misunderstandings don't always stay small. They become assumptions about intent, capability, attitude and trust.

THE COST OF SKIPPING THIS IS DOCUMENTED, NOT THEORETICAL

The DaimlerChrysler merger is the textbook case, and it's worth revisiting because the failure wasn't strategic — it was cultural, and it was entirely foreseeable.

German engineering culture ran on formal hierarchy, methodical consensus-building, and a low tolerance for ambiguity in decision-making.

American management culture at Chrysler ran on speed, individual accountability, and comfort with iterating in public.

Both approaches had produced strong independent results.

“Combined without translation, strong cultures can become sources of friction rather than sources of strength.”

The result was years of friction, executive departures, and synergies that never materialized on the scale the deal assumed.

Technology and the org chart integrated.

The culture did not.

And that is the piece that can determine whether combined teams outperform or underperform the sum of their parts.

WHY “HIRE GLOBALLY, MANAGE THE SAME WAY EVERYWHERE” DOESN’T HOLD

The idea sounds reasonable:

Build one operating culture. Hire people who fit it. Avoid adapting management by geography.

It can work, especially in younger, flatter organizations with less inherited hierarchy.

But in most multinational operations — particularly GCCs and shared services spanning several countries — the costs of this approach often surface elsewhere.

Talent leaves citing vague issues of “fit.”

Decisions stall because disagreements aren't openly escalated. Direct feedback intended as helpful can land as a reprimand, while cultural norms discourage the recipient from pushing back.

These rarely appear as “culture problems” on a dashboard.

They show up as:

• Turnover
• Slower decision cycles
• Unresolved disagreements
• Lower engagement
• Reluctance to escalate
• Misinterpretation of feedback
• Friction between headquarters and regional teams

The problem is not necessarily that people disagree.

The problem is that they may not understand why the other person is disagreeing — or what the disagreement means.

THE LANGUAGE BEHIND THE DIFFERENCE

Erin Meyer's work on high- and low-context communication, and Geert Hofstede's research on power distance, give leaders a practical language for understanding these differences.

They explain why communication, feedback, and hierarchy can be interpreted very differently across cultures.

A direct statement can be interpreted as honesty in one environment and aggression in another.

Silence can signal agreement in one culture and disagreement in another.

Deference can signal respect in one context and lack of ownership in another.

Neither framework replaces judgment.

But both can help leaders identify what might otherwise be dismissed as “personality” or “attitude” — and investigate the underlying cause.

WHAT BUILDS COHESION ACROSS DISTANCE?

The answer isn't another values statement.

It is a set of deliberate operating practices.

01 — Make Decision Rights Explicit, Not Inherited

Who can say no?

Who gets consulted?

Who gets informed?

These should be written down per workstream, not assumed from whichever country's norms happen to dominate the room that day.

When decision rights are ambiguous, people fall back on the behaviours their own cultures taught them.

Clarity reduces the need for cultural guesswork.

02 — Create a Channel for Cross-Geo Friction

A weekly delivery sync can surface schedule risk.

It rarely surfaces:

“The India team hasn't pushed back on a bad requirement in six weeks because nobody explicitly invited dissent.”

That is a different kind of risk.

Create spaces where teams can discuss how they are working together, not just what they are delivering.

Make dissent without specific invitation the norm through explicit instructions, especially when working across cultures where disagreement may not be expressed in the same way.

03 — Rotate Whose Norms Set the Room

If every escalation call defaults to the norms of wherever headquarters sits, the other geographies may comply without ever fully engaging.

Alternate which office's meeting conventions govern.

Let different teams occasionally determine:

• How the meeting opens
• How disagreement is raised
• Who speaks first
• How decisions are documented
• How follow-ups happen

This is difficult given organizational structures and decision-making power.

But if successfully governed, even for a few weeks, it can give everyone a glimpse into the cultural nuances of how different regions and individuals run the same meeting.

04 — Train the Middle, Not Just the New Hires

Cross-cultural onboarding decks reach people in their first month.

But onboarding isn't where culture is primarily experienced.

It is experienced through managers.

The managers who've been running teams the same way for eight years are the ones shaping day-to-day culture — and they're the ones least likely to get retrained.

If the middle layer doesn't change how it manages disagreement, feedback and escalation, the organization will continue reproducing the same friction.

THIS DOESN'T REQUIRE A MASSIVE PROGRAM

None of these require a large budget or a consulting engagement.

They require something more fundamental:

Someone senior enough to say that the friction is real, name it specifically, and build a structure around it.

The alternative is to hope goodwill closes the gap.

Goodwill helps. It doesn't translate operating systems.

THE LEADERSHIP QUESTION

The question for leaders isn't:

“How do we make everyone work the same way?”

It is:

“What needs to be common, and what needs to be translated?”

Decision rights may need to be common.

Strategic priorities may need to be common.

Performance standards may need to be common.

But the way people challenge authority, give feedback, signal disagreement, build trust and participate in meetings may require translation rather than uniformity.

That distinction matters.

THE TAKEAWAY

Cohesion across borders isn't a byproduct of good tooling, a shared language, or a well-written values statement on the intranet.

It's the output of leaders who treat cultural difference as an operating variable to be actively managed — the same way they'd manage currency risk or supply-chain latency — rather than a soft topic to be addressed once with a training session and then assumed solved.

The organizations that get real competitive advantage from global teams aren't necessarily the ones that eliminated cultural difference.

They're the ones that built the muscle to translate across it.

Consistently.

At every layer of the hierarchy.

Not just at the top where the values statement gets written.

ONE PLACE TO START

Pick your highest-friction cross-geo working relationship right now.

Then ask both sides — separately:

“What do you wish the other side understood about how you make decisions?”

Don't ask what the other team is doing wrong.

Ask what they wish the other team understood.

The answer will tell you more than any culture survey you could commission.