“When two engineers stop speaking, the team stops being one team. I would bring them into the same room and make it clear the silence is now costing everyone, including them.”
“I have seen silence between two engineers spread fast, and the longer the team picks sides, the harder it gets to ship anything. I would pull both people into a room today, name the split directly, and make them talk through the work conflict before everyone else has to choose.”
“I once let two directors' silence fester until it split their whole company, so I now move fast: get both engineers in a room and slow the conversation down until each can actually hear what the other is trying to protect. The sides will fall away once people stop performing the conflict and start saying what they fear.”
“I once watched a team fracture over a backend-frontend boundary dispute until the real issue surfaced: neither lead felt heard in roadmap calls. The silence between two people becomes a proxy fight for status, so I meet them separately first, then together, and make the team see we are choosing the project, not a side.”
“I’ve seen a quiet feud between two senior engineers turn a whole floor into a cold war, and the thing that actually worked was forcing the issue into the open: same room, same whiteboard, same problem to solve, no managers mediating. At Grindr we flew the Chat team from Poland, Croatia, and Argentina to LA for exactly that reason, and they shipped a complex feature in a week because the conflict had to become code.”
“I’ve seen a team fracture over two engineers who were both technically right and personally furious; the longer I let professional stand in for unaddressed, the deeper the sides dug in. I’d pull each of them aside today, name what I see without asking them to become friends, then rebuild the team’s decision-making so their conflict stops being everyone’s proxy war.”
“I used to run a standing agenda item called the airing of grievances: door shuts, people say the thing, then we walk out as a unified front. Silence between two engineers metastasizes fast, so get them in a room with a third party and make the expectation explicit: disagree here, commit out there.”
“I have seen whole teams stall over a silence between two people, and the longer everyone pretends it is just a technical disagreement, the deeper the sides dig in. I would pull the two engineers into the same room, name the split directly, and ask each what they actually need before the team picks a path forward.”