Difficult Conversations

Why This Matters for Engineering Leaders

With 16 direct and indirect reports, you face difficult conversations weekly: an engineer whose performance is declining, a product manager demanding unrealistic timelines, a senior IC who’s toxic but productive, a reorg that eliminates someone’s role, a promotion you can’t give. The difference between leaders who earn deep trust and those who are merely “nice” is the willingness to have these conversations honestly and caringly.

The Three Conversations Model

From Difficult Conversations (Stone, Patton, Heen – Harvard Negotiation Project), every difficult conversation is actually three conversations happening simultaneously:

Conversation	What’s at Stake	The Trap	The Shift
The “What Happened” Conversation	Who’s right? Who’s to blame?	Assuming you know their intent; arguing about facts	Move from certainty to curiosity. Explore each other’s stories
The Feelings Conversation	What emotions are involved?	Ignoring feelings or letting them hijack the conversation	Acknowledge feelings without being controlled by them
The Identity Conversation	What does this say about me?	All-or-nothing identity: “Am I competent or incompetent?”	Accept complexity: you can be a good manager AND have made a mistake

Key insight: When a conversation feels impossible, it’s usually because the identity conversation is activated. When someone’s self-image is threatened (“Am I a good engineer?”), they can’t hear your feedback – they’re too busy defending who they are.

Delivering Bad News

The Direct Approach

Bad news doesn’t improve with age. Don’t bury it in context. Don’t lead with 10 minutes of preamble. Don’t make them guess.

Structure:

1. State it clearly (1-2 sentences)
2. Acknowledge the impact (show you understand what this means for them)
3. Explain the reasoning (briefly – they deserve to understand why)
4. Outline next steps (what happens now)
5. Create space (let them respond)

Bad News by Type

Layoffs / Role Eliminations

Preparation:

• Have HR present or on standby
• Know the package details before you walk in
• Have logistics ready: last day, equipment return, reference policy
• Clear your calendar after – this takes emotional energy

Script framework:

“I have some difficult news. Your position is being eliminated as part of [reason]. This is not a reflection of your performance – this is a business decision about the role itself. Here’s what happens next: [package, timeline, support]. I want to give you space to process this. What questions do you have?”

What NOT to do:

• Don’t say “I know how you feel” (you don’t)
• Don’t over-explain or justify (it sounds defensive)
• Don’t make it about you (“This is really hard for me too”)
• Don’t ghost them afterward – follow up in 24-48 hours

Performance Improvement Plans (PIPs)

A PIP should never be a surprise. If it is, you failed as a manager long before the PIP.

Before the PIP:

• Document specific performance gaps with dates and examples
• Verify the employee has received clear feedback previously
• Confirm they had the resources, support, and clarity to succeed
• Check your own bias: is this genuinely about performance or about style/personality?

During the PIP conversation:

S (Facts): “Over the last three months, you’ve missed 4 of 6 sprint commitments, and I’ve received feedback from two team leads about incomplete handoffs on [Project X] and [Project Y].” T (Story): “This is a pattern I can’t ignore because it’s affecting the team’s delivery and your colleagues’ trust.” A (Ask): “I want to hear your perspective. What’s going on?” [Listen. Really listen.] The PIP: “Based on where we are, I need to put a formal improvement plan in place. Here’s what that looks like: [specific goals, timeline, support, consequences]. My goal is for you to succeed – I want to be clear about that.”

Key principles:

• Be specific about what “good” looks like – measurable, time-bound outcomes
• Define the support you’ll provide (weekly 1:1s, mentoring, reduced scope)
• Be honest about consequences if the PIP isn’t met
• Document everything

Promotion Denials

Structure:

“I want to talk about the promotion cycle. I advocated for you, and the decision was that it’s not this cycle. Here’s the specific feedback: [concrete gaps]. Here’s what I think you need to do to get there: [actionable plan]. I believe you can get there, and I want to help.”

Critical: Always follow with a written development plan. Words without a plan are empty.

Delivering Feedback that Stings

Not PIPs, but the regular “this needs to change” conversations.

The SBI Model (Situation-Behavior-Impact):

Element	What	Example
Situation	When and where did this happen?	“In yesterday’s architecture review…”
Behavior	What specifically did you observe? (Observable, not interpretive)	“…you interrupted Maria three times while she was presenting her proposal”
Impact	What was the effect?	“…and she stopped contributing for the rest of the meeting. I also noticed two other people went quiet after that”

Then ask: “What’s your perspective on this?”

The key: SBI separates the observable from the interpreted. “You’re dismissive” is an interpretation. “You interrupted three times” is an observation. Start with observations.

Saying No

Why Leaders Struggle with “No”

Engineering leaders are wired to solve problems and please people. Saying no feels like failure. But every yes to one thing is an implicit no to everything else. Saying no is how you protect your team’s focus, quality, and sanity.

The “No” Framework

Step	Action	Example
Acknowledge	Show you understand the request and why it matters	“I understand this feature is important for the Q2 launch, and I see why the team is pushing for it”
State the no	Be direct. Don’t hedge or leave ambiguity	“We can’t take this on in the current sprint”
Explain briefly	One reason, not five. Over-explaining invites negotiation on each reason	“We’re already at capacity with the migration, and splitting focus will put both at risk”
Offer an alternative	If possible, propose a different path	“We could pick this up in the next sprint, or we could scope it down to the MVP version that takes 3 days instead of 3 weeks”

Saying No to Your Boss

This is the hardest “no” because of the power dynamic. Three approaches:

1. Make the tradeoff visible: “I can do A or B, but not both. Which one is the priority?”
2. Show the cost: “We can do this, but here’s what it means: [delayed timeline, quality risk, team burnout]. Do you want to proceed?”
3. Propose an alternative: “Instead of X, what if we did Y, which achieves 80% of the goal at 30% of the cost?”

The key is never just saying “no” – always frame it as a tradeoff decision. You’re not refusing; you’re helping them make an informed choice.

Managing Conflict

Conflict is Not the Problem – Avoidance Is

Healthy teams have conflict. Unhealthy teams have either no conflict (fear-based silence) or destructive conflict (personal attacks). Your job as a leader is to normalize productive conflict.

When Two Engineers Are in Conflict

Step 1: Listen separately first. Meet with each person individually. Use AMPP (from Crucial Conversations). Understand their story, their feelings, their facts.

Step 2: Identify the actual disagreement. Most interpersonal conflicts are really one of these:

• Technical disagreement disguised as personal conflict (they disagree on the approach but it feels personal)
• Role/responsibility ambiguity (both think the other should be doing something)
• Communication style mismatch (one is direct, the other reads it as aggressive)
• Values conflict (one prioritizes speed, the other quality)

Step 3: Bring them together. Set ground rules:

• Focus on the issue, not the person
• Use “I” statements, not “you” statements
• Each person summarizes the other’s perspective before responding (forces listening)

Step 4: Find the mutual purpose. “What do you both want here? You both want the project to succeed and to feel respected. Let’s work from there.”

When You’re Part of the Conflict

Harder because you can’t be the neutral mediator. Key moves:

1. Check your stories (Victim/Villain/Helpless from Crucial Conversations)
2. Initiate the conversation – don’t wait for them to come to you
3. Use STATE – lead with facts, not your interpretation
4. Get a trusted third party if the conflict involves your manager or a peer at your level

Emotional Regulation

The Amygdala Hijack

When you feel threatened (ego, status, competence), your amygdala triggers fight-or-flight. Your prefrontal cortex (rational thinking) goes offline. Signs: heart racing, face flushing, tunnel vision, desire to attack or flee.

Regulation Techniques

Technique	When	How
Labeling	During the conversation	Name the emotion internally: “I’m feeling defensive right now.” Naming it reduces its power
The 6-second pause	When triggered in the moment	Pause for 6 seconds before responding. This is the neurological refractory period – enough time for the prefrontal cortex to re-engage
Physical reset	When you need a break	“Can we take 5 minutes? I want to think about what you said.” Get water, walk, breathe
Pre-conversation prep	Before the conversation	Write down your triggered scenarios. “If they say X, I’ll feel Y. My plan is Z.”
Post-conversation debrief	After the conversation	Journal what happened, what you felt, what you’d do differently. This builds emotional pattern recognition

Emotional Contagion

As the leader, your emotions are contagious. If you walk into a difficult conversation visibly anxious, the other person’s anxiety will spike. If you’re calm and grounded, they’re more likely to stay regulated. This isn’t about suppressing emotions – it’s about not dumping your emotional state onto someone who’s already stressed.

Anti-Patterns

1. The Feedback Sandwich

“You’re great, but here’s a problem, and also you’re great.” This is manipulative and transparent. People learn to dread your compliments. Just be direct.

2. The Delayed Conversation

Waiting months to address a problem that should have been addressed weeks ago. The longer you wait, the harder it gets, and the more the other person feels blindsided.

3. The Email Firing

Delivering serious bad news over Slack or email. Anything that affects someone’s livelihood, role, or standing deserves a face-to-face (or video) conversation. Email is for follow-up documentation, not the initial delivery.

4. Over-Empathizing to the Point of Inaction

“I understand this is hard” is good. Repeating it 10 times while failing to deliver the actual message is avoidance dressed as empathy. Be compassionate AND direct.

5. Making It About You

“This is really hard for me to say…” The conversation is about them, not you. Centering your discomfort on their bad news is self-indulgent.

6. The Vague PIP

“You need to improve your communication.” That’s not actionable. A PIP must have specific, measurable outcomes: “Submit PRs with complete descriptions including testing approach, by [date], for 4 consecutive weeks.”

7. Skipping the Follow-Up

Having the hard conversation and then disappearing. Always follow up within 24-48 hours: “I wanted to check in after our conversation. How are you doing? Is there anything you’d like to revisit?”

Decision Guide: Which Difficult Conversation Framework

Situation	Approach	Key Tool
Performance gap (first time)	SBI feedback model	Situation-Behavior-Impact
Performance gap (repeated, documented)	PIP conversation	Direct + specific + supportive
Layoff / role elimination	Direct delivery with empathy	Prepared script + logistics
Saying no to a request	Tradeoff framing	Make the cost visible
Two reports in conflict	Separate then joint mediation	AMPP + mutual purpose
Conflict with your own manager	STATE your path	Facts first, then story
Emotional flooding (yours)	Regulate first, then engage	6-second pause, labeling

References

• Stone, D., Patton, B., & Heen, S. (2010). Difficult Conversations: How to Discuss What Matters Most. Penguin. – The most comprehensive framework. Read chapters on the Three Conversations and the Identity Conversation.
• Patterson, K. et al. (2012). Crucial Conversations. McGraw-Hill. – Complementary framework, stronger on safety and shared meaning.
• Scott, K. (2017). Radical Candor: Be a Kick-Ass Boss Without Losing Your Humanity. St. Martin’s Press. – The “care personally + challenge directly” 2x2. Useful but oversimplified – use it as a compass, not a map.
• Heen, S. & Stone, D. (2014). Thanks for the Feedback: The Science and Art of Receiving Feedback Well. Penguin. – The receiving side. Useful for understanding why your feedback triggers people.
• Goleman, D. (2005). Emotional Intelligence. Bantam. – The foundational text on emotional regulation in leadership.
• Brown, B. (2018). Dare to Lead. Random House. – Practical framework for courage in difficult conversations. The “rumble” concept is useful.