The 1-on-1 meeting is the most important conversation a tech lead has. Not the architecture review, not the sprint planning, not the incident postmortem — the 1-on-1.
It’s where you find out what’s actually happening with your team. It’s where trust is built or eroded over time. And it’s where the quality of your English — specifically your ability to ask real questions, give honest feedback, and handle uncomfortable silences — matters most.
For Vietnamese tech leads working in international teams, this conversation is particularly challenging. In Vietnamese culture, hierarchy shapes how direct feedback flows. Senior people advise; junior people listen. But in international tech teams, the expectation is different: 1-on-1s are dialogues, not debriefs.
Here’s the language for each part of that conversation.
Opening the 1-on-1 Right
Most 1-on-1s fail in the first 60 seconds because they’re opened with status updates. “How’s the project going?” signals that this is a status meeting — and you’ll get status, not truth.
Open with something that invites honesty:
“What’s on your mind this week? Not just work — anything.”
“What’s been the most frustrating part of the last two weeks? And what’s been the best?”
“Is there anything I’m doing — or not doing — that’s making your job harder?”
That last question takes courage to ask in English when it’s not your first language. Say it anyway. It signals that you’re safe to be honest with, which is the whole point of a 1-on-1.
Giving Feedback That Lands
Feedback in English has a structure. Without it, feedback either lands too soft (the message doesn’t get through) or too hard (the person gets defensive and stops listening).
The structure that works in international tech teams: specific behavior → observable impact → what you’d like to see.
Too vague:
“You need to communicate more.”
Better:
“In the last two sprints, I noticed you didn’t raise the authentication blocker until the end of the sprint, when it was already a delay risk. I’d like you to flag blockers earlier — even if they feel uncertain. I’d rather hear about a maybe-problem than miss a real one.”
Notice what the second version does:
- Names the specific thing (the authentication blocker)
- States the impact (delay risk)
- Asks for a behavior change, not a personality change
When giving positive feedback, be equally specific. “Good job this sprint” is forgettable. This isn’t:
“The way you handled the API integration last week — you spotted the rate limit issue before it hit production, documented it clearly, and flagged it to the team without making it a drama. That’s exactly the kind of proactive thinking I want more of.”
Specific positive feedback tells the person what to repeat. Vague praise doesn’t.
Asking Questions That Get Real Answers
The questions most tech leads ask in 1-on-1s are safe questions. They generate safe answers. If you want honest signal about what’s happening on your team, you need a different kind of question.
Safe question: “Is everything okay?” Real question: “On a scale of 1–10, how motivated are you right now? What would make it a point higher?”
Safe question: “Any issues with the team?” Real question: “If you could change one thing about how this team works, what would it be?”
Safe question: “Do you have enough to do?” Real question: “What’s one thing you wish you had more time to work on? What’s getting in the way?”
The pattern: replace yes/no questions with questions that require a concrete, specific answer. They’re harder to answer generically.
Handling Silence and Discomfort
In 1-on-1s, silence often means something is being processed, not that there’s nothing to say. In English conversations, there’s a cultural tendency to fill silence quickly. Resist this.
When you ask a real question and get silence:
“Take your time — there’s no rush.”
If someone seems like they want to say something but isn’t:
“It feels like there might be more there. You don’t have to share, but I’m listening if you want to.”
When someone shares something difficult or critical of you:
“I appreciate you telling me that. Can you say more about what that’s looked like from your side?”
“That’s useful feedback. I want to think about it properly — can I come back to you about it next week?”
That last phrase is especially useful. It buys time to process criticism without becoming defensive, and following through builds enormous trust.
🗣️ Key Phrases to Say Out Loud
-
“What’s ON your MIND this WEEK?” /wɒts ɒn jɔː maɪnd ðɪs wiːk/ — Broad, open opener that invites honest conversation, not status
-
“Is there ANYthing I’m doing that’s MAking your job HARder?” /ɪz ðɛr ˈenɪθɪŋ aɪm ˈduːɪŋ ðæts ˈmeɪkɪŋ jɔː dʒɒb ˈhɑːdər/ — Vulnerable question that signals psychological safety
-
“I NOticed that… and the IMpact was…” /aɪ ˈnoʊtɪst ðæt/ — Opens specific feedback without accusation
-
“What would make it a POINT HIGHer?” /wɒt wʊd meɪk ɪt ə pɔɪnt ˈhaɪər/ — Follow-up to the 1–10 motivation question; specific and actionable
-
“Take your TIME — there’s NO RUSH” /teɪk jɔː taɪm ðɛrz noʊ rʌʃ/ — Holds space during silence; important for building trust
-
“I APpreciate you TELLing me THAT” /aɪ əˈpriːʃɪeɪt juː ˈtelɪŋ miː ðæt/ — Acknowledges difficult feedback without becoming defensive
-
“Can I COME back to you about it NEXT WEEK?” /kæn aɪ kʌm bæk tuː juː əˈbaʊt ɪt nɛkst wiːk/ — Professional way to process criticism before responding
📚 Vocabulary
1. Flag /flæɡ/ (verb)
- Meaning: To raise attention to a problem or risk proactively
- Example: “I want you to flag blockers as soon as you spot them, not at the end of the sprint.”
2. Proactive /proʊˈæktɪv/ (adjective)
- Meaning: Acting before problems arise, rather than reacting after
- Pronunciation note: stress on the second syllable — proˈactive
- Example: “That’s exactly the proactive thinking I want more of from the team.”
3. Calibrate /ˈkælɪbreɪt/ (verb)
- Meaning: To adjust understanding or behavior based on feedback
- Example: “These 1-on-1s help me calibrate what’s working and what isn’t on the team.”
4. Candid /ˈkændɪd/ (adjective)
- Meaning: Honest and direct, even when the truth is uncomfortable
- Example: “I’d rather have a candid conversation now than discover the problem at the demo.”
5. Actionable /ˈækʃənəbəl/ (adjective)
- Meaning: Specific enough to be acted on (not vague advice)
- Example: “I want to give you feedback that’s actually actionable, not just general.”
6. Psychological safety /ˌsaɪkəˈlɒdʒɪkəl ˈseɪfti/
- Meaning: The shared belief that the team is safe for interpersonal risk-taking
- Example: “1-on-1s are where psychological safety either gets built or broken.”
7. Follow through /ˈfɒloʊ θruː/ (verb phrase)
- Meaning: To complete what you committed to doing
- Example: “If I promise to come back to you on something, I’ll follow through — that’s the expectation I hold myself to.”
🎯 Practice Now
Exercise 1: Rewrite the Safe Questions
Take these safe 1-on-1 openers and rewrite them as real questions following the patterns above. Say your versions aloud.
- “How’s everything going?”
- “Are you happy with your work?”
- “Any problems I should know about?”
- “Do you feel supported?”
Sample rewrites:
- → “What’s been the most draining part of the last two weeks?”
- → “If your motivation right now is a 7 out of 10, what would make it an 8?”
- → “What’s the one thing that, if fixed, would make the biggest difference to how you work?”
- → “Is there anything I’m doing — or not doing — that’s making your job harder?”
Exercise 2: The Specific Feedback Practice
Pick a real situation where someone on your team did something well or poorly this week. Write out the feedback using this structure:
“I noticed [specific thing]. The impact was [what it caused]. Going forward, I’d like [specific behavior change].”
Say it aloud. Check: is the “specific thing” actually specific, or is it still vague? Could the person immediately know what event you’re referring to?
Exercise 3: Handling Criticism Role-Play
Practice this scenario aloud — your report has just said something critical about you:
Report: “Honestly, I feel like you don’t always listen when I bring up concerns.”
You: “I appreciate you telling me that. Can you give me a specific example so I can understand what it looked like from your side? I want to make sure I’m not dismissing things without realizing it.”
[Report gives example]
You: “That’s useful. I don’t want to be defensive about it — I want to think about this properly. Can I come back to you about it next week? I want to give it the response it deserves.”
Practice until the “I appreciate you telling me that” doesn’t feel stiff. The first few times, it will. That’s normal.
The best tech leads aren’t the ones with the strongest technical opinions. They’re the ones their team is honest with — early, clearly, and often.
That honesty doesn’t happen automatically. It’s built, conversation by conversation, with the right questions and the right language.
Start asking the real questions.