Fragmentation

It describes the breakdown of coordination between interdependent parts that are still, in fact, connected. Two teams can each be doing good, competent work and still end up building conflicting versions of the same feature, or making promises to the same customer that the other team never hears about — not because they've stopped needing each other, but because their actions no longer reflect what the other is actually doing. The interdependence hasn't gone anywhere. What's missing is behavior that accounts for it. The system keeps running, but every uncoordinated decision adds friction the next decision has to work around.

This tends to be felt as disconnection or miscommunication long before anyone names it structurally. Each part may be acting reasonably from where it sits — the tension comes from behavior that no longer reflects the relationship that's actually there. That gap produces redundancy (two teams solving the same problem separately) and contradiction (two decisions that quietly undo each other) without either side doing anything that looks wrong in isolation.

This is what makes a struggling system hard to diagnose from the outside — everything is still technically running. Parts keep producing output, meetings keep happening, deadlines mostly get hit, and none of that visible activity reveals that coordination itself has quietly stopped. Restoring coherence here isn't about adding more connection or more communication in volume; it's about making sure the connections that already exist are carrying accurate information about what the other parts are actually doing.