1. OPENING LINE "Thanks for making time. I want to talk about something that's important because I value your experience and the impact you've had on this team over the years. My goal isn't to criticize you—it's to make sure we're aligned on what's expected going forward." 2. CORE MESSAGE "Over the last several weeks, I've noticed two consistent issues. First, the quality of your code has slipped compared with your previous standard—there have been more review comments and more follow-up fixes after merge. Second, your turnaround on code reviews has become noticeably slower, which has delayed other people's work. We've talked about this informally a couple of times, but I haven't seen the improvement we need. I'm bringing it up directly now because these expectations matter for the whole team's effectiveness, and I want to address it before it becomes a bigger problem. Over the next 30 days, I need to see a return to your previous standard: timely code reviews and stronger code quality that requires fewer revisions. If there's something getting in the way, I want to understand it and help where I can, but the expectations themselves aren't changing." Notice this focuses on observable behaviors ("more review comments," "slower turnaround") rather than labels like "careless" or "unmotivated." 3. BRANCH MAP Likely reaction: "It's not me. Everyone else writes bad code / requirements keep changing." What's happening: He's protecting his professional identity by shifting responsibility. Your response: "I agree there are factors outside your control, and we can work on those separately. Today, though, I'm talking about the parts you're responsible for. Regardless of the broader context, I need to see improvement in your code quality and review turnaround." Likely reaction: Silence or visible offense What's happening: He's emotionally reacting rather than engaging. Your response: "I can see this isn't easy to hear. I'm happy to give you a moment. My intention isn't to question your value to the team—it's to be clear about what I've observed and what needs to change." If the silence continues: "You don't have to agree with everything I'm saying today, but I do need to make sure the expectations are clear." Likely reaction: "You never told me this was a problem." What's happening: He's challenging the premise or the process. Your response: "You're right that our earlier conversations were informal. That's on me—I should have been more direct sooner. I'm being explicit now so there's no ambiguity about the expectations going forward." This acknowledges your part without walking back the message. 4. BOUNDARY AND NEXT STEP "Here's what we're doing. The next 30 days are an opportunity to demonstrate consistent improvement. We'll check in weekly on code quality and review turnaround so there are no surprises. If you're running into obstacles, I expect you to raise them early rather than let work slip. My commitment is to support you where I can. My expectation is that these performance issues improve over the next month." If appropriate, end with: "Do you see any obstacles that could prevent you from meeting these expectations?" This invites collaboration after the expectation has already been set. 5. SELF-REGULATION CUES Because your trigger is backing down when he becomes quiet or offended: Silence is not disagreement—and it's not a cue to retreat. Pause for a few seconds before speaking again. Repeat, don't escalate. If the conversation drifts, calmly return to: "The expectation is improved code quality and review turnaround over the next 30 days." Stay curious without negotiating the standard. Ask about obstacles, but don't bargain away the expectation. 6. READY-TO-USE SCRIPT "Thanks for meeting with me. I want to talk about something important because I value your experience and everything you've contributed over the years. My goal is to be clear, not critical. Over the last several weeks, I've seen two patterns. Your code quality has slipped compared with your previous standard, with more review feedback and follow-up fixes, and your turnaround on code reviews has become slower, which has delayed the team. We touched on this informally a couple of times, but I haven't seen the improvement we need. That's why I'm having a more direct conversation now. Over the next 30 days, I need to see consistent improvement in both code quality and review turnaround. If there are obstacles, I want to hear about them and help where I can. At the same time, these expectations need to be met because they're important to the team's performance. We'll check in weekly so we can review progress together and address issues early. Before we wrap up, I'd like to hear your perspective and whether there's anything that could get in the way of meeting these expectations." Bullet Plan Start by acknowledging their experience and your positive intent. State the facts: lower code quality, slower review turnaround, impact on the team. Note that prior informal conversations did not produce improvement. Clearly set the 30-day expectation for measurable improvement. Invite discussion about obstacles without changing the expectation. Establish weekly check-ins and close by asking for their perspective. This is a communication tool, not a substitute for a therapist, lawyer, HR, or a domestic-violence professional. If you feel unsafe, contact local emergency services or a support line.