As a Vietnamese tech lead working in an international environment, few things are more stressful than having a difficult conversation in English. You know exactly what you want to say in Vietnamese, but the words come out wrong — too blunt, too vague, or just awkward.
This guide covers three high-stakes scenarios every tech lead faces: pushing back on unrealistic deadlines, addressing underperformance in 1-on-1s, and escalating blockers to management.
1. Pushing Back on Unrealistic Deadlines
This is perhaps the most common difficult conversation. A PM or stakeholder wants something delivered “by Friday” and you know it is simply not possible.
Vietnamese engineers often default to two extremes: silent acceptance (“okay, we try”) or blunt refusal (“impossible”). Neither builds trust. The professional approach is to acknowledge, explain, and offer alternatives.
Key Phrases
| Situation | Phrase |
|---|---|
| Acknowledge the request | ”I understand this is a priority for you.” |
| Express concern without blame | ”I want to make sure we deliver quality, not just speed.” |
| State the constraint | ”Given our current sprint commitments, committing to Friday would put us at risk.” |
| Offer an alternative | ”What if we scope it down and deliver the core feature by Friday, with the full version next week?” |
| Ask for a trade-off decision | ”Something has to give — scope, timeline, or quality. What matters most to the business right now?” |
Example Dialogue
PM (Sarah): “We need the payment integration done by Friday. The sales team has a demo on Monday.”
You: “I hear you — a Monday demo is a real deadline. I want to help make that work. Right now, Friday is very tight because we’re mid-sprint and the integration has a third-party API dependency we haven’t fully tested yet. If we rush it, we risk showing a broken demo, which would be worse than a delay.”
Sarah: “What can we do?”
You: “Here’s my proposal: we do a ‘happy path’ only version — payment succeeds, confirmation shows. No edge cases, no error handling. That’s deliverable by Friday. We document what’s not included so the sales team knows what not to click. Does that work?”
Notice the structure: empathy → concern → reason → concrete alternative. This keeps the conversation collaborative, not confrontational.
2. Addressing Underperformance in a 1-on-1
This is the conversation most tech leads avoid the longest. Telling a team member their work is not good enough feels uncomfortable, especially for Vietnamese professionals who value harmony (sự hòa hợp).
But avoiding it is worse — it’s unfair to the person who doesn’t know they need to improve, and it’s unfair to the rest of the team.
Key Phrases
| Situation | Phrase |
|---|---|
| Open without accusation | ”I want to talk about something I’ve been observing, and I’d love your perspective on it.” |
| State the behavior, not the person | ”Over the last two sprints, the tickets you’ve taken have frequently been reopened by QA.” |
| Invite their view | ”What’s your experience been? What do you think has been happening?” |
| Express the impact | ”This is creating extra work for the QA team and sometimes blocking the release.” |
| Set a clear expectation | ”Going forward, I’d like you to run through the acceptance criteria checklist before marking anything as done.” |
| Offer support | ”I want to help you succeed here — what support do you need from me?” |
Example Dialogue
You: “Hey Minh, thanks for making time. I want to talk about something I’ve noticed and get your take on it. I’ve seen several of your tickets come back from QA over the past couple of sprints. I want to understand what’s happening from your side.”
Minh: “Yeah, I know. I think I was moving too fast.”
You: “That makes sense, and I appreciate you saying that. The velocity pressure in this sprint has been real. Here’s my concern though: when tickets bounce back, it blocks the QA team and sometimes pushes our release date. So I need us to find a solution.”
Minh: “What do you suggest?”
You: “Before you move a ticket to ‘Ready for QA’, run through the acceptance criteria out loud — literally read each one and check it yourself. It adds 10 minutes but saves everyone hours. Can you commit to that?”
Common Mistakes Vietnamese Speakers Make
- Being too indirect — saying “Maybe the quality could be improved” instead of “The quality needs to improve.” This creates confusion about whether it is feedback or just a suggestion.
- Mixing languages — switching to Vietnamese mid-sentence if the team member also speaks Vietnamese. Keep the professional context in English so it is documented clearly.
- Ending without a clear action — the conversation must end with a specific, measurable next step.
3. Escalating Blockers to Management
You have tried to resolve something at your level and you cannot. Maybe it is a dependency on another team, a resource constraint, or a risk that leadership needs to know about. Escalating is not “complaining” — it is part of your job as a tech lead.
Key Phrases
| Situation | Phrase |
|---|---|
| Frame it as a risk, not a complaint | ”I want to flag a risk that I think needs your attention.” |
| Show what you’ve already tried | ”We’ve tried [X] and [Y], but we’re still blocked on [Z].” |
| Be specific about the impact | ”If this isn’t resolved by [date], we’re at risk of missing [milestone].” |
| Ask for a specific action | ”I need either a decision on [X] or an introduction to [person] so we can unblock this.” |
Example Escalation (written format — Slack or email)
Hi David,
I want to flag a blocker on the payments project that needs your visibility.
The issue: We’re waiting on the security team to approve our PCI compliance documentation. I’ve followed up with James twice this week but haven’t received a response. Without their sign-off, we cannot move to UAT, which is scheduled for April 1.
What I’ve tried: Direct messages, a meeting request, and a message to the shared security channel.
What I need from you: Either an introduction to someone else on the security team who can expedite the review, or a decision on whether we can proceed to UAT conditionally while the review is pending.
Happy to discuss on a call if easier.
Short, factual, respectful — and with a clear ask at the end.
Quick Reference: Softening Language That Still Gets the Point Across
Vietnamese speakers sometimes avoid softening phrases, thinking they sound weak. In English professional culture, softening language actually makes you sound more professional and trustworthy.
- Instead of “That’s wrong” → “I see it differently — can I share my perspective?”
- Instead of “We can’t do that” → “That’s going to be challenging given [constraint]. What if we tried [alternative]?”
- Instead of “You didn’t do this” → “I noticed [behavior] — can you help me understand what happened?”
- Instead of “I don’t know” → “Let me look into that and get back to you by [time].”
Practice This Week
Pick one of these scenarios and role-play it before your next real conversation. The goal is not perfection — it is enough fluency that you can think about the message, not the words.
Difficult conversations in English get easier with repetition. And the ability to have them well is what separates a good tech lead from a great one.