Should we impose a single company language?

Rarely, and never by decree. An imposed single language moves the problem rather than removing it: the gaps in fluency do not disappear, they simply become invisible, because nobody flags that they did not understand. What works is more modest: settle on a language per type of exchange — the team meeting, the written record, the one-to-one — and say so explicitly, rather than leaving everyone to guess each time.

Does Kreol belong in a professional meeting?

It is already there, and denying it changes nothing. The useful question is when it helps and when it excludes. In a sub-group, to unblock a technical explanation or defuse tension, it is often the fastest tool available. In a wider meeting that includes someone who does not speak it, the same move puts a person outside the conversation without anyone noticing.

How do I know whether someone has actually understood an instruction?

Not by asking "is that clear?", a question with only one available answer. The method that works in any language is to have it said back: ask the person to state, in their own words, what they are going to do and in what order. The gap appears immediately, and it appears without anyone losing face.

Do we have to translate every internal document?

No, and trying exhausts the team for a small return. The criterion is consequence: anything that binds someone — a rule, a safety procedure, an instruction whose breach is sanctionable — has to exist in the language of the people who must apply it. The rest can live in one language without harm.

Managing a team in three languages in Mauritius

A team meeting in Ébène opens in French because the manager opened it in French. Ten minutes in, two people settle a technical point between themselves in Kreol, because it is quicker. A document arrives, it is in English, and the discussion moves into English for as long as it takes to read it. Nobody decided anything, and everybody followed.

That is the ordinary experience of managing in Mauritius, and most managers only identify it as a subject the day a decision they believed was clear produces nothing. The temptation then is to make it a general explanation: “it’s a language problem”. Sometimes true, and often convenient.

Following is not being able to contradict

The gap that matters is not between those who understand and those who do not. In a Mauritian professional setting, almost everyone understands. The gap is between those who can object and those who can only nod.

Arguing in a language requires a considerably higher level than following one. You have to qualify, come back on what you have just said, find the phrasing that expresses disagreement without attacking — and do it in real time, in front of colleagues, sometimes in front of a superior. Someone perfectly comfortable receiving an instruction in English can be unable to say, in that language and at that moment, “I don’t think this will work, and here is why”.

What the manager gets instead is a silence they read as agreement. It is the most expensive mechanism in the whole subject, and it is invisible: nothing happens in the meeting, everything happens three weeks later.

The rule that follows is easy to state and uncomfortable to apply: choose the language in which the least fluent participant can still contradict, not the one the group understands on average. It is uncomfortable because it sometimes means running a meeting in French when everyone “speaks English”, or the reverse.

Kreol is not a lapse in professionalism

There is a reading of Kreol as the language of the informal — tolerated, not encouraged. It misses what the language actually does: it is the one in which a misunderstanding gets recovered fastest, and the one in which a technical move is explained without detour.

A team leader who switches for two minutes into Kreol to explain why a procedure exists is doing their job. Banning it in the name of professionalism means removing the most effective tool from the box.

The real question is not permission but who is in the room. The same switch that brings two people together puts the colleague who does not speak Kreol outside the conversation — an expatriate, a recent arrival — and it does so without anyone noticing, because the exclusion takes the form of a warm exchange.

Written English becomes a promotion criterion nobody decided on

Here is the most serious effect, and the least discussed. In many Mauritian organisations, a share of the documents that travel upwards — a board paper, a note to the regulator, correspondence with a parent company — are written in English.

The people who write them become visible. The people who do not stay competent and invisible. After a few years, the management line has been assembled by selection on a writing skill that nobody ever put in a job description or assessed as such.

That is not necessarily unjustified: if the role involves writing to the regulator, the skill counts. What is a problem is that it operates without being stated. A manager who wants to correct it has two immediate levers: name the skill explicitly where the role genuinely requires it, and stop routinely handing the drafting to the same person on the grounds that they write better.

What language does not explain

One last caution, and it is worth as much as the rest. Language is an explanation that is available, visible, and politically comfortable: it implicates nobody. It therefore attracts problems that are not its own.

Three sources of friction are commonly confused in a Mauritian team:

language — the person does not have the means to express what they think in the register being asked for, what the glossary calls code-switching;
hierarchical distance — the person has the means, in any of the three languages, and considers that it is not their place to say it;
the person — the disagreement is about the substance, and would be exactly the same in a monolingual team.

All three produce the same silence. They do not call for the same response, and treating the second as a language problem guarantees it is never resolved: you will translate documents for two years while nobody speaks up any more than before.

Individual coaching is sometimes the right place to tell the three apart, when the manager is themselves part of the problem.

The test is easy to run. Ask the same question one to one, in the person’s language of comfort. If the objection comes out, it was available: language was not the obstacle. If it still does not come out, the subject is elsewhere.

Managing in three languages: what actually changes, and what has nothing to do with it