When I tell people I work in nine languages, the first reaction is usually either skepticism or the assumption that this means I switch fluently between them in every meeting. Neither is right.
The operational reality of a nine-language practice across EMEA is different from what the phrase suggests, and what it has taught me about organizational design is probably the most transferable thing I have learned in the last four years.
What nine languages actually means in practice
English is the dominant operating language for architecture reviews, commercial negotiations, and executive communications across the region. It is the language in which deals are written, in which SLAs are negotiated, and in which most engineering debates take place.
The other eight languages are not secondary. They are the access layer.
Swedish for the Nordic engineering teams who are more precise and more cautious in Swedish than in English. German for the industrial SaaS customers in the DACH region where switching to English in a sensitive commercial conversation signals something about the relationship’s trust level that you do not want to signal. Turkish for calls where the other side has been speaking English all day and switches to Turkish with me after forty minutes, not because their English is insufficient, but because they are tired and they want to say something hard directly without the cognitive overhead of translation.
French for Paris, which is its own operating system. Norwegian because Norwegian engineers politely endure Swedish if you insist on it and will not tell you it is slightly wrong.
The point is not fluency in nine languages. The point is that the choice of language communicates something that content alone cannot. The choice says: I have made an investment in your context. I am not requiring you to operate in mine.
What code-switching is not
The common frame for multilingual professional environments is “code-switching”: the practice of shifting between languages or registers depending on context. This frame is correct but incomplete, and the part it misses is the most important.
Code-switching implies a cost: the cognitive load of switching, the risk of choosing the wrong register, the possibility of being inauthentic in one language relative to another. In my experience, the cost model is backwards.
The cost is not in switching. The cost is in staying in one language when another would serve the conversation better. The English-only approach to an EMEA practice has a real cost: it filters out the information that people only share in their first language, it creates a false precision in conversations where the other side is translating their actual concern into a form that English accepts, and it builds trust slowly compared to a conversation where the other party feels genuinely met.
The switching itself is not the hard part. The hard part is knowing when to switch and what it means when you do.
What this teaches about organizational design
The nine-language practice was also a 137-consultant-per-quarter bootcamp program at peak, operating across six countries with three reporting chains that did not all trace to the same VP.
The practical discovery: organizational dysfunction in a multilingual environment becomes visible faster than in a monolingual one. When a team in Stockholm and a team in Frankfurt are working on adjacent deliverables for the same customer, the coordination overhead shows up first as a communication friction. They are not miscommunicating because of language. They are miscommunicating because the organizational boundary between them has not been explicitly designed, and language differences make the boundary visible.
In a monolingual organization, that same boundary can stay invisible for months, obscured by the apparent smoothness of shared language. Everyone speaks English, so everyone assumes they understand each other, until a deployment day when they discover they had different assumptions about what “done” meant.
Multilingual teams surface the assumptions earlier because the translation work forces them. You cannot translate “done” from Swedish to German without negotiating what you mean by it.
This is one of the most counterintuitive things I have learned: linguistic diversity makes organizational design requirements more visible, not less. A team that operates in three languages has to be more explicit about its contracts than a team that operates in one.
The practical version
Three things I have learned to do that I would not have learned in a monolingual environment.
Negotiate the operating language before the agenda. When a call includes participants for whom English is not a first language, agreeing at the start which language to use, and giving people explicit permission to use their first language for specific points, changes the quality of what gets said. The technical details that only come out in the native language are usually the important ones.
Use language choice as a deliberate trust signal in commercial negotiations. Switching to the customer’s language for the moment when you are about to say something hard signals something different from staying in English. It says: what I am about to say is important enough that I am not going to let language be a barrier.
Build explicit organizational contracts in writing, always. The lessons about implicit versus explicit contracts apply everywhere, but in multilingual environments they apply with more urgency. A verbal agreement in Swedish between two Swedish engineers will not survive intact when it needs to be implemented by a team in Finland who were briefed in English by someone who thought they understood the Swedish agreement. Write the contract. Write it in the operating language. Translate it if it needs to travel.
The nine-language practice was not designed as a pedagogical exercise in organizational theory. It was just the practice that existed in the region I was hired to serve. What it taught was real, and most of it applies equally well to organizations that operate in one language but assume that shared language means shared understanding.
It does not.