Building an operating model that survives growth
The operating model that takes a business from zero to ten million in revenue is almost never the one that will take it to a hundred million. This is not a failure of the original model — it is a feature of growth. The structures, decision processes, and coordination mechanisms that work at one scale break at the next, reliably and predictably. The question is not whether the operating model will need to change, but whether that change is anticipated and designed or reactive and disruptive.
An operating model is a decision architecture
At its most fundamental, an operating model is a system for making decisions: which decisions are made centrally, which are delegated to teams, which require cross-functional coordination, and what information each level of the organisation needs to make decisions well. Everything else — the organisation structure, the process design, the governance mechanisms — follows from these choices.
The answers that work at twenty people break at two hundred. The answer to "who decides the product roadmap?" that worked when the founders sat in the same room does not survive an organisation where product managers in three markets are each making roadmap decisions that affect shared infrastructure. The answers that work at two hundred rarely survive a thousand. The informal coordination that allowed a mid-sized team to operate without explicit process becomes a bottleneck that slows every decision as the team doubles again.
Auditing the decision architecture — mapping where decisions are currently made, where they should be made given the current scale and strategy, and what information each level needs to make them well — is not a reorganisation exercise. It is an infrastructure exercise, and it deserves the same rigour that technology infrastructure decisions receive.
Span of control is a symptom, not the problem
When organisations grow past their operating model, the visible symptom is management overload: spans of control that exceed what any individual can meaningfully supervise, and decisions that queue behind a small number of bottlenecks. The instinctive response — hire more managers — treats the symptom without addressing the cause.
The underlying cause is that accountability is concentrated where it should be distributed, and coordination is required where it should be unnecessary. Every decision that escalates to a senior leader because the team lacks the authority or the information to make it independently is a signal that the decision architecture has not kept pace with growth. Hiring more managers into that structure adds cost; it does not add decision velocity.
The intervention that works is redesigning the authority structure: pushing decision rights down to the level where the relevant information lives, ensuring those teams have the accountability to match the authority, and defining clearly which decisions genuinely require central coordination and which have been escalating by default rather than by design.
Build for the next stage, not the current one
The most effective operating model redesigns are anticipatory. They are designed for the volume, complexity, and geographic distribution of the next stage of growth — not the stage the business is currently in. This requires a clear and honest view of where the business is going: which markets will be added, which product lines will expand, which customer segments will require different service models.
Anticipatory design feels premature when the immediate pressure is to move fast in the current stage. The cost of deferring it is not visible until growth exposes the structural constraints — at which point redesigning the operating model under pressure, while simultaneously managing operational performance, is significantly more expensive than designing it deliberately beforehand.
The businesses that maintain strategic momentum through rapid growth are almost always the ones that invested in operating model design before the constraints became acute. The ones that did not consistently find that the growth they worked to achieve creates internal friction that consumes the momentum they were trying to build.
