Feedback across a language barrier can fail in two opposite ways. A manager may become so indirect that the employee misses the required change. Or the manager may simplify the message until it sounds abrupt and disrespectful.
Clarity does not require harshness. Use a structure that makes the evidence, impact, expectation, and next step explicit.
Prepare the message before the meeting
Write down four elements:
- Observation: What happened, without interpreting motive?
- Impact: Why does it matter?
- Expectation: What needs to happen differently?
- Confirmation: How will both people verify understanding?
Example:
“The last two customer updates did not include the revised delivery date. Customers then called support for clarification. Starting with today’s update, include the current date and label it as confirmed or estimated. Before we finish, I would like us to review one example together.”
This is easier to understand than “Your communication needs improvement.”
Use direct language about requirements
Polite English often uses softened requests, but excessive softening can hide the standard.
Unclear:
“It might be good to be a little more careful with the dates.”
Clear:
“Please verify the date against the schedule before sending the update.”
If something is optional, say so. If it is required, do not disguise it as a suggestion.
Understanding is only the first step.
Lyra Practice helps you retrieve and use high-value workplace expressions in realistic situations until they feel natural.
Start a practice session →Separate language from performance
If the work problem is missing information, discuss the missing information. Do not turn the conversation into a general judgment about English.
You can address a material language issue specifically:
“When you said the delivery was guaranteed, the customer understood that the date could not change. In this situation, use ‘current estimate’ until operations confirms the date.”
That feedback connects wording to consequence.
Check understanding without asking “Do you understand?”
Many employees will answer yes to that question even when part of the message remains unclear.
Use a work-focused check:
- “What will you include in the next update?”
- “Which date can be described as confirmed?”
- “If the supplier has not replied, what will you tell the customer?”
- “What support do you need from me?”
The purpose is mutual accuracy, not testing the employee publicly.
Allow time for response
Silence after feedback may mean the employee is processing the message, choosing careful language, or deciding whether it is safe to disagree. Do not fill every pause.
Offer a written follow-up for complex expectations. Writing does not replace the conversation; it gives both people a stable reference.
Avoid idioms when the stakes are high
Phrases such as “drop the ball,” “step up,” or “get your act together” may be familiar to some employees and opaque or insulting to others. Use literal language for the core requirement.
You can still teach workplace expressions deliberately. Do not make understanding an idiom a condition for understanding a performance expectation.
Invite relevant disagreement
A clear feedback conversation leaves room for missing context.
“That is what I observed. Is there information I may be missing?”
This does not weaken the standard. It prevents the manager from treating an incomplete account as settled fact.
Follow up on one observable change
Do not end with “communicate better.” Set one action and a review point.
“For the next three updates, include the confirmed date, remaining uncertainty, and next checkpoint. We will review them together on Friday.”
For broader diagnosis, read Language Barriers at Work: What Business Owners Can Actually Fix. Managers can practice related vocabulary through the feedback and performance assessment.
Frequently Asked Questions
Should feedback be simplified for a non-native English speaker?
Make the structure and wording clear, but do not remove necessary detail or lower the performance standard. Avoid unnecessary idioms and long, nested explanations.
Is it appropriate to correct grammar during feedback?
Only when the language caused a meaningful misunderstanding or relates directly to the work expectation. Handle lower-priority correction separately.
How can a manager confirm understanding respectfully?
Ask the employee to describe the next action or work through an example. Frame this as mutual confirmation, not a language test.