The Two Structures Every Organization Runs On
The chart and the current underneath it
Every organization has an org chart. Boxes, lines, titles, reporting relationships. It is the structure leaders point to when they explain how work gets done. It is also, on its own, almost never sufficient to explain how work actually gets done.
Underneath the chart sits a second structure. Nobody draws it. It has no boxes and no owner. It is made of the informal channel where two departments actually coordinate, distinct from the meeting where they are scheduled to coordinate. The unwritten norm that certain decisions get tested with certain people before they go anywhere official. The web of who trusts whom enough to say the honest version of something, rather than the version that is safe to put in writing. None of this appears in an org design deck. All of it is doing real work.
This second structure is not a nice supplement to the formal one. It is load bearing. Take it away and the formal structure, the one on the chart, does not simply get less efficient. It reveals that it was never doing the work alone.
What a merger actually has to merge
Mergers make this unusually visible, because a merger does not combine one structure. It combines two. On paper, the exercise looks clean: two org charts become one, redundant titles are resolved, a new reporting structure is issued. What actually has to happen is much harder and almost never scheduled. Two separate invisible layers, each built over years, each with its own norms about who gets consulted and how information actually moves, have to be reconciled or replaced. The formal integration can be finished in a quarter. The informal one often isn't finished in two years, and during that gap, people on both sides describe the same experience: the new chart says we're one company, but nothing moves the way it used to, and nobody can say exactly why.
What an ordinary reorg leaves out
The same thing happens on a smaller scale inside an ordinary reorganization. Leadership redraws reporting lines to fix a real problem, unclear ownership, duplicated effort, slow decisions, and the redesign is often genuinely sound on paper. What it does not account for is that the old structure was working, to whatever degree it was working, partly because of relationships and routes of trust that had nothing to do with the reporting lines being changed. Move the boxes and you have not moved the trust. It has to be rebuilt from somewhere close to zero, under a new chart that assumes it already exists.
This is not an argument for sentimentality about how things used to be done. Informal structures can entrench bad habits, protect underperformance, or route around the very problems a reorg is trying to fix. The point is not that the hidden infrastructure is always good. The point is that it is always there, and any redesign that only accounts for the visible structure is planning around half of what actually makes the organization function.
Why it stays invisible until it fails
There is a reason infrastructure, in the literal sense, is invisible when it works. Nobody thinks about the load bearing wall until it is removed. Nobody thinks about the water main until it fails. The absence of attention is not evidence of the absence of function. It is evidence that the function is being performed well enough not to require attention, which is a very different thing, and considerably more fragile than it looks from the outside.
Taking inventory before you redesign
Organizations that take structural change seriously have started asking a different question before they redesign anything. Not only what should the new structure be, but what invisible work is currently holding the current one up, and what happens to that work the moment it is asked to operate inside an entirely different set of lines. That question does not have a tidy answer. It requires actually finding out how information really moves and who really gets consulted, before assuming the new chart will simply inherit it.
Clarity, in this sense, starts with an inventory. Not of roles, but of the invisible work currently keeping the visible structure standing. You cannot protect infrastructure you have not first admitted exists. And an organization that only ever plans around its org chart is planning around half of itself.
