Every company maintains an official version of itself. It’s usually stored in an HR platform, occasionally exported into slides, and presented as a clear, structured map of the organization. Names are placed into boxes, boxes are connected by lines, and those lines establish hierarchy, reporting relationships, and formal ownership. It is designed to answer a straightforward question: who is responsible for what, and who reports to whom.
That representation is useful, but it is incomplete in a way that becomes obvious the moment you look at how work actually happens.
Because work does not move through an organization by following reporting lines. It moves through people, and more specifically, through the relationships, habits, and patterns that form around those people over time. When something needs to get done, especially under pressure or with ambiguity, individuals do not consult the org chart to decide their next step. They rely on a mental map built from experience: who tends to respond quickly, who understands the broader context, who can make a decision without escalating it further, and who is likely to slow things down.
This map is rarely written down, but it is widely shared among those who have spent enough time inside the system. It forms gradually, through repeated interactions. Someone helps unblock a problem once, then again, and eventually becomes the default person others reach out to in similar situations. Another person consistently provides clarity across team boundaries, and over time becomes a reference point, even if their role does not formally require it. These patterns accumulate, and as they do, they create a second layer of structure that sits on top of the official one.
This second layer is not designed. It emerges.
It reflects how decisions are actually shaped, how information circulates, and how dependencies are resolved in practice. It also explains why two people in the same role can have very different levels of influence over outcomes, and why certain individuals become central to the system regardless of their position in the hierarchy. Their importance is not defined by title, but by how frequently the flow of work passes through them.
The difference between these two layers becomes particularly visible in moments of urgency or uncertainty. When a system breaks, a deadline is at risk, or a decision carries significant consequences, the organization does not behave according to its formal diagram. People bypass queues, reach across teams, and involve individuals who are not technically part of the process but are known to be critical to resolving it. These actions are not exceptions; they are a more accurate reflection of how the organization functions under real conditions.
What the org chart captures is accountability. What it misses is dependency.
And dependency is what determines speed.
In many cases, the points where work slows down are not aligned with formal ownership. A team may appear fully staffed and clearly responsible for a given area, yet progress depends on a single individual who holds key context or institutional knowledge. A decision may be assigned to a specific role, but in practice it is shaped by informal input from others whose perspectives carry weight. These dependencies are not visible in the official structure, but they have a direct impact on how efficiently the system operates.
This gap between representation and reality creates challenges that are easy to misdiagnose. When delays occur or coordination breaks down, the instinct is often to adjust the formal structure: redefine roles, move teams, redraw reporting lines. While these changes can improve clarity at the surface level, they do not necessarily address the underlying patterns that govern how work actually flows. The informal network remains intact, and in some cases, becomes even more relied upon as people adapt to the new structure.
Over time, this leads to an organization that looks orderly from the outside but behaves in a far more complex and uneven way internally. Those who understand the informal layer can navigate it effectively, finding the shortest path to action and avoiding unnecessary friction. Those who do not are left following the official map, encountering delays that are difficult to explain and inconsistencies that seem arbitrary.
None of this implies that the formal structure is unnecessary. It provides a foundation for scale, clarity, and accountability that organizations cannot function without. But it is only one part of the system. The other part — the one that determines how work actually gets done — exists in the connections between people, in the accumulation of trust and context, and in the patterns that emerge from repeated collaboration.
Understanding an organization, therefore, requires looking beyond its documented structure and paying attention to its behavior. It means observing where decisions are truly made, how information actually travels, and which relationships consistently influence outcomes. It means recognizing that the official org chart describes how the company is supposed to operate, while the real one is continuously being built through everyday work.
And in practice, it is that real, informal structure that determines whether things move smoothly or get stuck, whether decisions are clear or contested, and whether the organization can respond effectively when it matters.
