How to Give Feedback to Non-Native English Speakers on Your Team

You have a team member whose work is strong, apart from one recurring issue. You know you should say something, but you worry about being too harsh or whether your message will be understood. So you soften your words, and the issue quietly returns next week. Learning how to give feedback to non-native English speakers effectively is essential for modern leaders managing a multicultural team. When approached with clarity and respect, communication in international teams becomes a team strength.

Why feedback goes wrong in international teams

Feedback often fails because small verbal habits change the meaning of a message entirely. When managing a multicultural team, understanding these communication gaps helps prevent misunderstandings.

Soft feedback sounds like a suggestion

Phrases like "maybe", "you might want to", and "it would be nice if" can sound optional, especially to someone taking words literally or coming from a direct culture. Colleagues navigating Corporate English Jargon: 25 Phrases Western Colleagues Use (and What They Mean) often struggle to decode whether a phrase is a polite suggestion or an urgent requirement.

Avoiding feedback altogether

Some managers delay conversations to avoid causing offence. Unfortunately, waiting weeks or months allows small habits to entrench themselves until the problem becomes a major performance issue that arrives as a surprise.

Asking "Does that make sense?"

Many leaders close a conversation by asking if everything is clear. Professionals will often say "yes" instantly to be polite, to avoid slowing down the meeting, or to save face, even when key details remain unclear.

Signs your feedback to non-native English speakers is not landing

When communication misses the mark, certain patterns tend to repeat across your daily operations:

• The exact same issue keeps appearing in project deliverables week after week. The initial conversation did not transfer clear expectations.
• The team member always smiles, nods, and agrees during one-to-ones, but nothing changes in practice. Agreement is used as politeness rather than understanding.
• The colleague expresses genuine surprise and upset when a recurring issue appears as a negative point in a formal review. They believed their work met all required standards.
• You feel frustrated because you are certain you already raised the point, while the colleague genuinely believes they were never told. Soft phrasing obscured the core instruction.

A real story: the feedback that was too kind to be clear

A team lead at a software company worked with an international team that included several non-native English speakers. One developer's work was strong, but his pull requests often had missing tests. The team lead did not want to embarrass him or sound unfair to a colleague working in a second language. So he gave soft comments such as, "Great work. Maybe have another look at the tests when you have time." The developer took this as a suggestion, not a request, and the problem continued for months. In the end, it came up in a formal review, and the developer was surprised and upset that nobody had told him earlier.

When they talked it through, Steve saw that the team lead was softening his feedback because he cared about the developer, but the softness hid the message. The feedback was kind, but it was not clear, and the developer never knew it was a real expectation. They practised a simple structure: say what you saw, say the impact, say clearly what needs to change, and agree on the next step. They also practised asking the person to say in their own words what they would do next, instead of asking "Does that make sense?".

In the next one-to-one, the team lead used the structure. The developer said he was relieved to hear it plainly, and added that he preferred direct feedback. The missing tests stopped appearing in his pull requests, and the team lead started using the same structure with the whole team. Steve, AptSpeak's coach, puts it this way:

"Managers often think soft feedback is the kind option. But feedback that nobody understands isn't kind, it's just delayed. Clear feedback, given early and with respect, is one of the best things you can give a team member, whatever language they speak at home."

How to give clear feedback to non-native English speakers

To build trust and clarity, structure your conversations around simple, actionable steps that leave no room for guesswork.

1. Give feedback early and in private

Do not wait for the formal review cycle or bring up performance issues in group meetings. Schedule a quiet one-to-one where both of you can focus entirely on the topic.

2. Say what you saw

Describe the objective behaviour rather than offering a vague opinion. For example, say, "In the last three pull requests, there were no tests included."

3. Say the impact

Explain why the behaviour matters to the wider team or project outcomes, such as noting that "This slows down our review cycle and risks bugs in production."

4. Say clearly what needs to change

Be explicit about your expectations without being aggressive. State, "From now on, I need every pull request to include tests." Phrases like "I need" or "I'd like you to" provide absolute clarity while remaining respectful.

5. Check understanding properly and agree the next step

Instead of asking if things make sense, ask the person to articulate their action plan in their own words, such as, "Can you tell me how you'll approach this next week?" Exploring Active Listening in English: How to Show You Really Understood helps ensure both sides are aligned.

Make your language easy for everyone to follow

Clear communication benefits everyone on your team, regardless of their background. Implementing these daily habits removes unnecessary linguistic hurdles:

• Avoid idioms and sports or war metaphors. Phrases such as "drop the ball" (failing at a task) or "low-hanging fruit" (easy tasks) confuse non-native speakers.
• Use one core idea per sentence. This keeps your spoken instructions digestible and easy to process during fast conversations.
• Send short written notes via chat after a verbal conversation. Following up in writing reinforces key action items clearly.
• Speak at a steady, measured pace and allow natural pauses. Pausing gives listeners sufficient time to absorb information without feeling rushed.
• Avoid sarcasm and understatement. Saying "not bad" when you mean "great work" creates unnecessary ambiguity.

These habits make feedback clearer for everyone on the team, including native speakers. Strong communication practices align closely with insights shared in Why Technical Skill Isn't Enough: The Communication Gap Costing Outsourcing Firms Their Clients.

Useful phrases for managers

Having the right phrasing ready helps you maintain a calm, professional tone during delicate conversations.

Opening the conversation

• "I'd like to give you some feedback on one specific thing."
• "Do you have ten minutes to talk about the last release?"

Being clear and kind

• "Your work on the design was strong. The part I need you to improve is the testing."
• "This is important, so I want to be direct."

Checking understanding and inviting two-way feedback

• "What's your view of this?"
• "What would help you to do this?"
• "Please tell me if my feedback is ever unclear."

A team that gives feedback in both directions builds trust faster.

Frequently asked questions

Should I give feedback differently to non-native speakers?

The aim is to give everyone clear and specific feedback, not to treat non-native speakers as different, and to ask individuals how they prefer to receive it. Tailoring your approach to individual working styles creates a fairer environment for all team members.

Is direct feedback rude?

Direct and respectful are not opposites, and maintaining professionalism depends entirely on your tone and intent. When managing international projects, mastering techniques outlined in How to Speak Up in Meetings When Native Speakers Talk Fast (and Keep Interrupting) helps bridge cultural divides.

What if the person always says "yes" but nothing changes?

When agreement does not lead to action, it usually means the initial instructions lacked specific behavioural outcomes. Asking the person to summarise the agreed steps in their own words resolves this disconnect instantly.

When your whole team needs a shared way to communicate

Individual managerial habits help, but a shared team approach often works better. When everyone adopts clear feedback practices, shared meeting habits, and confident communication with clients, collaboration flows smoothly across borders. Establishing these norms prevents isolated misunderstandings from turning into recurring team friction. AptSpeak offers communication training for corporate teams looking to align their daily workflows and professional communication standards.

Support your team with an AptSpeak coach

AptSpeak offers communication training for international professionals and for corporate teams. Coach Steve, an interview and communication coach from Arizona, USA, brings 13 years of experience teaching and mentoring professionals, including 8 years at international schools in China, Cambodia, and Vietnam. Having coached hundreds of professionals across diverse cultures, he helps teams navigate international business culture, executive communication, client calls, and meetings. His focus is building confidence through clear, constructive feedback. Readers can start with a trial session.