Six weeks later, nothing had moved. No response, no counter, no forward motion. When I finally got clarity through an intermediary, the answer I received was almost funny: there had never been a “yes” in that room. There had been a series of signals I didn’t know how to read, in a language I didn’t know existed.
Mind you, I studied Japanese studies (I failed, but at least I tried). I should have known. But when cultures and expectations clash…they clash.
That moment cost me weeks. The DaimlerChrysler version of the same story cost thirty billion dollars.
The friction that kills cross-border deals is almost never the obvious kind. It’s not food, or greetings, or whether you hand someone a business card with one hand or two. Those are surface protocols. A foreigner who fumbles them is forgiven immediately. The Japanese know you’re foreign. The Germans will tell you directly that you got something wrong. The correction is fast and cheap.
The expensive friction lives one level deeper.
It lives in the place where both sides believe they communicated clearly. Where the British executive who said “that’s quite interesting” genuinely believes he sent a signal, and the German who heard it genuinely believed he received good news. Where the American VP thought the Japanese nodding meant alignment, and his Japanese counterpart thought the nod was, appropriately, an acknowledgment that he was listening.
Neither side realized the gap existed. That’s what makes it dangerous.
Two Operating Systems, One Room
I’ve watched this play out enough times now to see the underlying structure. Every culture I’ve operated in falls into one of two trust architectures, and this distinction predicts more about business behavior than almost anything else.
Some cultures build trust through competence. Show up prepared. Deliver on commitments. Keep the personal and professional separate. The relationship forms around the transaction. Germany works this way. The Netherlands. Scandinavia. Large parts of the Anglo-American business world. You earn trust by performing, and once you have it, a contract is a contract.
Then there are cultures where the transaction cannot precede the trust. You eat together first. You meet the family first, or meet through the family’s network. You commit time without an apparent agenda. Only after the relationship has substance does the business conversation become possible. China works this way. Japan, in its own distinct form. Most of Southeast Asia. Parts of the Gulf.
The collision between these two architectures is where most cross-border business failures actually originate. Not in incompatible products or bad market timing, but in two groups of intelligent people who held fundamentally different assumptions about what had to happen before a deal could be real.
eBay learned this in China. They held roughly 85 percent market share when a domestic competitor began offering something eBay couldn’t understand the value of: instant messaging, built directly into the purchasing flow. Chinese buyers spent an average of 45 minutes chatting with a seller before completing a transaction. eBay saw this as friction. Their competitor saw it as the product. Within three years, eBay’s share had collapsed. They weren’t beaten by a better platform. They were beaten by a better understanding of what trust requires before money moves.
The Interpretation Layer
Below the trust architecture question sits a subtler problem, and I’ve found it harder to see because it masquerades as communication.
Erin Meyer, in her work on cultural contrast, made an observation that should be required reading before any international negotiation. The directness of a culture’s general communication, she found, tells you almost nothing about the directness of its feedback. These are two separate dimensions, and they can point in opposite directions.
The British are among the most sophisticated practitioners of this inversion. General communication in the UK is relatively explicit, relatively direct. But criticism is delivered through layers of understatement so compressed that they function as code. “I almost agree” means “I don’t agree at all.” “That’s not bad” means “that’s good.” “Very interesting” means the proposal is nonsense. “By the way”...slipped in at the end of a meeting, casually…signals the entire point of the conversation.
A German manager who moved to London spent months believing his performance was strong. His British line manager had told him things were going well, with a few minor suggestions. When it emerged that the manager was close to being let go, the German read back through those conversations and found, embedded in the language, explicit warnings he had processed as casual observations. The British system wasn’t ambiguous. It was precise. He simply didn’t have the decoder.
BMW bought Rover and spent years unable to understand why problems kept escalating that no one had flagged. British staff described serious operational failures as “a few slight issues on the production line.” German engineers, expecting directness, heard exactly what was said. The downstream cost of that gap is well documented.
What I find instructive about this isn’t the failure itself. It’s that both sides were using language they believed was unambiguous. The British thought they were communicating clearly. The Germans thought they were listening carefully. The problem wasn’t dishonesty or incompetence. It was that two groups were running different interpreters on the same words.
France adds another layer of complexity to this. French professionals tend toward high-context communication in general, meaning a great deal is implied rather than stated. Yet French feedback culture is among the most direct in Europe. A French manager who thinks your analysis is weak will tell you so, clearly and without the diplomatic scaffolding an American or British executive would construct around the same observation. While some would think this is a contradiction, it’s rather two separate cultural variables that many Western frameworks tend to collapse into one.
I’ve pitched the same product to companies in Paris and in San Francisco. The San Francisco room asked how fast I could scale. The Paris room wanted to understand the theoretical foundations of the model before considering the numbers. Neither question was wrong. But walking into Paris expecting San Francisco questions, and San Francisco expecting Paris questions, produces two different versions of a meeting that goes nowhere.
The Decision That Isn’t Made When You Think It Is
The Japanese “hai” problem is well known in principle. Less well understood is the organizational logic behind it.
When I sat in that Kuala Lumpur room with my potential Japanese client watching the nodding and saying nothing about agreement or disagreement, I was watching something called ringi in action. Or rather, I was watching the pre-ringi phase, in which a foreign proposal was being received but had not yet entered the actual decision-making system.
The ringi process requires a formal document to circulate from the lowest relevant level upward, each person in the chain stamping their seal in a direction that signals their position. This can take weeks. Toyota, famously, spends months on the planning and consensus-building phase for major decisions. American competitors, operating on a quarterly logic, spend a fraction of that time. But Toyota’s implementation rate at scale is close to frictionless. The total cycle time, from idea to execution, may not be longer. It’s just distributed differently than Western companies expect.

The operational mistake I see repeatedly, and have made myself, is assuming that a positive meeting means a decision is in motion. In Japan, a positive meeting often means a decision hasn’t started yet. The nemawashi, the informal network of conversations that precede formal approval, may not have begun. The person you’re meeting with may not be the decision maker in any sense that matters to the outcome. Understanding this doesn’t just change how you interpret silence. It changes your entire timeline assumption, which changes your resourcing, your forecasting, your patience.
Germany presents the mirror image of this pattern in a different form. German business culture is relatively flat in hierarchy, and decisions are reached through genuine consensus. But what distinguishes German consensus from, say, American team discussion is that German decisions tend to be treated as commitments rather than starting positions. When an American executive says “we’ve decided to go with option A,” this often means the team is aligned on option A as the current best direction, with the implicit understanding that new information could shift it. When a German counterpart makes the equivalent statement, the expectation is that the decision is closed. Reopening it isn’t a normal iteration as an American would see it, it signals full-blown instability to a German.
I’ve watched American counterparts return from a German meeting believing they had successfully planted seeds for future renegotiation, while the German side left believing the matter was settled. The first phone call in which the American tried to revisit the decision was experienced, genuinely, as a breach.
Germans take ages to make a decision looking at every little detail and angle that could go wrong, working through red tape after red tape. Hence a decision made is a decision made. Americans on the other hand, oftentimes just go for it and iterate along the way. Even running into huge roadblocks that could’ve been prevented by simply taking a little more time in the decision process.
Neither is right or wrong. But it’s best to be prepared for these cultural differences. Personally, I try to mix both approaches: let’s go for it, but let’s think about the biggest issue that could arise and we could foresee now.
What the Frameworks Don’t Tell You
The academic models of cultural difference, and they exist in reasonable numbers, are useful as orientation tools. They tell you where to look. They don’t tell you what you’ll find.
I’ve operated in enough markets now to know that cultures are not monolithic. Singapore presents itself as an East-West hybrid, English-speaking and institutionally Western, and this is partly true. But the hierarchy beneath the surface is real, the face-saving is real, and assuming that a professionally calibrated Singapore counterpart thinks about conflict and authority the way a London-based peer does is a mistake I’ve watched many operators make once. Only once, usually.
Malaysia compounds this further. In a single meeting, you can be sitting across from Malay, Chinese Malaysian, and Indian Malaysian professionals, each operating with subtly different assumptions about directness, relationship depth, and what constitutes an appropriate pace for getting to the point. The country is not one cultural tradition. It’s three, with a common passport.

What I’ve learned is that cultural competence isn’t a body of knowledge you acquire and then possess. It’s a calibration practice. You develop sensitivity to signals that suggest the operating system is different from your own, and you slow down enough to run your reading of the room through more skeptical filters. This is what 25 years across fifteen-plus markets actually produces. Not fluency in any single culture. Fluency in the transitions.
The German teenager in an English class, forced to convert direct statements into polite British phrasing, said something I find more analytically accurate than most cross-cultural training I’ve encountered: “What the hell? All the British do is lie to each other with this.” She wasn’t wrong about the mechanics. She was wrong only about the value judgment embedded in “lie.” The British system isn’t dishonest. It’s differently encoded. Understanding the difference between a broken system and a system you haven’t learned yet is, in my experience, the actual skill.
The thirty-billion-dollar DaimlerChrysler collapse is frequently told as a story about corporate strategy or executive ego. What the people inside it described was something simpler. Germans who followed detailed process manuals operating alongside Americans who valued spontaneous judgment. Germans who used vacations as expected, Americans who found this incomprehensible during a crisis. Germans who offered direct criticism of a proposal and watched American colleagues experience this as a personal attack. Two groups who were, by any reasonable standard, trying to build the same thing, who spent years talking past each other in a language neither realized was different.
Richard Lewis, whose firm designed a comprehensive cross-cultural training program for the merger, completed the proposal and won agreement on its general principles. Implementation still depended on approval from DaimlerChrysler University. Soon afterward, integration lead Andreas Renschler changed jobs. Lewis’s firm never heard from DaimlerChrysler again. Most of the executive teams were deployed without any preparation at all.
That detail is the one I keep returning to. The solution existed. The knowledge was available. The gap wasn’t in understanding that culture matters. It was in treating that understanding as optional, as a nice-to-have that could be deprioritized when things got busy.
Culture is never optional when you’re in the room. The only choice is whether you’ve done the work of understanding it before you arrive.
So, next time you’re in an intercultural negotiation/deal-making/working environment, try to leave your ego at the door, and try to understand that you and your counterpart might be talking past each other, not out of spite but out of culture.


