Managing people is hard. Managing people in your second language — where nuance is harder to detect, where you may miss the emotional register of a conversation, where the words you reach for under pressure may not be the right ones — is harder still.
The specific challenges for non-native English speakers who manage in English are not the same as the challenges of presenting or negotiating in English. Management is relational, continuous, and depends on the accumulation of trust over time. A single high-stakes presentation can be prepared. A management relationship cannot.
This post covers the core language demands of managing in English: giving direction, delivering feedback, handling conflict, and building the kind of trust that makes a team work.
Giving Direction That Gets the Right Result
The most common management communication failure is giving direction that seems clear to the manager and isn't clear to the team member. This problem is not unique to non-native English speakers, but it's amplified when the manager is working in a second language — because the natural impulse under uncertainty is to say less, not more.
Clear direction has four components:
- What needs to happen (the task)
- Why it matters (the context)
- By when (the deadline, including the precision needed — "end of week" and "Friday at 5pm" are different)
- What good looks like (the standard, so the person knows when they're done)
Most managers communicate 1 and 3 reliably. The two that are most often dropped — why and what good looks like — are the two that matter most for autonomous execution.
| Component | What gets missed | Better version |
|---|---|---|
| What | "Sort out the client situation." | "Call Chen's team today and agree a timeline for the delayed deliverable." |
| Why | Assumes the person understands the stakes | "This is important because they've escalated once and we can't afford a second escalation." |
| By when | "Soon" or "when you can" | "By end of Thursday — we need to report back on Friday morning." |
| What good looks like | Left undefined | "A confirmed date from their side, in writing. That's the finish line." |
The Language of Effective Feedback
Feedback in English professional contexts is generally expected to be direct, specific, and timely. This can feel at odds with cultural norms around maintaining face or preserving harmony — but in practice, feedback that is too indirect, too cushioned, or too delayed fails the person receiving it.
Ineffective feedback patterns:
- The "sandwich" (positive, negative, positive) — it dilutes the message and many people only hear the positives
- Vague feedback ("I think there's room to improve your presentation style")
- Delayed feedback ("I've been meaning to mention for a few months...")
- Qualified feedback that becomes praise ("I think this is mostly very good, you just might want to consider...")
What effective feedback looks like:
Specific: "In the client meeting on Tuesday, when the questions got harder, you deferred to me rather than answering. I want you to take those questions directly."
Behaviour-focused: "What I'm observing is X" rather than "You are X."
Actionable: The person should know exactly what to do differently.
Language that delivers this clearly:
- "I want to give you some direct feedback on [specific context]. Is now a good moment?"
- "Here's what I noticed: [specific observation]. The impact of that was [consequence]."
- "What I'd ask you to do differently is [specific behaviour]."
- "I'm telling you this because [reason it matters], not because [remove misinterpretation]."
The last line is valuable. "I'm telling you this because I think you can be running those client calls alone within three months, not because I think you performed badly" changes how the feedback is received.
Handling Underperformance
Managing underperformance is one of the hardest conversations in any management role, in any language. Non-native English speakers often avoid it longer than native speakers because the language required — directness without aggression, firmness without cruelty — is genuinely difficult to calibrate in a second language.
The framework is the same as feedback, but with escalation built in:
First conversation (early, specific, no ambiguity): "I want to talk about [specific issue]. This has happened [number of times] in the last [period], and I need it to change. Here's what I need to see instead."
Second conversation (if the issue continues): "We spoke about this two weeks ago. I said I needed [specific change]. The pattern has continued. I want to be direct with you: if this doesn't change by [date], we'll need to involve HR and think about whether this role is the right fit."
What to avoid:
- The conversation that sounds direct but is actually indirect: "I just want to flag that I've noticed some things that could potentially be improved..."
- Framing underperformance as a team problem when it's an individual one
- Giving an ultimatum without a specific date or measurable outcome
The rule: if you're having a performance conversation, the person should leave with no uncertainty about what is wrong, what is required, and what the consequences of non-improvement are.
Building Trust Across Languages and Cultures
A manager who leads a diverse team — where team members come from different language backgrounds — faces a specific trust challenge: each team member may have different assumptions about what a manager is supposed to do, how decisions are made, and what kind of communication signals respect.
The most common sources of trust erosion in diverse teams:
Inconsistency in visibility. If team members who communicate easily in English are more visible, more included, and more often in the room for key conversations, the team becomes stratified. The manager's job is to compensate for this actively.
Assumptions about understanding. "Does everyone understand?" is not a useful check. People who don't understand often say yes because saying no feels like an admission. Better: "What questions do people have?" or "Before we close this, I want to make sure the next steps are clear — [name], can you tell me what you're taking away from this?"
Feedback delivered only in private. In some management cultures, public recognition is important. In others, singling people out is uncomfortable. Know which applies to your team members, and calibrate accordingly.
Language for building trust over time:
- "What do you need from me to do this well?"
- "I want to make sure you're getting what you need from me as your manager. What's working, and what isn't?"
- "I should have [checked in earlier / given you more context / asked before deciding]. I'll do that differently next time."
The last one — acknowledging your own management errors specifically — is one of the most powerful trust-building moves available. It models the accountability you're asking of your team.
Managing Up in English
Managing a team in English often also means managing up — communicating with your own manager or the broader leadership of the organisation — in a way that builds confidence in your team's work.
The specific language demands: reporting progress without underselling, raising problems without triggering alarm, and advocating for your team without seeming self-promotional.
Progress updates that land well: "We're on track for [outcome] by [date]. The one thing I'm watching is [specific risk] — I've [mitigating action] and will know more by [date]."
Raising problems without alarm: "I want to flag something early rather than late. [Issue]. Here's my current thinking on how to handle it. I wanted your input before I proceed."
Advocating for your team: "The work my team did on [X] had a direct effect on [outcome]. I want to make sure that's visible, because it reflects well on them and I want them to know their work is recognised."
Frequently Asked Questions
I'm managing native English speakers who sometimes correct my English in front of the team. How do I handle this?
Address it directly and privately: "When you correct my language in front of the team, it undermines my position as your manager. I need you to raise those things with me privately." This is a management issue, not a language issue. Your authority as a manager does not depend on perfect English, and team members who challenge it by focusing on language are confusing the two.
How do I give negative feedback to someone who is significantly more senior or older than I am?
The same framework applies, but the framing leans more on impact and less on instruction: "The impact of what happened in that meeting was [X]. I want to be direct with you because I think this matters for how you're perceived." You're not telling them what to do; you're giving them information and trusting them to respond to it. This is the appropriate frame regardless of the power dynamic.
My team spans multiple time zones and we mostly communicate in writing. Does any of this apply?
All of it applies, but asynchronous communication is a different medium with different risks. The most common error in written management communication is a tone that reads as colder than it was intended. Proofread for warmth, not just accuracy. And never deliver negative feedback in writing if a call is possible — written feedback removes the human context that makes hard conversations navigable.
How do I handle a team member who simply doesn't respond well to direct feedback?
First, understand what "doesn't respond well" means. If it means they become defensive, that's a normal reaction and worth addressing directly: "I notice this conversation has become difficult. That's not what I'm trying to create. I'm giving you this feedback because I think you can improve, not because I'm criticising you." If it means the behaviour doesn't change despite multiple conversations, that's an underperformance issue and needs to be treated as one.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.