The cursor is spinning, again. I’ve force-quit the conferencing app 19 times-or maybe it was 29, I lost count after the tenth frozen frame of a colleague’s mid-sneeze face. My laptop is running so hot I could probably fry a single quail egg on the trackpad, but I’m too busy staring at the 12 boxes on my screen to care about hardware degradation.

We are 19 minutes into the kickoff meeting. This is the moment where the project either takes flight or, more likely, belly-flops into a pool of expensive misunderstandings.

On the left side of the grid, the Berlin team is leaning forward, their brows furrowed in that specific German way that suggests they’ve already found 9 flaws in the proposed architecture. In the top right, the São Paulo contingent is smiling, but their eyes are darting toward their phones. At the bottom, the Seoul team is a wall of polite, muted squares.

We’ve all agreed that English is the language of this project. We’ve written it into the “Operating Model” document, a 49-page PDF that cost roughly $9,999 in consultant hours to produce. It says: All communications will be conducted in English to ensure maximum transparency and efficiency.

The Edible Illusion

It is a beautiful lie. It’s the kind of lie that Wei C.M., a food stylist I worked with back in the day, would appreciate. Wei was a master of the “edible illusion.” I remember watching her prep a roast turkey for a commercial. It looked succulent, golden-brown, and steaming.

In reality, the bird was stone cold and raw. She’d painted it with a mixture of mahogany wood stain and dish soap to get that sheen. The “steam” was just a microwaved cotton ball hidden in the cavity. Our English-only meetings are that turkey. They look perfect on the “project health” dashboard, but if you actually tried to digest the information being exchanged, you’d end up with corporate salmonella.

As the Berlin lead starts explaining the sprint velocity requirements-using words like “interdisciplinary” and “granularity” with a speed that would make a native speaker dizzy-the chat window remains silent. But I know for a fact that the real meeting is happening elsewhere.

My phone, sitting face-down on the desk, is vibrating so hard it’s practically walking toward the edge. I know what’s in those notifications. There are at least 39 unread messages in the “Projeto Sampa” WhatsApp group and probably double that in the KakaoTalk room.

I’m part of the problem. I’m nodding. I’m saying “Yes, that makes sense,” even though I realized 9 minutes ago that I have no idea what “de-coupling the legacy middleware” actually entails in this context.

I once agreed to a 9-month delay because I thought the word “defer” meant we were giving it top priority. I spent three weeks working on the wrong end of a database because I was too embarrassed to admit that the “English” being used was actually a dialect of Technical Esperanto that only three people in the world truly speak.

The silence of the Korean team isn’t a lack of opinion. It’s a bottleneck. They are processing the German-accented English, translating it into Korean, debating the technical feasibility among themselves in a side-channel, and then trying to formulate a response that is both technically accurate and culturally respectful in a language they only use for work.

By the time they’re ready to speak, the meeting has moved on to the next three agenda items. We pretend this is efficient. We call it “streamlining.” But what we’re actually doing is creating a massive amount of cognitive debt.

The Polite Fiction

Every time someone stays silent in a meeting while their thumbs fly across a private chat, we are losing data. We are losing the 19% of nuance that actually prevents the project from exploding six months down the line.

I’m currently watching the São Paulo project manager’s video feed. He’s looking directly at the camera, but his pupils are moving in that rhythmic, horizontal way that says he’s reading a long text on his second monitor. He’s probably explaining to his engineers that the “English” instructions they just received are actually impossible to implement and they should just keep doing what they were doing before.

This is the polite fiction of the global lingua franca. We use it as a thin veneer of unity, while underneath, the work is being rerouted through seven different languages and a dozen private channels. It’s a decentralized game of telephone where the stakes are millions of dollars and the sanity of everyone involved.

Wait, why did I just say seven languages? We only have three teams. I’m getting ahead of myself. The point is the noise-the silent, digital noise that fills the gaps where actual conversation should be. I’ve realized that the more we insist on “English-only,” the more we drive the real decision-making into the shadows. We are afraid of the messiness of translation, so we choose the clean, sterile void of “understanding” instead.

The price of a shared language is often the loss of the very ideas that language was meant to convey.

I’ve spent the last 239 days of my life in these types of meetings, and I’m starting to think that the traditional model of international collaboration is fundamentally broken. We treat language as a binary-either you speak it or you don’t. But language is a spectrum of energy. When you force everyone into one narrow band of that spectrum, you lose all the heat.

I remember a moment with Wei C.M. where the illusion broke. The director wanted a shot of a burger being bitten into. You can’t bite a “styled” burger; it’s held together with pins and cardboard. Wei had to build a real one, but she was so used to the fake ones that she forgot how to make it look “natural” without the wood stain. She struggled for 49 minutes before she realized she just needed to let the lettuce be messy.

Cooking the Turkey

That’s where we are with our meetings. We are so obsessed with the “mahogany wood stain” of perfect English minutes and “clear” action items that we’ve forgotten how to let the conversation be messy. We need the side-conversations. We need the native-language debates.

The problem isn’t that people are talking in Portuguese or Korean; the problem is that those conversations are happening outside the flow of the project. This is why the approach of Transync AI fascinates me.

It’s not about forcing everyone to be a linguistic gymnast. It’s about acknowledging that the “raw turkey” of our meetings needs to actually be cooked. If everyone can contribute in the language where their thoughts are fastest and most precise, the “official” meeting might actually start to resemble reality.

I recently tried to explain this to my boss, but I think I used too much jargon. I told him we were “optimizing our linguistic throughput to minimize subterranean workflows.” He just blinked at me. I should have just told him the turkey is raw.

The Sinking Ship

The irony is that as I write this, I’m listening to the Berlin lead finish his monologue. He asks, “Does everyone agree with this approach?”

“There is a 9-second pause.”

“Yes,” says the São Paulo PM, his eyes still flicking toward his second monitor.

“Understood,” says the Seoul lead, his mic clicking off immediately after.

Nothing was decided. Nothing was understood. The project will move forward on the strength of 19 different assumptions, and we will all meet again in 9 days to wonder why the milestones were missed.

We will force-quit our apps, we will stare at the spinning wheels, and we will pretend that as long as we are all speaking English, we are all speaking the same language. I’m tired of the wood stain. I’m tired of the microwaved cotton balls. I want a meeting that is as messy and as real as the work itself. I want the side-conversations to be the front-conversations.

As I log off, I see one final message pop up in the private group. It’s an emoji of a sinking ship. I give it a thumbs-up. This time, I’m pretty sure I know exactly what it means. We are all vibrating on the same frequency of disaster, and no amount of “English-only” policy is going to change that until we change how we actually listen.

The cursor stops spinning. The laptop starts to cool down. 19 people leave the call. And the real work-the messy, multilingual, chaotic work-finally begins in the dark.