Why your company switched to English (and what it quietly expects of you)

The short answer

Companies adopt English as their official language for four fairly boring reasons: a merger left them with two head offices, hiring stopped being local, the accounts and contracts need one governing language, and their customers or regulators already work in English. None of those reasons is a judgement about your English.

But the policy has a side effect that no announcement mentions. It changes who gets heard. Once the meeting runs in your second language, the person who speaks first is not always the person who knows most, and over a few quarters that difference becomes a reputation. That is a problem of producing language in real time, long before it is a certificate problem, and almost nobody treats it as one.

The announcement, and the part it leaves out

The email is always similar. From the start of next quarter, meetings, documentation and internal systems will be in English. There are reasons: collaboration, alignment, mobility, one version of the truth. There is usually an offer of language training, and a reassurance that nobody is expected to be perfect.

What the announcement does not say is which parts of your job just moved into a second language. Not the formal parts. Those are fine: you can prepare a presentation, and you will. It is the informal layer that shifts, and the informal layer is where influence lives. The two minutes before the call starts. The corridor conversation where a decision gets pre-agreed. The quick objection in a meeting that changes the direction of a project. The joke that makes you a person rather than a name on a screen.

The best-documented example of a company doing this deliberately is public. Rakuten's chief executive, Hiroshi Mikitani, announced an English mandate covering the company's Japanese workforce, most of whom did not work in English at the time. The Harvard Business School professor Tsedal Neeley followed the company for years afterwards and published the account as The Language of Global Success (Princeton University Press, 2017). The finding worth carrying out of it is not that the mandate succeeded or failed. It is that a language policy is never only about language. It rearranges status inside the organisation, and it does so whether or not anyone intended that.

The four drivers, honestly

A merger or an acquisition. Two organisations with two head-office languages now share one board and one set of processes. English is the neutral choice, and neutrality is the point. Choosing either side's national language would be a political act on day one of an integration that already has enough of those.

Hiring stopped being local. Once you recruit engineers in five countries, requiring one national language shrinks the candidate pool in every one of them. Companies that compete for scarce specialists give that requirement up quickly, and English is what remains.

One reporting, audit and legal language. Consolidated accounts, audit trails, board minutes, supplier contracts, internal policies. Maintaining two authoritative versions of anything is expensive, and the moment they diverge somebody has to answer which version governs. One language removes an entire category of risk.

Customers and regulators. Technical documentation, filings, tenders, support. If the people you sell to and the bodies you report to already work in English, running your internal life in another language means translating at every boundary.

It is worth stating plainly that none of these is about anyone's ability, because the announcement often lands as though it were. Companies do this for structural reasons, then discover the human ones afterwards.

What actually changes day to day

Meetings become faster than your composition speed. In your first language you think and speak at once. In your second you often compose, then speak. A meeting rewards the first mode. By the time your sentence is ready, the topic has moved.

Writing becomes the visible record. Tickets, review comments, memos, incident notes. This is the part where a careful non-native writer often does better than a fast native one, because writing allows editing. Many people underuse it.

Your work gets described in English by someone else. In calibration and promotion discussions, a manager argues your case from evidence. The evidence is mostly made of moments where you were visible.

The informal layer gets quieter. This is the change people feel most and mention least. It is also the one that no course addresses, because it cannot be scheduled.

Fluent on paper, silent in the room

Here is the pattern I have watched in myself and in colleagues. Someone holds a C1 certificate. They read the documentation faster than most of the room. In the meeting, a claim goes past that they know is wrong. They begin assembling the sentence: the polite opener, the correct tense, the technical term. Somewhere around the third word of that internal draft, the conversation moves on.

Nothing about that is a comprehension failure. It is a production failure under time pressure, and from the outside it looks like something else entirely. It looks like disengagement, or a lack of conviction, or not being ready for the client-facing role. Nobody in the room calls it a language problem, so it never gets treated as one. The person is simply less often asked.

Three moments do most of the damage, and none of them appears on any certificate:

• Interrupting to correct a factual error, quickly, without sounding aggressive.
• Disagreeing with someone more senior in a way that leaves the relationship intact.
• Answering "why not the other approach?" live, with reasoning, in under a minute.

Each is a language task with a social edge. Each is rehearsable. Almost nobody rehearses them, because the training on offer is aimed elsewhere.

Why the course they offered probably will not close it

Two reasons, and neither is a criticism of teachers.

The first is scope. Generic Business English teaches the average of every job, which is nobody's job. The controller does not need to circle back; she needs to defend a variance to a board that reads numbers faster than sentences. The supply-chain lead needs to say no to a supplier and keep the supplier. The engineer needs to push back on a design decision without implying that the person who made it is careless. Same language, three different worlds. A syllabus that serves all of them serves none of them particularly.

The second is format. A weekly ninety-minute class is comfortable and mostly receptive: listening, reading, some controlled speaking with a supportive teacher. The skill that decides the three moments above is speaking while being challenged by someone who is not being supportive. If a programme never puts you under that pressure, it cannot build the reflex, however good the material is. If you are the person choosing the training rather than receiving it, the trade-offs between the formats are worth reading properly, and I have set them out in how to choose English training for a multinational team.

What actually closes it

Practise your own function, not "business". The vocabulary you need is the vocabulary of the documents you produce and the objections you field. Everything else is decoration.

Practise under interruption. Say a claim, get interrupted halfway, keep the thread. The skill is holding an argument together while someone is talking over it, and it only improves by doing it.

Rehearse the three moments literally. Write down the five questions you dread in your own job. Answer each aloud in under a minute. Then answer them again with an interruption at the thirty-second mark.

Use writing deliberately. The memo is the one place where you control the clock. A short, well-organised written argument travels further in an English-language organisation than most people expect, and it builds the record that gets read out in the calibration meeting.

Choose rhythm over intensity. Fifteen minutes on five days beats ninety minutes on one, because the second one gets cancelled in a busy quarter and the first one does not.

Where nicheAce fits

I built nicheAce: language because I was on the wrong side of exactly this. Certified, quick on paper, and quiet in the room where it counted. The app opens with a conversation about your job, your field and where you get stuck, and builds a fifteen-week journey out of that answer: five exercises a day of about fifteen minutes each, five days a week, ending in role-play with a character who has a goal of their own and does not let you finish comfortably. It is deliberately not a general course. If your company has just switched to English and the gap you feel is the one described above, the language page shows what a journey actually contains.

It is honest about the cost: roughly seventy-five minutes a day, five days a week, for fifteen weeks. Hands-free Audio Mode is live in English, French, German, Spanish and Italian, and the app runs on Android in the EU today. If you want something lighter, that is a reasonable choice, but expect it to move the needle less.

The policy is not going away

Language mandates rarely get reversed. Once the accounts, the contracts and the hiring pipeline are in one language, going back costs more than going forward.

So the useful question is not whether the policy was fair. It is which three moments in your particular job are currently being decided by how quickly you can produce a sentence, and what it would take to make those three automatic. That list is short, specific to you, and nothing like the syllabus of a general course.