1 min lesson
De-escalate with diagnosis, not defense
Take "De-escalate with diagnosis, not defense" step by step, then finish with the result that proves it worked.
Step 1 of 2
De-escalate with diagnosis, not defense
When a senior engineer is angry, the instinct is to defend the work. Resist it. Defensiveness confirms their fear that you don't get it. Diagnostic questions do the opposite: they show you're treating their frustration as data.
- 1Acknowledge the cost to them, specifically. "You've lost two days to this and you're getting heat from your VP - that's on me to fix."
- 2Ask, don't justify. "Walk me through exactly what broke and when - I want to see what you're seeing."
- 3Take ownership in the first person. "I'll own getting this unblocked. Here's what I'm doing in the next 24 hours."
- 4Close the loop. Come back with the fix and the metric, so the next conversation starts from trust.
Watch out: over-promising on the model
The fastest way to lose a senior engineer's trust is to claim the model guarantees something it can't. Never say "the agent won't break anything." Say what's true: "the agent will sometimes be wrong and here's the guardrail that means a wrong edit never reaches main." Honesty about limits, paired with a guardrail, is more reassuring than a promise they know is false.