Structural outgrowth rarely announces itself. There is no moment when a founder wakes up and thinks: my organization has exceeded the architecture designed to run it. What happens instead is quieter and more persistent. A set of operational patterns emerges — patterns that feel like people problems, communication failures, or management gaps — that are actually structural signals. The company is telling you something in the only language organizations have: friction.
Larry Greiner’s model of organizational growth, first published in the Harvard Business Review in 1972, established that growing companies move through predictable phases — and that each phase ends not with a smooth transition but with a crisis. The crisis is not a failure of leadership. It is a structural mismatch: the organization has grown past the architecture that served it at the previous stage, and the new architecture has not yet been built.
These are the five signals that precede that crisis — the observable patterns that tell you the structure has been outgrown before the wheels come off entirely.
Signal 1 Decisions are taking longer but your team is not getting less capable
When a growing team consistently struggles to make timely decisions, the instinct is to diagnose a capability gap. The team lacks confidence, judgment, or experience. But when the same capable people who once moved quickly are now slow and hesitant, the problem is almost always structural rather than personal.
Decisions slow when authority, information, and accountability no longer move through the organization at the same speed — and the gap between them fills with hesitation, escalation, and delay. The people have not changed. The coordination infrastructure has failed to keep pace with what they are being asked to navigate.
Henry Mintzberg’s work on organizational coordination, developed in The Structuring of Organizations (1979), describes the mechanisms by which organizations align effort: direct supervision, standardization of work processes, standardization of outputs, and mutual adjustment. At small scale, mutual adjustment — people figuring things out informally with one another — is sufficient. As organizations grow, informal coordination degrades and formal mechanisms must take its place. When those mechanisms are not built, decision velocity drops, not because the people have changed, but because the coordination infrastructure is no longer adequate.
If your team is slow to decide, the diagnostic question is not about their confidence. It is about where decision authority lives, how clearly it is defined, and whether the people who should be deciding have the information, permission, and structural backing to do so.
Signal 2 The same conversations keep happening
A recurring meeting, a repeated misunderstanding, or a coordination problem that resurfaces after every resolution is not a communication failure. It is a structural symptom. The conversation keeps happening because the underlying structure has not resolved the condition that generates it.
The pattern is recognizable in almost every founder-led company that has crossed 15 employees: the weekly check-in that exists to re-clarify the same handoff between two functions; the customer escalation path that keeps resurfacing because no one has defined where ownership ends; the billing or scheduling dispute that gets resolved one-on-one and then reappears three weeks later. The incident changes. The structure that produces it does not.
Peter Senge’s concept of systemic archetypes, introduced in The Fifth Discipline (1990), describes patterns in which organizations repeatedly produce the same problem through the same structural dynamic. The fix that relieves pressure temporarily — the conversation, the clarification, the one-off decision — does not address the system that produced the problem in the first place. The problem returns because the structure returns it.
A useful diagnostic: if you have addressed the same coordination problem more than twice in the past six months, stop troubleshooting the incident and examine the structure. What is the repeated conversation actually about? What structural ambiguity or misalignment is generating it? The conversation is a symptom. The structure is the condition.
Signal 3 Your org chart and your workflow are two different maps
Most organizations have a formal reporting structure and an informal operating structure — and in healthy companies at small scale, the gap between them is manageable. As organizations grow, that gap becomes operationally significant. Work gets done through informal networks, workarounds, and undocumented handoffs that the org chart does not represent.
Mintzberg’s distinction between formal structure and what he called the “informal organization” — the actual patterns of interaction and coordination that emerge in practice — is useful here. The informal organization is not inherently a problem. It is how organizations fill the structural gaps that formal design leaves. But when the gap between formal and informal grows large enough, the informal organization begins to carry load it was never designed to bear: accountability, institutional knowledge, coordination between functions.
When the person who actually knows how something works is not the person whose role says they should know, the organization is operating outside its formal structure. When that pattern is consistent and widespread, it is a structural signal: the architecture has not kept pace with how the work actually flows.
Signal 4 New people take much longer to become productive than they used to
Onboarding time is one of the more reliable indicators of structural clarity. In a well-architected organization, new people can learn the role because the role is defined, the processes are documented, and the decision authorities are clear. In an organization that has outgrown its structure, new people learn by observation, by asking questions repeatedly, and by gradually understanding the informal networks that actually govern how work gets done.
Michael Gerber’s argument in The E-Myth Revisited (1995) that businesses should be built on documented systems rather than the tacit knowledge of individuals is not simply an efficiency argument. It is a structural argument. When the knowledge required to do the work lives in people’s heads rather than in defined processes, the organization cannot scale without degrading its operating quality. New people cannot absorb tacit knowledge quickly. They can learn documented systems.
If your onboarding time has grown without a corresponding growth in role complexity, the likely cause is that the structure has not been made explicit. New people are not slower. The architecture is less legible than it used to be.
Signal 5 The founder is still the path of least resistance for most decisions
This is the most common signal and the most frequently misread. When decisions consistently find their way back to the founder — not because they are complex, but because the founder is faster, more certain, or more trusted than the formal process — the organization has not built a decision architecture capable of operating independently.
Greiner’s model describes a crisis of autonomy in which growing organizations must transition from direct founder control to delegated decision-making with appropriate accountability structures. The transition requires more than a willingness to delegate. It requires defining decision authority clearly, building the information flows that allow others to decide well, and creating the governance structures that allow delegation without chaos.
The founder who remains the path of least resistance is not holding on out of ego. In most cases, they are filling a structural gap. The solution is not a mindset shift. It is an architectural one: mapping what decisions need to be made, defining who should make them, and building the structural backing that allows them to do so without routing through the founder.
These five signals are not dramatic. They do not look like a crisis until they accumulate. But each one is organizational data: a measurement of the gap between the structure that exists and the structure the company actually needs.
Operational clarity does not begin with a strategy. It begins with an honest reading of what the friction in your organization is telling you. If two or more of these signals are present in your company right now, the structure deserves a serious examination before the next growth phase makes the gap harder to close.
The Operational Clarity Scorecard™ is one tool for that examination. It surfaces where the structure has held and where it has not — before the friction becomes a crisis.
References
Gerber, M. E. (1995). The E-Myth Revisited: Why Most Small Businesses Don’t Work and What to Do About It. HarperBusiness.
Greiner, L. E. (1972). Evolution and revolution as organizations grow. Harvard Business Review, 50(4), 37–46.
Mintzberg, H. (1979). The Structuring of Organizations. Prentice-Hall.
Senge, P. M. (1990). The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday.
Legacy Line Operations works exclusively with founder-led companies between 10 and 75 employees.
This post is part of the Signals & Symptoms Series — observable patterns that precede operational breakdown in founder-led companies.
legacylineoperations.com