In brief: when meetings and reporting lines start bending around two people, a tension has become organizational structure. Named with care, a shared secret becomes a shared project.
In most leadership teams there is one relationship doing more work than all the others. Two people who manage carefully around each other. A tension the rest of the team absorbs, routes around, and compensates for.
Everyone knows. Nobody says.
The org chart says the team has eight members. Functionally, it has six, plus a weather system.
Watch how the team actually operates and you can map it precisely. Certain topics get raised only when one of the two is absent. Certain decisions travel strange paths, through side conversations and pre-meetings, so the two are spared negotiating directly.
Colleagues develop a quiet diplomatic skill set nobody hired them for: timing, translation, de-escalation.
The cost shows up in aggregate. Decisions take three cycles instead of one. Information arrives at the top pre-shaped. And the whole team learns that some truths are unsayable here, then quietly extends that lesson to other truths.
What keeps it unnamed is a kind of misplaced decency. Naming it feels like an accusation, and everyone involved is usually competent and well intentioned.
So the team performs normalcy, and the leader performs patience while privately designing the organization around the problem.
Designing around it is the tell. The moment reporting lines and meeting invitations start bending to keep two people out of the same room, the tension is making design decisions.
The dynamic everyone notices is already public. Naming it just makes it honest, and teams can work with honest.
These notes are observations from advisory work, written with details changed and identities protected. They are patterns, not prescriptions.
All Field Notes