First team conflict you have to resolve
What's actually happening
It might look like a disagreement about a technical approach, a code review that got heated, or tension around who owns a workstream. But the real issue is almost never the surface issue. Someone feels unheard, undermined, or unfairly treated.
New managers either avoid the conflict hoping it resolves itself or pick a side too quickly. Both approaches make it worse. The team is watching how you handle this. It sets the precedent for every future disagreement.
Infrastructure Team Lead, Anthropic · 10 months tenure
How to navigate this
Talk to each person separately first
Never start with a three way conversation. Hear each side privately. Ask "what happened from your perspective?" and listen without reacting. Your goal is to understand the full picture before doing anything.
Identify the real issue underneath
Technical disagreements are usually about respect, ownership, or trust. Once you hear both sides, name the pattern you see: "It sounds like this is really about who has decision authority on X."
Bring them together with a clear frame
Set the purpose of the meeting explicitly: "We're here to agree on how we'll work together on X going forward." Don't relitigate the past. Focus on the working agreement.
Follow up within a week
Check in with each person separately. Ask if the agreement is holding. Make it clear that coming to you with friction is expected, not a failure.
The difference between good and common
Sourced from five managers who resolved interpersonal conflicts in technical teams. Includes one case that escalated to HR and one that was resolved in a single conversation.
Designed by Sandra Tokarz · Application artifact for Anthropic, Talent Development & Enablement