Two people on the same team have the same argument every few weeks. The topic changes: a deadline, a hire, a slide deck. The shape does not. One escalates, the other withdraws. Afterward, both privately conclude the same thing: the other one is difficult.

That conclusion is the most expensive mistake in organizational life, because it is unfixable by design. If the problem is who someone is, the only remedies are tolerance and departure. Neither is a strategy.

The alternative is to treat the exchange as a structure rather than a personality clash: something with parts, an order, and a set of conditions under which it reliably runs. Structures can be mapped. Once mapped, they can be interrupted at a specific point, which is a far smaller task than changing a person.

Mapping starts before the argument, not during it. What was each person doing in the ten minutes prior? What had just been said, and by whom, and in front of whom? Recurring conflicts almost always have a reliable trigger, and it is rarely the topic under discussion. More often it is a condition: an audience, a deadline, a decision that was made without one of them in the room.

Next comes the sequence. Not what each person felt, but what each person did, in order, in observable terms. Raised the voice. Went quiet. Started listing prior examples. Checked the phone. This is unglamorous work, and it is where the pattern usually becomes obvious to everyone involved, often for the first time, because nobody has previously written it down.

Last is the payoff. Every stable pattern persists because it works for someone, at least in the short run. Withdrawal ends an unpleasant exchange. Escalation produces a decision. Neither person is being irrational; each is running a strategy that has succeeded before, and the two strategies happen to feed each other.

What emerges from that map is not blame. It is a diagram with a small number of intervention points: moments where a different move is available and cheap. The pair does not need to like each other more. They need one of them to do something different at minute two, reliably, until the loop stops closing.

This is what it means to say behavior is structural. Not that people don't matter, but that the pattern is doing more of the work than either person realizes, and that the pattern, unlike the people, is something you can take apart.