# Difficult Conversation Pack: Performance Conversation with Senior Engineer

---

## 1) Conversation Brief

### Context
- **Conversation type:** Performance feedback / behavior change
- **Relationship:** Manager (you) to direct report (senior engineer)
- **Person:** Senior Engineer (anonymized as "Alex")
- **When/where:** This week; in-person preferred (private meeting room, door closed), or video with cameras on if remote. Schedule for a time when neither of you has a hard stop immediately after.
- **Time box:** 45 minutes (30 min conversation + 15 min buffer)
- **HR/legal involved?** Not yet required (this is a direct feedback/improvement conversation, not a formal PIP or termination). However, document the conversation and outcomes. If behavior does not improve after the 4-week plan, escalate to HR for a formal performance improvement plan.

### Desired Outcomes
- **Immediate (right after the conversation):**
  - Alex understands that the pattern of missed sprint commitments, late standups, and resistance to peer code review feedback has been noticed, is being taken seriously, and must change.
  - Alex feels heard -- you have opened space for them to share what is going on (burnout, personal circumstances, or other root causes).
  - You and Alex agree on a concrete 4-week improvement plan with measurable expectations and weekly check-ins.
- **In 2-4 weeks:**
  - Alex meets sprint commitments for 2 consecutive sprints.
  - Alex attends standups on time consistently.
  - Alex engages constructively with peer code review feedback (acknowledges comments, incorporates or discusses with reasons).
  - Team morale stabilizes; no further private complaints from peers about Alex's behavior.

### Non-Negotiables (3 bullets)
- The missed commitments, late attendance, and code review pushback must change starting this sprint. This is not optional.
- Weekly 1:1 check-ins for the next 4 weeks to track progress together.
- If the pattern continues after 4 weeks, the next step is a formal performance improvement plan (PIP) with HR involvement.

### Facts + Examples (3 specific, observable, time-bounded)

- **Example 1: Missed sprint commitments (3 consecutive sprints)**
  - Observation: In Sprint 14, Sprint 15, and Sprint 16, Alex committed to deliverables that were not completed by sprint end. [Insert specific ticket IDs or feature names if available.]
  - Impact: Downstream dependencies were delayed, cross-functional partners had to re-plan, and the team's sprint velocity has become unpredictable. Other engineers have had to absorb unfinished work.

- **Example 2: Late to standups**
  - Observation: Over the past 3-4 weeks, Alex has arrived 5-15 minutes late to daily standup on a recurring basis. [Note specific dates if you have them, e.g., "At least 8 of the last 15 standups."]
  - Impact: The team waits or moves on without Alex's update, which creates information gaps and signals to the team that standup is optional. Two engineers have flagged this to you privately.

- **Example 3: Pushback on peer code review feedback**
  - Observation: In recent PRs [reference specific PRs if possible], Alex has dismissed or pushed back on substantive code review comments from peers without providing technical rationale -- responding with short rejections or ignoring comments entirely.
  - Impact: Peer engineers feel their feedback is not valued, which discourages them from reviewing Alex's code thoroughly. This erodes the team's code quality culture and has contributed to declining morale.

### Expectations / Standard
- **What "good" looks like:**
  - A senior engineer is expected to deliver on sprint commitments or proactively flag blockers and re-scope before sprint end.
  - Attendance and punctuality at team ceremonies (standups, retros, planning) is a baseline professional expectation at every level.
  - Senior engineers model constructive engagement with code review: they respond thoughtfully to feedback, explain trade-offs when they disagree, and treat peer review as a collaborative quality gate.
- **Where this comes from:** Team working agreements, engineering level expectations for senior engineers, and general professional standards.

### Support I Can Offer
- Reduce scope or re-prioritize Alex's sprint load for the next 2 sprints while they get back on track.
- Pair Alex with a peer for planning/estimation to improve commitment accuracy.
- Flexible schedule adjustments if personal circumstances require it (within team norms).
- Connect Alex with EAP (Employee Assistance Program) or mental health resources if burnout or personal issues are a factor.
- Weekly 1:1s focused specifically on progress, blockers, and wellbeing (not just status updates).
- Shield Alex from non-essential meetings or interrupt-driven work for 4 weeks.

### Boundaries + Consequences
- **What is not up for debate:** The pattern must change. The team cannot absorb continued missed commitments and disengagement.
- **If nothing changes by [4 weeks from conversation date]:** We will move to a formal performance improvement plan with HR involvement, which has a defined timeline and consequences.

### Risks / Sensitivities
- Alex was a top performer 6 months ago. There is likely a root cause (burnout, personal issue, disengagement). Leading with curiosity alongside directness is critical to preserving the relationship and getting to the real problem.
- If Alex discloses a mental health issue or protected personal circumstance, shift to support mode, involve HR as appropriate, and do not use it against them.
- Two team members have raised concerns privately. Do not name them or reveal who spoke to you.
- Risk of Alex feeling "ambushed" if they have no idea this is coming. The directness of the opening mitigates this.

---

## 2) Message Map (Spine for the Conversation)

### Opening (direct + caring)
- "Alex, I asked for this meeting because I need to talk with you about some things I've been observing over the past few sprints. I'm going to be direct, because I care about you and your success on this team."

### Key Message (1-2 sentences, no hedging)
- "Over the last three sprints, you've missed your sprint commitments, you've been consistently late to standup, and there's been friction in how you're engaging with code review feedback from your peers. This is a pattern that needs to change, and I want to understand what's going on and figure out how to move forward together."

### Evidence (3 bullets)
- "In Sprints 14, 15, and 16, committed work was not delivered by sprint end, which caused downstream teams to re-plan."
- "You've been arriving late to standup regularly over the past several weeks, which disrupts the team's rhythm and creates information gaps."
- "In recent pull requests, peer review comments have been dismissed or ignored without discussion, which is discouraging your teammates from engaging in reviews."

### Impact (why it matters)
- "The combined effect is that the team's velocity is unpredictable, trust between you and your peers is eroding, and team morale is suffering. Other engineers have noticed, and it's affecting how the whole team operates."

### Ask / Decision
- "Starting this sprint, I need you to meet your commitments or proactively flag and re-scope before sprint end, attend standups on time, and engage constructively with code review feedback. I'm proposing we put a 4-week plan in place with weekly check-ins so we can track progress together."

### Support (hope + a path)
- "I want to help you get back to where you were. I can reduce your sprint load, pair you with someone for estimation, adjust your schedule if you need flexibility, and connect you with any resources that would help. I also want to understand if there's something going on that I should know about so I can support you properly."

### Boundaries
- "I want to be transparent: the pattern as-is cannot continue. If we don't see sustained improvement over the next four weeks, the next step would be a formal performance improvement process with HR."

### Close (summary + next step)
- "To recap: I need to see consistent sprint delivery, on-time standup attendance, and constructive code review engagement starting now. We'll check in weekly. I'll send you a written summary of what we discussed and the plan by end of day tomorrow. What questions do you have?"

---

## 3) Talk Track / Script

**[Opening -- set intent, be direct and caring]**

> "Alex, thanks for making time for this. I want to talk about something important, and I'm going to be direct with you because I genuinely care about you and your growth here. This isn't going to be a comfortable conversation, but it's one we need to have."

**(Pause. Let the tone land.)**

**[Key message -- deliver early, then pause]**

> "Over the last three sprints, I've seen a pattern that concerns me. You've missed your sprint commitments three times in a row, you've been consistently late to standup, and you've been pushing back on code review feedback from peers in a way that's shutting down collaboration. I need to talk about this because it's affecting the team."

**(Pause. Give them space to react. Do not fill the silence.)**

**[Evidence + impact -- facts, not labels, 3 examples max]**

> "Let me be specific. In Sprints 14, 15, and 16, the work you committed to wasn't completed by sprint end, and downstream teams had to adjust their plans. Over the past few weeks, you've been arriving to standup late on a regular basis, which means the team either waits or moves on without your update. And on recent pull requests, comments from your peers have been dismissed without discussion, which discourages them from doing thorough reviews."

> "The cumulative impact is real. The team's delivery has become unpredictable, and the dynamic between you and your peers is strained. People have noticed, and morale is being affected."

**[Invite their perspective -- curiosity, not interrogation]**

> "I want to understand what's going on from your side. You were one of the strongest contributors on this team six months ago, and this is a real shift. Is there something happening that I should know about?"

**(Pause. Listen. Do not interrupt. Let them talk.)**

**[Anchor phrase if needed]**

> "I hear you, and I appreciate you sharing that. I want to stay on the core point, which is that the pattern needs to change, and I want to figure out how to support you in making that happen."

**[Ask + support]**

> "Here's what I'm proposing. Starting this sprint, I need you to deliver on your commitments or flag blockers early so we can re-scope together. I need you at standup on time. And I need you to engage with code review feedback constructively -- that means responding to comments, discussing trade-offs, not dismissing them."

> "On my side, I can lighten your sprint load for the next couple of sprints, pair you with someone for estimation, give you schedule flexibility if you need it, and connect you with our EAP if that would help. I want to remove obstacles, not just point at problems."

**[Boundaries -- clear and calm]**

> "I want to be upfront about what happens if we don't see improvement. If this pattern continues over the next four weeks, the next step is a formal performance improvement plan with HR. I don't want that -- I'm telling you now so there are no surprises."

**[Close -- confirm understanding and next steps]**

> "Let me summarize. I need to see consistent sprint delivery, on-time standups, and constructive code review engagement. We'll have weekly check-ins for the next four weeks to track progress and address anything that comes up. I'll send you a written recap of this conversation and the plan by end of day tomorrow."

> "What are you hearing me say? Is there anything that feels unclear?"

**(Pause. Listen. Clarify if needed.)**

> "Thank you for hearing me out, Alex. I'm in your corner. Let's make the next four weeks count."

---

### Anchor Phrases (repeat under stress)
1. "I hear you. Let's stay on the core point: the pattern needs to change, and I want to help."
2. "I'm being direct because I care about your success here."
3. "Let's focus on what happens next."

---

## 4) Objection + Emotion Handling Plan

| Likely Reaction | What They Might Say | What You Do (1-2 moves) | What You Say | What NOT to Do |
|---|---|---|---|---|
| **Shock / surprise** | "I had no idea this was a problem." / "Why didn't you say something sooner?" | Pause. Acknowledge that this may feel sudden. Take responsibility if you could have flagged it earlier. | "I understand this may feel like it's coming out of nowhere. I should have raised it sooner, and I'm raising it now because the pattern has become clear and it needs to be addressed." | Do not over-apologize or let the conversation become about your timing instead of the behavior. Do not retract the feedback. |
| **Defensiveness / justification** | "The sprint estimates were unrealistic." / "Those code review comments were wrong." / "I'm only a few minutes late, it's not a big deal." | Acknowledge their perspective briefly, then return to the pattern and impact. Do not debate each individual instance. | "I hear that you see it differently on some of these. What I'm focused on is the overall pattern and its impact on the team. Even if any single instance has context, three sprints in a row, repeated lateness, and multiple teammates feeling shut down in reviews -- that's a pattern we need to address." | Do not argue point by point. Do not "kitchen-sink" additional examples. Do not get pulled into relitigating each sprint or PR. |
| **Anger / frustration** | "This is unfair." / "Other people miss deadlines too." / "You're singling me out." | Stay calm. Breathe. Let them express frustration without matching their energy. Acknowledge the emotion, then re-center. | "I can see you're frustrated, and that's understandable. This conversation is about your performance because I'm your manager and I have a responsibility to raise this with you directly. I'm not comparing you to others -- I'm talking about what I need from you." | Do not get defensive yourself. Do not bring up other team members. Do not raise your voice or match their intensity. Do not say "calm down." |
| **Sadness / withdrawal** | (Goes quiet, looks down, tears up.) | Give space. Sit in silence for 10-15 seconds. Offer a brief empathy statement. Offer to pause if needed. | "I can see this is hard. Take your time. We can pause for a minute if you need to." ... (After a pause) "I'm raising this because I believe in your ability to turn this around. That's why we're having this conversation." | Do not rush to fill silence. Do not minimize ("It's not that bad"). Do not pivot to forced positivity. Do not hand them tissues aggressively -- just have them available. |
| **Disclosure (burnout / personal issue)** | "I've been dealing with something personal." / "I'm completely burned out." / "Things at home have been really hard." | Listen fully. Thank them for sharing. Shift partially to support mode. Do not probe for details they don't offer. Keep the improvement expectation but adjust the support plan. | "Thank you for telling me that. I'm sorry you're going through this. That context helps me understand what I'm seeing. I still need the pattern to change, but let's talk about what support would actually help -- whether that's adjusting your workload, flexible hours, or connecting you with our EAP. We can figure out the right plan together." | Do not pry for details. Do not use what they share against them. Do not waive all expectations -- the team still needs reliability. Do not diagnose or play therapist. Do not promise confidentiality you cannot guarantee (e.g., if HR needs to know). |
| **Negotiation / deflection** | "Can we just wait and see?" / "I'll try harder." / "Give me one more sprint." | Acknowledge their willingness to improve, but hold the line on the structured plan and check-ins. Vague promises are not enough. | "I appreciate that you want to improve. I need more than 'I'll try' -- that's why I'm proposing a specific plan with weekly check-ins. It gives us both a way to see progress concretely. Let's define what success looks like together so there's no ambiguity." | Do not accept vague commitments without a plan. Do not drop the check-in cadence. Do not agree to "just wait and see." |

---

## 5) Follow-Up Note (Send Within 24 Hours)

**Subject:** Follow-up: Our conversation on [date]

Hi Alex,

Thank you for the conversation today. I know it wasn't easy, and I appreciate your willingness to engage with it.

Here is a summary of what we discussed:

**What I observed:**
- Sprint commitments missed in Sprints 14, 15, and 16, causing downstream delays.
- Recurring late arrival to daily standup over the past several weeks.
- Pushback on peer code review feedback without constructive discussion.

**The core message:**
This pattern is affecting team delivery, collaboration, and morale, and it needs to change starting now.

**What needs to change (expectations for the next 4 weeks):**

| Focus Area | Expectation | How We'll Measure |
|---|---|---|
| Sprint delivery | Meet committed scope, or proactively flag and re-scope by mid-sprint | Committed vs. delivered tickets at sprint end |
| Standup attendance | Arrive on time to daily standup | Attendance log / observation |
| Code review engagement | Respond to peer review comments constructively -- acknowledge, discuss trade-offs, or incorporate | PR review threads; peer feedback at check-ins |

**4-Week Improvement Plan:**

| Week | Focus | Check-in |
|---|---|---|
| **Week 1** (starting [date]) | Establish baseline. Agree on sprint commitment scope (reduced if needed). Resume on-time standups. Engage with at least 2 peer review threads constructively. | 1:1 on [date] -- review sprint commitment, standup attendance, and initial code review engagement. |
| **Week 2** ([date range]) | Sustain Week 1 improvements. Complete committed sprint work or escalate blockers by Wednesday. | 1:1 on [date] -- review sprint progress mid-cycle, discuss any obstacles. |
| **Week 3** ([date range]) | Demonstrate consistency. Full sprint commitment delivered. Constructive engagement on all PR reviews. | 1:1 on [date] -- review sprint delivery, peer feedback on reviews, overall trend. |
| **Week 4** ([date range]) | Consolidate. Full sprint delivery. On-time standups. Positive peer review dynamic. | 1:1 on [date] -- final review of 4-week plan. Decide path forward together. |

**Support I am providing:**
- Reduced sprint load for the next 1-2 sprints (we will right-size together in planning).
- Pairing with [peer name] for estimation support.
- Schedule flexibility as needed -- let me know what would help.
- EAP / mental health resources available if you want them (no questions asked): [link or contact info].
- Weekly 1:1s dedicated to this plan (not just status -- we'll talk about how you're doing overall).

**What happens at the end of 4 weeks:**
- If we see sustained improvement, we'll return to a normal cadence and I'll consider this resolved. I'll make sure to recognize the progress.
- If the pattern continues, the next step is a formal performance improvement plan with HR involvement. I'm being transparent about this so there are no surprises.

**Check-in schedule:**
- Week 1: [specific date and time]
- Week 2: [specific date and time]
- Week 3: [specific date and time]
- Week 4 (final review): [specific date and time]

If I've missed anything important from our conversation, or if something here doesn't match your understanding, please let me know and we'll align.

I meant what I said -- I believe you can turn this around, and I'm here to support you in doing it.

Best,
[Your name]

---

## 6) Documentation Note (Manager Record -- Keep Factual)

**Title:** Performance conversation summary -- Sprint delivery, standup attendance, code review engagement -- [date]

- **Participants:** [Your name] (Engineering Manager), Alex (Senior Engineer)
- **Context/type:** Direct performance feedback conversation (behavior change). Not a formal PIP. HR not involved at this stage.
- **Facts/examples discussed:**
  - Missed sprint commitments in Sprints 14, 15, and 16.
  - Recurring late arrival to daily standup over past 3-4 weeks.
  - Dismissive engagement with peer code review feedback on recent PRs.
- **Expectations stated:** Meet sprint commitments or re-scope proactively; attend standup on time; engage constructively with peer code reviews.
- **Agreements/next steps + dates:**
  - 4-week improvement plan starting [date].
  - Reduced sprint load for 1-2 sprints.
  - Weekly 1:1 check-ins: [dates for weeks 1-4].
  - Final review at end of Week 4.
  - If no improvement after 4 weeks, escalate to formal PIP with HR.
- **Employee response (brief):** [To be filled in after the conversation -- note their general reaction and any commitments they made or context they shared, without sensitive personal details.]
- **Follow-up cadence:** Weekly check-ins for 4 weeks.

---

## 7) Risks / Open Questions / Next Steps

### Risks
- **Root cause unknown:** If Alex is experiencing burnout, personal crisis, or a medical issue, the improvement plan may need to be adjusted. Be prepared to shift to an accommodation/support track if they disclose something that warrants it.
- **Perception of unfairness:** Alex may feel singled out, especially if they perceive others also miss deadlines. Stay focused on the specific pattern and its impact; do not compare team members.
- **Flight risk:** Alex was a top performer 6 months ago. A direct conversation could trigger them to start looking elsewhere. This is a risk worth taking -- the alternative (saying nothing) guarantees continued team damage and is unfair to Alex, who deserves to know where they stand.
- **Team dynamics:** Two engineers raised concerns privately. If Alex's behavior does not change, those engineers may disengage or escalate further. Timely follow-through on this plan is critical to retaining team trust.
- **Escalation to PIP:** If the 4-week plan fails, you will need HR partnership. Brief your HR business partner now so they are not surprised if it escalates.

### Open Questions (would change the plan if answered)
- **What is the root cause?** Burnout, personal issues, disengagement, or something else? The conversation should surface this. If it's burnout or personal circumstances, the support plan may need to include time off, workload reduction, or professional support beyond what's outlined here.
- **Has Alex received any prior feedback on these issues?** If this is the first time they are hearing about it, acknowledge that and take some ownership for not raising it sooner.
- **Are there specific sprint estimation or scoping issues** that made the commitments unrealistic? If so, the problem may be partly systemic (estimation practices), not purely individual.
- **Does your company have a formal performance management process** that requires specific documentation or HR notification at this stage? Confirm before the conversation.
- **Are the two engineers who raised concerns willing to give direct feedback to Alex** (now or later), or does it need to stay anonymous? This affects how you frame the "team morale" point.

### Next Steps

| Action | Owner | By When |
|---|---|---|
| Brief your HR business partner that you're having this conversation and may need PIP support in 4 weeks | You | Before the conversation |
| Schedule the conversation with Alex in a private setting (45-min block) | You | This week |
| Prepare your personal notes: specific ticket IDs, standup dates, PR links to reference if needed | You | Before the conversation |
| Have the conversation | You | This week |
| Send written follow-up note (Section 5 above) | You | Within 24 hours of conversation |
| Schedule 4 weekly check-in 1:1s | You | Day of conversation |
| Complete documentation note (Section 6 above) with Alex's response | You | Within 24 hours of conversation |
| Week 1 check-in | You + Alex | [Date] |
| Week 2 check-in | You + Alex | [Date] |
| Week 3 check-in | You + Alex | [Date] |
| Week 4 final review -- decide path forward (resolved vs. formal PIP) | You + Alex (+ HR if escalating) | [Date] |

---

## Quality Gate: Self-Assessment

### Checklist Pass/Fail

**Prep checklist:**
- [x] Conversation type and desired outcome stated in one sentence: "This is a performance feedback conversation with my direct report to address missed sprint commitments, late standups, and code review friction, with the goal of agreeing on a 4-week improvement plan."
- [x] 3 specific, observable, time-bounded examples with impact.
- [x] Expectations/standard clearly stated.
- [x] Non-negotiables are explicit and consistent with policy.
- [x] Support menu defined.
- [x] Private setting recommended with adequate time.
- [x] Follow-up plan with summary note + weekly check-in cadence.
- [x] STOP checks clear: No harassment/discrimination/investigation; not a termination/layoff.

**Script checklist:**
- [x] Key message deliverable in 1-2 sentences without hedging.
- [x] Script is direct and respectful (care personally + challenge directly).
- [x] Evidence limited to 3 examples (no kitchen-sinking).
- [x] Pauses included.
- [x] No labels or attributions -- uses observable behaviors.
- [x] Boundaries are clear.

**Follow-up checklist:**
- [x] Written recap template provided (send within 24 hours).
- [x] Check-in schedule defined (weekly for 4 weeks).
- [x] Expectations documented with measurable criteria.
- [x] Escalation path identified (formal PIP at 4 weeks if no improvement).

### Rubric Scores

| Dimension | Score | Notes |
|---|---|---|
| Clarity + directness | 5 | Key message stated early and explicitly; boundaries and next steps unmistakable. |
| Care + respect (dignity) | 5 | Acknowledges likely emotional weight; creates space for disclosure; offers genuine support. |
| Specificity + fairness | 5 | 3 observable, time-bounded examples tied to impact; no labels or character judgments. |
| Safety + policy alignment | 4 | Stop checks addressed; HR briefing recommended; routes disclosure to EAP. Minor gap: specific company PIP policy not confirmed (flagged in Open Questions). |
| Emotion + objection handling | 5 | 6 likely reactions mapped with specific response moves, anchor phrases, and anti-patterns. |
| Follow-up system | 5 | Written follow-up template, 4-week plan with measurable criteria, weekly check-in schedule, escalation path. |
| **Average** | **4.83** | **Pass** (>=4 average, no dimension below 3, no Stop items triggered). |