We're Fine. It's Them.
You know the feeling. Your team's retros are positive. Velocity is stable. People genuinely like working together. Psych safety is high — folks admit mistakes, ask dumb questions, challenge each other without it getting weird. By every internal measure, you're a healthy, high-performing team.
And yet.
Every dependency is a nightmare. Every cross-team interaction feels like pulling teeth. You're waiting three weeks for a PR review from another squad. Their API keeps breaking yours. Planning sessions with them feel like hostage negotiations. And the conclusion your team reaches — naturally, inevitably — is: "We're fine. It's them."
I've been in this room. Multiple times. On both sides of it. And I've come to believe that this specific pattern — a team that feels healthy internally but generates friction at every boundary — is one of the most dangerous failure modes in engineering orgs. Not because it's dramatic, but because it's invisible. The team genuinely is healthy by local measures. That's what makes it so hard to diagnose.
I've started calling this the insular health fallacy — the belief that internal team health equals systemic health. The team isn't broken. The interface is broken. But from inside, it looks like everyone else is the problem.
Social psychology has a name for the underlying mechanism: in-group bias. The minimal group experiments in the 1970s showed that people will favour their own group — even when the groups are assigned randomly. Give people a label, any label, and they'll start preferring "us" over "them." Now imagine what happens when "us" is a team that's genuinely built trust, shared context, and psychological safety over months or years. The in-group cohesion becomes a fortress. And fortresses, by design, keep people out.
