The symptoms of an organization growing faster than its structure

When an organization grows faster than its structure, it sends out fairly recognizable signals: decisions slow down, roles blur, priorities scatter, and a few people end up overloaded. These symptoms don't reflect a flaw in the individuals. They show that the coordination mode in place is no longer sized for the level of complexity reached.

Learning to read them is useful, because they often appear before the numbers deteriorate. Treating them as people problems leads to ineffective, even counterproductive, fixes. Treating them as signals of the system opens the right question: what, in the organization, needs to become more explicit? The broader logic is laid out in Structuring your company to stay agile.

Why symptoms arrive in steps

Organizational difficulties don't rise steadily. They trip at thresholds, because every mode of coordination has a range in which it works. As long as you stay inside that range, everything feels smooth. The moment you leave it, the same practices start producing friction.

This explains a common experience: nothing seemed to justify changing anything, and then everything started seizing up within a few months, without any single decision being the cause. It isn't an event that broke the organization, it's a threshold that was crossed. The symptoms that follow are the concrete ways that crossing shows itself.

Decision symptoms

The most visible signal has to do with decisions. They move up. Trade-offs that could be settled at their own level end up systematically on the desk of the founder or a small group of leaders. The gap between the moment a question arises and the moment it is settled stretches out, and people get into the habit of waiting for a sign-off rather than moving forward.

This bottleneck keeps up the illusion of control for a long time. In reality, it makes the organization dependent on the availability of a few people and curbs everyone's ability to act. When everything has to pass through a single point, that point becomes both the guardian of coherence and the main cause of slowness.

Clarity symptoms

A second set of signals touches the clarity of roles. No one knows exactly who decides what anymore. Two teams work on the same topic without realizing it, or conversely an important topic has no identified owner and advances in fits and starts. Gray areas multiply at the borders between functions, where scopes don't quite overlap.

This fuzziness doesn't come from bad faith. It comes from the fact that roles were defined, implicitly, for a smaller organization, and have not been revised since. The work has evolved, the scopes have not, and the gap between the two is paid in duplication, oversights, and recurring discussions about turf.

Execution symptoms

Then comes the erosion of execution. Priorities scatter: you start many things, you finish fewer, and attention spreads across topics that are not all decisive. Deadlines slip, not for lack of work, but because coordination between contributions becomes the real limiting factor.

Quality suffers in turn. It isn't that people work less well, it's that the work crosses more interfaces, and every poorly managed interface introduces a loss. An organization can look very busy while producing fewer net results than before, simply because its energy goes into articulation rather than progress.

Human symptoms

The last group of signals is human, and it is often the most telling. Managers tire out, because they compensate for the lack of structure with their constant presence and arbitration. Certain people become so indispensable that their absence blocks everything, which reveals less about their value than about the organization's excessive dependence on a few individuals. And that relay carries a lot of weight: Gallup estimates that managers alone account for about 70% of the variation in engagement between teams, so a management layer worn down by a system that makes it compensate for missing structure doesn't wear out alone; it drags the engagement of its whole team along with it.

You also see a diffuse weariness set in: the feeling of reprocessing the same questions over and over, re-explaining the same priorities, chasing a coordination that doesn't hold by itself. This isn't a motivation problem, it's the predictable effect of a system that asks people to make up in energy for what the structure should be holding.

Reading the symptoms without blaming managers

The trap, faced with these signals, is to look for someone to blame. You suspect a lack of rigor, a failing team, an overwhelmed leader. That reading is almost always unfair and rarely useful, because it goes after people where the problem lies in the arrangement. The difficulties come from the system, not the individuals, and individuals generally do their best within the constraints they are left with.

The right response is to translate each symptom into a question of structure. A decision bottleneck questions how responsibilities are distributed. Priorities that scatter question the mechanisms of focus. Management fatigue questions the rhythm and the relays. Read this way, the symptoms stop being reproaches and become a fairly precise map of what needs to be made explicit.

These signals are the visible face of a deeper mechanism, the one by which growth produces complexity.

Depending on the dominant symptom, two projects most often come first: clarifying responsibilities, and putting in place an operating cadence that keeps alignment alive without depending on managers being constantly present.