Most founder-led companies have an org chart. It lives in a Google Drive folder, gets updated when someone new is hired, and occasionally surfaces in an investor deck. It shows who reports to whom. It shows titles. It shows structure.
What it does not show is how the company actually works.
That gap — between the structure on paper and the structure in practice — is not a cosmetic problem. It is the source of most operational friction in growing companies. And until a founder can see both maps clearly, they are making decisions about a company that exists only on paper.
Three structures, not one
Niels Pflaeging, in Organize for Complexity, identifies not one but three distinct organizational structures operating simultaneously in every company. The formal structure — the org chart — facilitates compliance. The informal structure represents the realm of influence between individuals. And the value creation structure describes how work actually gets done, based on interpersonal and inter-team reputation and coordination.
Most founders know their formal structure well. They designed it. What they rarely map — and what actually determines how decisions get made, how work moves, and where it stalls — is the value creation structure. That is the workflow. And in most founder-led companies between 10 and 75 employees, that structure was never formally designed. It evolved. It lives in habits, workarounds, and the institutional memory of a handful of people who have been there long enough to know how things actually get done.
What the org chart cannot show
The org chart was never designed to capture coordination. It captures authority — who has it, who reports to whom, where formal accountability sits. That is useful information. But it is not operational information.
Karl Weick's foundational work on organizational sensemaking makes a distinction that matters here. Organizations do not simply execute pre-designed structures — they enact them. People construct the organization through their actual patterns of behavior, communication, and coordination. What gets enacted over time becomes the real structure, regardless of what the formal chart says. The org chart describes an intention. The workflow describes an enactment.
This is why reorganizations so frequently fail to change anything. The boxes move. The reporting lines shift. And two months later the same decisions are routing to the same people, the same work is stalling at the same points, and the same three individuals are carrying the coordination load for the entire organization. The enactment did not change because the underlying structure — the real one — was never redesigned.
The Galbraith distinction that most founders miss
Jay Galbraith's Star Model draws a critical distinction between vertical and horizontal processes. Vertical processes deal with allocating authority, funds, and talent — budgeting, planning, performance management. Horizontal processes are designed around workflow and are carried out through lateral coordination across the organization.
The org chart governs vertical processes. It tells you who has authority, who allocates resources, who reports to whom. But the actual work — client delivery, project execution, decision-making in real time — moves horizontally. It crosses the boxes on the org chart rather than flowing cleanly between them.
Galbraith's critical insight, documented across decades of organizational design research, is that structure is necessary but insufficient. The single most overlooked design element in growing organizations is lateral processes — the formal and informal mechanisms that coordinate work across structural boundaries. In founder-led companies, those lateral mechanisms are almost always informal. They work through relationships, through institutional memory, through whoever picks up the phone fastest. That is functional when a company is small and everyone can hold the operational map in their head. It becomes a structural liability the moment complexity outpaces the capacity of any single person to carry it.
What it looks like on the ground
Here is how this plays out in practice. A service company with 18 employees has a capable project coordinator and a documented intake process. A client submits a non-standard request — scope that sits between two service categories. The coordinator, unsure which service lead owns the decision, sends a message to both. One responds. The other is in the field. The client follows up directly with the founder, who clarifies the scope, assigns the work, and moves on. The next week, a similar request comes in. The coordinator skips the service leads and messages the founder directly. Within 60 days, non-standard requests — which represent roughly a third of incoming work — are all routing to the founder by default.
No one decided this should happen. There was no policy change, no restructuring, no deliberate shift in authority. What happened is that the workflow found the path of least resistance, and that path ran through the founder. The org chart still shows the coordinator and the service leads as the operational owners of intake. The workflow tells a different story entirely.
The problem in that company was not a communication failure. It was not a performance issue. It was a structural gap: the decision boundary between standard and non-standard scope had never been formally defined. Without that boundary, coordination collapsed to the person with the most context — the founder — every time ambiguity appeared.
What the workflow reveals
When I map the actual workflow of a founder-led company — not the org chart, but the real sequence of how work initiates, moves, gets decided, and gets delivered — three things almost always become visible that were invisible before.
The first is where decisions are actually made. Not where the org chart says they should be made, but where they land in practice. In most companies at this stage, that answer is: with the founder, far more often than anyone intended.
The second is where work stops. Every organization has points of accumulation — inboxes, approval queues, handoffs that require a specific person's involvement before anything can move forward. These are not random. They follow a pattern, and that pattern tells you something precise about which structural elements are missing.
The third is who the real coordinators are. In most founder-led companies, one or two people carry a disproportionate share of the organizational knowledge — the informal map of how things actually work, who to call, what decisions require escalation, what can move without approval. These people are often not in formal leadership roles. Their value to the organization is real and significant. It is also invisible, undocumented, and completely non-transferable if they leave.
Why this matters before anything else
Operational improvement efforts — process documentation, new tools, restructuring, delegation initiatives — almost universally fail when they are applied to the formal structure rather than the real one. You cannot optimize a workflow you have not mapped. You cannot delegate authority into a structure that was never designed to hold it. You cannot build systems on top of informal coordination patterns that no one has made explicit.
Mintzberg defined organizational structure as the sum total of the ways in which an organization divides its labor into distinct tasks and then achieves coordination among them. That definition is precise and important. Coordination is the operative word. The org chart handles division of labor. It says almost nothing about coordination. And coordination is where the work either flows or stalls — where organizational friction either accumulates or dissolves.
The org chart is a wish — a picture of how authority should be distributed. The workflow is the truth — a picture of how coordination actually happens. Before you can fix the second, you have to be able to see it clearly.
Most founder-led companies have never formally mapped the workflow that actually runs the business. Until they do, operational friction remains invisible — a felt experience without a structural address. Operational clarity begins not with optimization or reorganization but with diagnosis: a rigorous look at the structure that already exists, so that what gets built next is designed for the company as it actually operates, not the one that appears on the org chart.
That is where this work starts.
References
Mintzberg, H. (1979). The Structuring of Organizations. Prentice-Hall.
Galbraith, J. R. (1993). Competing with Flexible Lateral Organizations. Addison-Wesley.
Gerber, M. E. (1995). The E-Myth Revisited. Harper Business.
Pflaeging, N. (2014). Organize for Complexity. BetaCodex Publishing.
Weick, K. E. (1995). Sensemaking in Organizations. Sage Publications.
Legacy Line Operations works exclusively with founder-led companies between 10 and 75 employees. This post is part of the Decision Anatomy series — a running examination of how decisions actually move inside growing organizations. legacylineoperations.com