Operating in three languages and three regulatory cultures. What actually changes in execution.

Running a business across three working languages and three regulatory cultures is discussed, when it is discussed at all, in the language of diversity and global mindset, which is not useful to anyone actually doing it. The useful version is concrete: specific things change in how the business executes, and a leader who does not adjust for them watches the execution degrade in ways that are hard to diagnose because they do not look like language problems on the surface.

I run a business across different regulatory contexts, and the adjustments that matter are operational rather than cultural in the soft sense. The soft-culture advice, be respectful of differences, is true and useless. The operational adjustments are specific, learnable, and the difference between a multilingual business that executes cleanly and one that drifts quietly out of alignment across its language lines.

The single-language reporting standard

The first and most important adjustment is a single language for anything that is a record. Strategy documents, board materials, client-facing deliverables, contracts, regulatory filings, and the written decisions the company runs on are all in one language, regardless of what language the conversation that produced them happened in. In my case that language is English, because it is the common denominator across the markets and the counterparties.

The reason is drift. When the same strategy exists in three languages, the three versions diverge, slowly and invisibly, as each is edited in its own language by people who never compare it to the others. Six months later the English version, the Spanish version, and the Russian version of the same plan say subtly different things, and the teams working from each are executing subtly different plans while believing they are aligned. The single-language standard for records prevents the divergence at the source, because there is only one version and everyone reconciles to it.

Conversation is different from record. The internal strategy discussion can and should happen in whatever language the participants think best in, and forcing a Russian-speaking team to strategise in English degrades the quality of the thinking to serve a consistency the conversation does not need. The rule is precise: think and discuss in any language, but record in one. The moment a decision becomes a document the company will act on, it is in the record language, and the informal multilingual discussion that produced it does not become three competing written versions.

Regulatory culture shows up in vendor relationships

The three regulatory cultures differ in ways that show up most concretely not in the regulations themselves but in how vendor and counterparty relationships work, and a leader who reads only the regulations misses the part that affects execution daily.

European regulatory culture, in the contexts I operate in, is process-heavy and documentation-first. The vendor relationship runs on written agreements, formal change processes, and a paper trail that assumes the regulator may one day read it. The execution adjustment is that everything is documented as it happens, because the documentation is not overhead, it is the medium the relationship runs in, and a European counterparty reads the absence of documentation as disorganisation.

MENA regulatory culture, again in the specific contexts I work in, is more relationship-weighted. The formal framework matters, but the relationship and the trust between the parties carry more of the weight, and a vendor relationship that would run on paper in Europe runs on a combination of paper and personal relationship in MENA. The execution adjustment is that the relationship investment is not a nicety, it is load-bearing, and a leader who tries to run a MENA counterparty relationship purely on documentation without the relationship underneath finds the relationship does not perform when it is needed.

The markets adjacent to Latin America bring their own pattern, where the pace and the formality sit differently again, and the adjustment is to match the counterparty’s actual working rhythm rather than imposing the rhythm of whichever market the leader is most used to. The general principle across all three is that the regulatory culture determines how the commercial relationship runs, and the leader operating across all three carries three different modes of running a counterparty relationship and switches between them by context rather than applying one mode everywhere.

Translation lag breaks weekly cadence

A subtle operational problem in a multilingual business is that translation introduces a lag, and the lag breaks the cadence that a business runs on if it is not managed. A decision made in one language on Monday that needs to reach a team working in another language does not reach them on Monday; it reaches them after someone has translated it, which may be Wednesday, and the team that needed it to start their week starts their week without it.

The lag is invisible because no one experiences it as a translation delay. The team working in the other language experiences it as information arriving late, and the leader who made the decision experiences it as a team that is slow to act, and neither diagnoses the translation lag in between. Over a quarter, the lag compounds into a persistent misalignment where one part of the business is always a step behind another, not because anyone is slow but because the information is always crossing a language boundary that adds delay.

The adjustment is to build the translation into the cadence rather than treating it as something that happens after the decision. The decisions that need to cross language lines are translated as part of making them, not after, so they reach every team at the same point in the week. In practice this means the record language document is produced immediately and the teams that work in other languages either work from the record language directly, if they can, or receive the translation as part of the same communication rather than as a delayed follow-up. The cadence holds only when the translation is inside it.

The parallel narrative problem

The hardest multilingual problem is the one I think of as parallel narratives: the business develops a different internal story about itself in each language, and the three stories drift apart until the company does not have one shared understanding of where it is and where it is going but three, one per language community.

This happens because narrative lives in conversation, and the conversation happens in language communities. The Russian-speaking part of the team develops, through its own discussions, a particular understanding of the company’s priorities and challenges. The English-speaking part develops another. The Spanish-speaking part a third. Each is coherent internally, each is reasonable, and they are not the same, because they were formed in separate conversations that never fully met. The company ends up with three parallel narratives about itself, and the misalignment is deep because it is not about facts, which the single-language records keep straight, but about interpretation, which lives in the untranslatable texture of how each community talks about the work.

The adjustment is deliberate narrative alignment, which is different from information alignment. It is not enough to ensure everyone has the same facts; the leader has to actively tell the same story about those facts across all three language communities, in each language, repeatedly, so that the interpretation stays shared and does not fork into three. This is real work, it does not happen automatically, and it is the work a monolingual single-market leader never has to do because their whole company forms its narrative in one conversation. The multilingual leader has to hold three conversations to the same story, and holding them there is a continuous effort rather than a one-time alignment.

What this adds up to

The multilingual, multi-regulatory business is not a monolingual business with translation added. It is a structurally different thing to run, with failure modes that a single-language single-market business never encounters: record drift across language versions, counterparty relationships that run on different logics by region, cadence broken by translation lag, and narratives that fork by language community. None of these is visible as a language problem on the surface, which is why they are dangerous, and each has a specific operational adjustment that contains it.

The advantage, and there is one, is that a business built to run cleanly across three languages and three regulatory cultures can operate in markets that a monolingual single-market business cannot reach without stumbling. The adjustments are a cost, but they buy a genuine reach, and the leader who has built the operational discipline to run across the language and regulatory lines has built something that travels into markets where the single-language single-market business does not function. The discipline is the price of the reach, and for a business whose markets are genuinely spread across languages and regulatory cultures, it is a price worth paying because the alternative is not a simpler business, it is a business that cannot go where the opportunity is.