The Pattern Nobody Chose

You ask again, a little more directly this time, because a moment ago the silence felt like something slipping away. They go a little quieter, because the directness feels like something closing in.

You press because distance feels dangerous. They withdraw because intensity feels dangerous. Each response, reasonably, produces more of the exact thing the other person is reacting to. The quieter they get, the more you need to hear something back. The more you ask, the further they need to go to find room to breathe.

Neither of you is doing anything you haven’t done a dozen times before. That’s what makes it hard to see from inside it: nothing here is new. It’s a familiar shape, running again, a little faster than last time. By the time either of you notices, you’re a long way into a pattern neither of you designed and neither of you can find the start of.

There’s a pull, somewhere in the middle of it, to work out who started this. If they hadn’t gone quiet, you wouldn’t have needed to press. If you hadn’t pressed, they wouldn’t have needed to go quiet. Both accounts are true, which is exactly the problem. Looking for the first move doesn’t end the pattern. It tends to deepen it, because now each of you also has to defend the reasonableness of your own move, which means holding onto it a little harder, which means the other person gets a little more of what they were already reacting to.

The result doesn’t belong to either of you. It belongs to the loop between you. Each move makes sense from its own position, but together the two responses produce an outcome neither of you wants.

A product organisation can run the same loop at a larger scale. One team protects a launch date. Another avoids replacing a component everyone already knows is fragile, because migration feels riskier than continuing. A third optimises the metric its own leadership will actually ask about. None of this is unreasonable. Each team is making the same kind of locally defensible move you were making a moment ago. Nobody decides to fragment the product. Fragmentation emerges when several sensible decisions start answering each other faster than anyone can see their combined effect, then persists because each team continues to protect the part for which it is responsible.

Once it’s visible, the instinct is the same one you already know: find whichever team’s move is least defensible, and hold it responsible for the shape of the whole thing. It rarely works, for the same reason it didn’t work between the two of you a moment ago. Everyone can show that their move was reasonable, because it was. The pattern was never contained in any single decision. It arose from the way the decisions kept meeting each other.

Change doesn’t start with finding who is at fault. It starts when everyone can examine the pattern itself, rather than one person’s motives or one team’s choices, as something each side is helping to maintain and has been trying to survive alone. Nobody chose the pattern, but each participant has a part in sustaining it.