I grew up speaking two languages and now I work in two more. Arabic at home, English at school, Python and SQL at work. The grammar I think in changes depending on who’s in the room and what’s on the screen.
Most people who work this way assume it’s a soft skill. Code-switching. Cultural fluency. Useful for getting along but not load-bearing on the work itself.
I think they’re wrong. I think bilingualism, in any pairing, is a design discipline.
What bilingual design forces
When you design something that needs to live in two languages, you can’t treat one as primary and the other as a translation. The system has to hold weight in both directions. If the English wordmark is the brand and the Arabic is “the translation,” the system is broken. Because to half the market, the Arabic is the brand and the English is the translation. The work fails the second you let one of them be derivative.
Bilingual design forces you to design the underlying idea, not just the surface that expresses it. The idea has to be strong enough that both surfaces can hold it. If it only works in one language, it wasn’t actually a brand. It was a wordmark.
The same problem, in other clothes
This isn’t only about Arabic and English. The same discipline applies any time you’re translating an idea across two registers that both matter.
A great technical leader is bilingual in code and business. They can talk to engineers about architecture and to executives about quarter-over-quarter without switching brains in between. The translation isn’t happening in the moment. It happened earlier, in their thinking, when they figured out what the idea actually was, underneath the language.
A great designer is bilingual in craft and constraint. The aesthetic surface and the operational reality. Most bad design fails one of these two tests. It’s beautiful and unbuildable, or buildable and forgettable. Bilingual design holds both at once.
A great teacher is bilingual in expert and beginner. They remember what it was like not to know the thing, while still knowing it. That’s why they can answer the obvious question without making the asker feel small.
The cost of monolingualism
What happens when you only speak one of them? You optimise for the audience that speaks your language and treat the other as a translation problem to be solved by someone downstream. You hand the Arabic to “localisation.” You hand the architecture explanation to “comms.” You build the technically correct system and then wonder why the stakeholders never trust the dashboard.
That handoff is where the work loses its integrity. Because the person on the other end of the translation has to recover the underlying idea from a surface that wasn’t designed to carry it.
Building the idea, then dressing it
The bilingual discipline forces you to do the hardest part of the work first. Strip the idea down to something that doesn’t depend on which language you’re standing in. Make sure the idea itself is strong. Then dress it in whichever surface the room needs.
It’s slower, the first time. But it’s the only way the work survives the translation.