Why Feedback Gets Lost in Translation at Work

How to Give Feedback That Actually Lands in a Multilingual Team

When companies build multilingual teams, they almost always check for one thing: does everyone speak the working language well enough. What they don’t check is whether everyone expects feedback delivered the same way. Two people can use the exact same words, in the exact same language, and walk away from the same conversation having heard two different things.

That gap isn’t about politeness, and it isn’t about one person being right and the other wrong. It comes down to an unwritten rulebook for how directly a concern should be voiced out loud, absorbed so early and so thoroughly that most people never notice they’re following one, right up until they collide with someone using a different set of rules entirely.

That collision happens constantly on multilingual and multicultural teams, and it hits nowhere harder than in feedback. One person delivers a concern gently, expecting it to register as serious. The other hears gentle phrasing and files it away as a passing comment rather than something requiring action. The words can be in the same shared working language. The meaning doesn’t always survive the trip between them.

Why Feedback Is One of the Hardest Things to Translate

Most workplace communication has some margin for error. A slightly awkward email still gets the point across. Feedback has much less room, because its entire function depends on the listener correctly reading not just what was said, but how seriously it was meant. That’s a lot to ask of two people operating with different defaults for directness, even when both are speaking fluently in a shared working language.

I’ve written before about the communication pitfalls multilingual teams run into, and feedback sits right at the sharpest edge of that problem, because unlike most workplace conversation, feedback is meant to change behaviour. If the message doesn’t land as intended, nothing changes, and both people can walk away with completely different impressions of what just happened.

Directness Isn’t Universal

Communication researchers have mapped this pattern for decades under the labels high-context and low-context communication: shorthand for how much meaning a listener is expected to read into tone versus have it spelled out plainly in words. In her research on cross-cultural business communication, Erin Meyer found these two dials don’t always move together: a culture can lean high-context in everyday conversation while still being unusually direct specifically when it comes to negative feedback. That’s part of why “read the culture correctly” is a less reliable strategy than “check the feedback actually landed,” no matter which culture either person is from.

The trouble starts when two people from different defaults assume the other shares theirs. A direct style can land as blunt or even hostile to someone expecting more cushioning. A softened style can land as vague or, worse, as not-actually-important to someone expecting plain language. Both interpretations are reasonable given each person’s background. Neither person is wrong. The feedback simply doesn’t survive the handoff.

How Misread Feedback Quietly Erodes Trust and Performance

The cost of this isn’t always visible immediately, which is part of what makes it dangerous. An employee who consistently misses softened feedback doesn’t usually realise they’re missing anything, so the same issue resurfaces, and a manager can start reading that repetition as carelessness or resistance rather than a communication mismatch. Meanwhile, an employee on the receiving end of blunt, direct feedback they weren’t braced for can quietly disengage, reading bluntness as personal criticism rather than professional input.

Neither person necessarily says anything out loud. That’s often the most costly part. Feedback misfires tend to show up not as conflict, but as a slow, quiet erosion of trust that’s hard to trace back to its source, because on paper, the feedback conversation happened. It’s easy to miss what happened between the lines.

Over enough cycles, this pattern can shape how an entire team is perceived, unfairly, by leadership who only ever see the outcome and not the communication mismatch that produced it. A team that looks inconsistent or slow to improve might simply be a team where feedback keeps getting lost in the handoff between two different sets of assumptions about how directly things need to be said.

What Managers Can Do Differently

Building a habit of checking that feedback has actually landed matters more than picking one universal style and asking everyone to adapt to it, or assuming the words alone did the job. One simple, underused practice puts that into action: after giving feedback, ask the person to reflect it back in their own words. Not as a test, but as a genuine check: “just so I know we’re on the same page, what’s your read on what I just said?” It takes thirty extra seconds and closes a gap that would otherwise stay invisible until the same issue resurfaces weeks later.

It also helps to separate the seriousness of a message from the softness of its delivery. A manager doesn’t have to abandon a gentler communication style. They can pair it with a direct summary at the end: “to be clear, this needs to change by next sprint,” said plainly, even within an otherwise warm conversation. That combination tends to travel well across different defaults, because it gives both the emotional cushioning some people expect and the clarity others need to register that action is required.

I explored a related angle in the hidden cost of lingua franca culture at work: a shared working language solves less than it appears to, because fluency in the words doesn’t guarantee fluency in each other’s communication norms.

A Simple Framework Worth Trying

For managers who want something more concrete than “check it landed,” a three-part structure tends to hold up well across different communication defaults. Start with the observation, stated plainly and without hedging: what specifically happened, described as fact rather than interpretation. Follow with the impact, explained clearly enough that the seriousness is unmistakable, even if the tone around it stays warm. Close with an explicit check, inviting the other person to reflect back what they’ve understood, rather than simply asking “does that make sense,” which most people will answer yes to regardless of whether it actually does.

If this structure feels familiar, it’s a close cousin of SBI (Situation-Behaviour-Impact), a feedback model long used in management training. The multilingual-team twist is making that third step, the check, deliberate and explicit rather than assumed, since it’s exactly the step that gets skipped when two people don’t share the same default for directness.

This structure works because it separates three things that often get blurred together in feedback conversations: the facts, the stakes, and the confirmation that the message was received as intended. A manager can still deliver all three warmly, with empathy, with care for how it lands emotionally. What changes is that none of the three gets lost in translation, because each one is handled deliberately rather than folded into a single, softened paragraph that different listeners will parse completely differently.

It’s worth adding that this isn’t only a challenge for managers speaking a second language themselves. Native speakers giving feedback to colleagues from different communication backgrounds run into exactly the same mismatch, because the issue comes down to differing assumptions about how directly meaning should be stated, not language proficiency. Those assumptions run deep, often below the level either person consciously notices until a misunderstanding forces it into view.

Making This Work Across the Whole Team, Not Just One Conversation

Individual habits help, but the biggest shifts tend to happen when an entire team develops a shared vocabulary for talking about communication style itself. Teams that can openly discuss “I tend to be pretty direct, tell me if that ever lands wrong” or “I sometimes soften things more than I mean to, push me for the plain version if you need it” build a kind of shared map that makes future misunderstandings far less likely.

This doesn’t require a lengthy workshop to establish, though a facilitated conversation early in a team’s life, or after a period of friction, often accelerates it considerably. What it requires most is permission: an explicit acknowledgement from leadership that different communication defaults exist, that neither is wrong, and that naming the difference out loud is a sign of a healthy team, not an awkward admission of a problem.

Building a Feedback Culture That Works Across Languages

None of this requires a complex framework. It requires managers who treat “did that land the way I meant it” as a genuine question worth asking out loud, rather than one that is taken for granted in every conversation. Teams that build this habit tend to catch communication mismatches early, before they turn into resentment or repeated mistakes that look, from the outside, like a performance problem rather than what they actually are.

None of this is really about fixing a flaw in either communication style. Both directness and diplomacy serve real purposes, and teams that include a mix of both, handled with awareness, tend to be more resilient than teams built entirely around one default. The goal is mutual legibility, not uniformity: making sure that when something important is said, it’s actually heard the way it was meant.

If you’re navigating questions, challenges, or goals around multilingualism, whether that’s in your hiring, your team’s day-to-day communication, or your organisation’s wider culture, workshops for teams and leadership are available to help build exactly this kind of habit.

You can book a free 30-minute introductory call or find more information about my work and current offers on my website. I also share ongoing insights and resources on Instagram, Facebook, and LinkedIn. I’d love to have you there!

FAQs