Thursday Evening: Difficult Conversation Role-Play
Welcome to tonight’s evening session. This is your time to put everything together — review the words from today, then practice speaking in real workplace scenarios. Difficult conversations are unavoidable in tech. The goal tonight is to feel less uncomfortable the next time one comes up.
1. Quick Recap — Thursday Words
| Word | IPA | Vietnamese | Quick reminder |
|---|---|---|---|
| articulate | /ɑːˈtɪkjʊlət/ | diễn đạt rõ ràng, mạch lạc | ”She articulated the problem clearly before writing a single line of code.” |
| facilitate | /fəˈsɪlɪteɪt/ | tạo điều kiện, giúp dễ dàng hơn | ”The Scrum Master facilitates the daily standup.” |
| empathize | /ˈempəθaɪz/ | đồng cảm, đặt mình vào vị trí người khác | ”A good tech lead empathizes with their team’s workload.” |
Take 30 seconds. Cover the right column and test yourself. Can you use each word in one sentence about your current project?
2. Word of the Day — Empathize
empathize /ˈempəθaɪz/ — động từ
Vietnamese: đồng cảm, đặt mình vào vị trí của người khác
What it means in practice: To genuinely understand and share the feelings or perspective of another person — not just to acknowledge them, but to feel where they are coming from. In the workplace, empathizing does not mean agreeing. It means showing that you understand before you respond.
3 Examples
-
In a code review:
“I try to empathize with junior developers when I leave comments — I remember what it felt like to receive blunt feedback early in my career.”
-
In a project delay discussion:
“Before pushing back on the deadline, the PM took a moment to empathize with the engineering team’s concerns about technical debt.”
-
In a 1-on-1:
“She didn’t offer solutions right away. She just empathized — ‘That sounds really frustrating. I’d feel the same way.’ That made all the difference.”
Related forms
| Form | Word | Example |
|---|---|---|
| Noun | empathy | ”Show empathy before giving advice.” |
| Adjective | empathetic | ”An empathetic response builds trust.” |
| Noun (person) | empath | Less common in professional settings. |
Tip: In difficult conversations, lead with empathy. The formula: acknowledge → empathize → respond. “I hear you. That makes sense. Here is my perspective…“
3. Role-Play Scenario 1 — Giving Critical Feedback to a Junior Developer
Context
You are a senior developer. Your junior teammate, Minh, submitted a pull request with several issues: no tests written, unclear variable names, and a logic bug in the payment flow. You need to give feedback that is honest but constructive. Minh is talented but sensitive to criticism.
Useful phrases before you start
- “I wanted to chat about your PR — do you have a few minutes?”
- “Overall, I can see what you were going for here…”
- “One thing I’d like us to look at together is…”
- “This is a learning moment, not a problem.”
- “What was your thinking when you wrote this part?”
Script — Fill in the Blanks
Read the script aloud. Where you see [_____], pause and say your own words before continuing.
You: Hey Minh, do you have a few minutes? I wanted to go over your PR together.
Minh: Sure, is something wrong?
You: Not wrong — there are some things I want to walk through with you. First, I want to say [_____] (acknowledge something positive about the PR).
Minh: Oh okay, thanks.
You: Now, I noticed there are no unit tests in this PR. I understand [_____] (empathize — why might he have skipped tests?), but here is why it matters for us: [_____] (explain the business or team reason).
Minh: Yeah, I was in a hurry. I thought I’d add them later.
You: I get that. Can we agree that going forward [_____] (set a clear expectation without sounding like a rule)? I am not trying to slow you down — I want to help you build habits that will make your work stronger.
Minh: That makes sense. What about the logic in the payment flow?
You: Good question. Walk me through your thinking on that part. [_____] (ask a question rather than stating the bug directly).
Minh: Oh… wait, I think I see the issue now.
You: Exactly. You caught it yourself — that is the goal. [_____] (close with encouragement).
Debrief questions (think or say aloud)
- Did you lead with something positive before the criticism?
- Did you ask questions rather than just listing problems?
- Did you use “I” statements instead of “you always / you never”?
4. Role-Play Scenario 2 — Pushing Back on an Unrealistic Deadline
Context
You are in a sprint planning meeting. The product manager has just announced that a major feature — user authentication with OAuth, including MFA — needs to be done in one week. You and your team know this is a three-week task at minimum. You need to push back professionally without damaging the relationship or sounding obstructive.
Useful phrases
- “I want to make sure we set ourselves up for success here…”
- “Can I share some concerns about the timeline?”
- “Based on our experience with similar work…”
- “What is the most critical part of this feature for the launch?”
- “What if we shipped X first, and followed up with Y in the next sprint?”
Script — Read Aloud, Add Your Words
PM (Lan): Alright, so OAuth + MFA needs to be done by next Friday. Can the team commit to that?
You: Lan, I appreciate the urgency — I know this feature is important for the Q3 roadmap. Before we commit, can I share some concerns?
Lan: Of course, go ahead.
You: Based on our experience with similar authentication work, [_____] (give a realistic estimate with reasoning). We are not trying to slow things down — we want to be honest about what a quality implementation looks like.
Lan: But the business really needs this by next Friday. Can’t we cut some corners?
You: I understand the pressure. Let me ask — [_____] (ask what the minimum viable version looks like). If we prioritize that, we might be able to hit a partial milestone by Friday.
Lan: The most critical part is the basic OAuth login. MFA can come later, I suppose.
You: That is helpful. If we focus on OAuth only this sprint, [_____] (confirm what you can deliver and when). Does that work as a plan?
Lan: That works. Can you document the full scope so we can plan the next sprint?
You: [_____] (confirm and close positively).
Key techniques used in this scenario
| Technique | Why it works |
|---|---|
| Acknowledge the goal first | Shows you are on the same team |
| Use data / past experience | Makes the pushback objective, not personal |
| Ask what is truly critical | Opens space for negotiation |
| Offer an alternative | You are a problem-solver, not a blocker |
| End with a clear commitment | Leaves the conversation on a productive note |
5. Speaking Challenge — 60-Second Talk
Set a timer for 60 seconds. Speak continuously. Do not stop to correct yourself — keep going.
The prompt
“Think of a time at work when you had a difficult conversation — giving or receiving feedback, disagreeing with a decision, or discussing a problem with a colleague. What happened? How did you handle it? What would you do differently now?”
Structure to follow (optional)
- 0–10 sec: Set the scene. Who was involved? What was the situation?
- 10–30 sec: What did you say or do? How did the other person react?
- 30–50 sec: What was the outcome? Was it resolved well?
- 50–60 sec: One thing you would do differently with today’s vocabulary.
Phrases to try slipping in
- “I tried to empathize with their position…”
- “I should have articulated my concerns more clearly…”
- “Looking back, I could have facilitated a better discussion by…“
6. Evening Challenge — One Thing Before Tomorrow
Pick one of the following to do before you sleep or before your first meeting tomorrow:
- Option A — Write it out: Think of an upcoming conversation you have been avoiding. Write 3 sentences you could open with. Use at least one of today’s three words.
- Option B — Say it out loud: Repeat Scenario 2’s opening line five times until it feels natural: “Before we commit, can I share some concerns?”
- Option C — Observe: In your next Slack or email exchange, notice — does the other person lead with empathy or jump straight to their point? How does it land?
There is no quiz. The goal is one small, concrete action that connects today’s lesson to your real work.
7. Preview — Friday: Career and Growth
Tomorrow we shift from conversation skills to the bigger picture: your career trajectory as a tech professional.
Topics coming up:
- Vocabulary for talking about career goals, performance reviews, and promotions
- How to discuss your strengths and areas for growth in English
- Key phrases for mentorship conversations and 1-on-1s with your manager
- Word of the Day: something you will want in your next performance review
Prepare by thinking about: How would you answer this in English — “Where do you see yourself in two years?” — in a way that sounds confident and specific, not vague?
Good work tonight. Difficult conversations do not get easier because they become less uncomfortable — they get easier because you get more prepared. See you tomorrow morning.