Scenarios
Two engineers on your team disagree about an architectural direction
and it's turning personal in code review. What would you do — ask them
to keep it professional and move on, or get the actual technical
disagreement written down and decided so there's nothing left to be
personal about?
A colleague has clearly been annoyed with you for weeks and hasn't
said why. What would you do — wait for them to raise it, or ask
directly and privately, accepting that the conversation will be
uncomfortable and the alternative is that it never happens?
You're in a heated thread where a message you sent has been read far
more harshly than you meant it. What would you do — send a longer
message clarifying your intent, or stop writing and get on a call?
Takeaway
- Name the disagreement plainly before trying to solve it. You can't
settle something nobody has stated.
- Keep it to the current issue. Bringing history in expands the conflict
past what any single conversation can close.
- Go to the person first. Every round of discussing it with others makes
the eventual direct conversation harder.
- Move a charged exchange out of writing. Text has no tone, and both
sides will supply the worst available one.
- Aim for a decision people understand, not for everyone feeling fine.
Comfort without resolution just reschedules the conflict.