Insights

The Two-Language Tax

Many Canadian businesses serve clients in one official language and run their operations in the other. That mismatch has a real cost in errors, rework and turnover, and it never shows up on the P&L.

---

Walk into a lot of Manitoba businesses and you find the same quiet split. The counter serves customers in French. The back of the house runs in English.

Nobody decided this. It happened one hire and one document at a time. The first SOP got written in whatever language the person writing it thought in. The safety board came from a supplier who only sent English. A manager built the scheduling sheet, and it stuck. Ten years later the company sells in one language and operates in another, and the gap between those two has a price. I have started calling it the two-language tax, because it behaves like a tax: small, constant, taken off the top before anyone counts, and paid by the people who can least afford it.

Where the tax gets collected

It shows up first in documentation. The standard operating procedure, the one that tells a new hire how to close the till or lock out a machine, is written in the language the owner or the office thinks in. Half the floor reads it slowly, mouthing the harder words, checking the parts they are least sure of the least. They do not ask. Asking in a second language, in front of the team, about a document everyone else seems to have understood, costs a kind of pride most people will pay a lot to protect. So they guess. A procedure that gets guessed at is not a standard. It is a suggestion.

It shows up in training. You bring the team in for a half day on a new process, a new machine, a new compliance rule. The session runs in one language. For part of the room it lands clean. For the rest it lands at maybe seventy percent, and the missing thirty is exactly the part that was hard enough to need training in the first place. Everyone nods, because nodding is free and questions are expensive. You leave thinking the team is trained. You have trained part of the team, and you will find out which part the first time something goes wrong.

It shows up at the handoff, which is where an operations person spends half their life. Day shift writes the shift note. Night shift reads it. If those two crews do not comfortably share a first language, the note is written carefully by one and skimmed nervously by the other, and the thing that did not get written down clearly is the thing that becomes tomorrow's problem. The handoff is already the largest single source of delay and error in most operations. Put a language seam through the middle of it and you have widened the crack.

And it shows up at the customer counter in reverse. A francophone customer in Saint-Boniface or Shediac asks a question the front-line staffer can answer, but the answer depends on a policy that only exists in English in the back. Now the staffer is translating on the fly, under time pressure, in front of the customer, and translating a warranty term or a dosage is exactly the moment you least want someone improvising.

Why it never shows up on the P&L

Here is the part that makes this tax so durable. It has no line. There is no account called "language friction." The cost hides inside numbers you already have and blame on other things.

The reorder that had to be redone because the spec was misread becomes a rework number, and you blame the supplier. The near miss on the floor because someone did not fully take in the English lockout sheet becomes a safety statistic, and you blame carelessness. The newcomer who never quite got up to speed and left inside a year becomes a turnover number, and you blame the labour market. The slow onboarding, the manager who has to re-explain the same thing four times, the customer who did not come back because the answer felt uncertain, none of these arrives labelled. They arrive disguised as ordinary operational noise, and every one of them is partly the two-language tax being collected.

I spent years as a tax auditor before I did this work. The thing you learn auditing is that the costs that hurt a business most are almost never the ones with their own line. They are the ones spread thin across a dozen other lines, invisible in any single place, ruinous in aggregate. This is one of those.

What it actually costs

Take the newcomer worker, because Manitoba and New Brunswick are both betting hard on immigration to staff their businesses. You recruited someone skilled who works in French, or in English as a strong second language. Then you handed them an operating system written entirely in the other one. Their ramp to full productivity, which should take weeks, takes months, because every procedure is a translation exercise before it is a work instruction. They make more early errors, not because they are less capable, but because they are decoding and doing at the same time. Some of them leave, and you record it as turnover and start the hiring cost over. You paid to recruit them, to train them badly, and to replace them, over a language mismatch you never named.

Take quality. A misread instruction does not announce itself as a language problem. It announces itself as a defect, a return, a redo, a customer who is polite about it once and gone the second time. Lean people have a word for the work you do twice: rework, one of the eight classic wastes. When a chunk of your rework traces back to instructions half the floor reads at reduced comprehension, you do not have a discipline problem or a talent problem. You have a documentation-language problem wearing a quality problem's clothes.

The fix is not translation

The obvious answer is to translate everything, and that is not quite it. A pile of documents run through a translation tool gives you two piles nobody trusts, drifting apart every time one gets updated and the other does not. Translation is a task. What the business actually needs is for its operations to be built and run in the language its team works in, from the start, as a design choice rather than a cleanup project.

That means the SOP is written once, in the working language of the people who use it, and the customer-facing version is derived from it rather than the reverse. It means training is delivered in the language the room actually thinks in, so the hard thirty percent lands too. It means the shift note, the KPI board, the standard work, the safety instruction all live in the language of the floor, and the front counter is the surface you localize, because that is the surface the customer sees. You match the language to where the work happens, not to where the owner happens to think.

This is ordinary operations work. It is standardizing your standard work, closing the gap between how a job is documented and how it is done, taking friction out of the handoff. The only difference is that language is treated as one of the variables instead of an accident. A genuinely bilingual operator does this without a translation vendor in the loop, because they can write the SOP in French, teach it in French, check that it landed in French, and build the English customer-facing layer on top, all in the same head, the same week. That is not a nicety. In a bilingual province it is an operational advantage most competitors are leaving on the table.

Where to start

You do not need a program. Pick the three documents where a misread costs you the most: the safety-critical one, the quality-critical one, and the one every new hire relies on in week one. Find out, honestly, what language the people who use those three actually work in. If there is a gap between that and the language the documents are written in, you have found where your tax is highest, and you have found where to start.

This is the work I do as a fractional operations lead for owner-run businesses in Manitoba, in French and English both, and the training I deliver is built the same way. If any of this sounds like your floor, the plainest next step is a short conversation. You can read how the fractional operations and training work fit together, book a call at cal.com/provenance/30min, or just get in touch and tell me where the friction is.