Imagine a Monday morning in a growing company.
A customer issue has reached the CEO because two functions cannot agree on who should resolve it.
The CEO asks why.
The answer is not that nobody is responsible.
Both functions have responsibilities. Both managers are capable. Both are working hard.
The problem is that the issue sits between their responsibilities.
So the CEO gets involved.
A similar decision is waiting for approval from another senior executive. Another team is coordinating through personal relationships because the formal process is too slow. A manager is escalating something that, a year earlier, would have been resolved directly.
Nothing appears fundamentally broken.
The business is growing.
But the way the organization operates is becoming increasingly difficult to execute through.
That raises a more consequential question:
Has the way the organization operates kept pace with what the organization has become?
When yesterday’s way of operating becomes today’s constraint
An operating model is not simply an organizational chart.
It is reflected in how work is coordinated, how decisions are made, how responsibilities connect, how functions interact, and how execution is managed across the organization.
An organization can therefore change substantially while its operating model remains largely unchanged.
The original model may not have been wrong.
It may have been exactly right for the organization at that time.
A smaller company can often rely on direct communication.
A CEO may be close to most important decisions.
A few experienced people may coordinate across functions informally.
Teams may solve problems through relationships rather than formal mechanisms.
As the organization grows, however, the conditions under which those practices worked can change.
More relationships create more coordination.
More decisions create more pressure on the executive layer.
More products, customers, locations or business lines can create greater interdependence.
What once created speed can begin to create dependence.
What once created flexibility can begin to create inconsistency.
What once allowed leadership to stay close to the business can eventually pull leadership into too many operational decisions.
Growth changes the operating problem
This is why organizational growth should not be understood only as an increase in size.
Growth can change the operating conditions under which the organization has to function.
More business activity can create more interdependence.
More customers can create greater variation in requirements.
More employees can create more coordination needs.
More products or business lines can create competing priorities.
More locations can make informal coordination harder.
More decisions can increase pressure on the executive layer.
The organization may therefore reach a point where the question is no longer simply:
How do we grow further?
It becomes:
Can the way we currently operate support what we have already become?
The operating model may be doing exactly what it was designed to do
There is an important nuance here.
When execution begins to feel difficult, the immediate reaction may be to conclude that the organization needs restructuring.
But that conclusion can be premature.
Sometimes the problem is not that the operating model was badly designed.
It is that the organization has changed while the conditions assumed by that model have not.
A structure that worked when decisions were concentrated among a few people may become difficult when decision volume expands.
A highly centralized model may have been appropriate when leadership needed close control.
Later, the same concentration of decisions may slow execution.
A functionally organized business may have worked when coordination requirements were relatively simple.
As the organization becomes more interconnected, functional boundaries may create additional coordination demands.
The issue, therefore, is not simply:
Is the operating model good or bad?
It is:
Is the operating model still appropriate for the organization we have become?
Where the friction begins to appear
Operating-model limitations rarely announce themselves as an operating-model problem.
They often appear somewhere else.
A decision that should take a day takes a week.
A customer issue moves between several functions before someone owns it.
Executives spend increasing amounts of time resolving matters that should be handled closer to execution.
Teams work hard but depend on one another in ways that are not clearly coordinated.
Different parts of the organization make locally sensible decisions that create problems elsewhere.
People may describe the organization as becoming “more bureaucratic” when the deeper issue is that the existing way of coordinating work no longer matches the organization’s complexity.
These are not necessarily signs that the organization has become badly managed.
They may be signs that the operating model is being asked to support a different organization from the one for which it originally evolved.
The executive problem is fit
This is where the discussion becomes more useful.
The question is not whether every growing organization needs a new structure.
It does not.
Nor is the answer necessarily decentralization, centralization, new reporting lines, additional management layers, or a formal restructuring exercise.
The more fundamental question is fit.
Does the way decisions are made fit the volume and complexity of decisions now required?
Do responsibilities connect clearly enough across functions and business units?
Can teams coordinate without creating unnecessary escalation?
Does the executive layer have enough visibility without becoming the operating bottleneck?
Can the organization maintain accountability while allowing execution to move at the appropriate level?
These are questions about how the organization operates—not simply how it is drawn.
From organizational size to organizational complexity
One of the more important distinctions is that size alone does not determine operating-model pressure.
Two organizations with similar headcount can have very different operating challenges.
One may operate with a relatively simple product, market and delivery model.
Another may manage multiple offerings, customer segments, locations, regulatory requirements and interdependent functions.
The second organization may face substantially greater coordination demands even if the number of employees is similar.
So the executive issue is not simply:
Have we become bigger?
It is:
What has become more complex, more interdependent, or more consequential—and does the way we operate reflect that change?
That is a different way of looking at organizational growth.
What happens when the organization outgrows its way of operating?
The consequences can accumulate gradually.
Senior leaders become involved in more decisions.
Functional boundaries become harder to navigate.
Teams create workarounds.
Informal relationships become increasingly important for getting things done.
Different managers develop different interpretations of responsibility.
Execution becomes dependent on particular individuals.
The organization may continue to perform, but with increasing effort.
And this is where an important executive distinction emerges:
An organization can continue to grow while its operating model becomes increasingly difficult to execute through.
Growth itself therefore does not prove that the operating model is working well.
It may simply mean that the organization has been successful enough to expose limitations that were previously less consequential.
The question is not “Should we restructure?”
This distinction matters because restructuring can become an attractive response to operating friction.
Change the boxes.
Move responsibilities.
Create new functions.
Add management layers.
Centralize something.
Decentralize something else.
Sometimes these changes are necessary.
But if the executive diagnosis begins with restructuring rather than understanding the operating problem, the organization may change its structure without resolving the underlying friction.
The more useful starting point is to understand what has changed in the organization and what that change now requires from the way work is coordinated and decisions are made.
Only then does the question of structural change become more meaningful.
What has the organization become?
When an organization grows, executives naturally look at what has been added:
new customers, people, products, markets, locations or revenue.
But growth can also change the organization qualitatively.
The relationships become different.
The dependencies become different.
The consequences of decisions become different.
The amount of coordination required becomes different.
The executive role itself can change.
And therefore the way the organization operates may need to evolve as well.
Not because the previous operating model was wrong.
But because the organization is no longer the same organization it was when that model emerged.
Executive reflection
The question for an executive team may therefore be less about whether the organization needs restructuring and more about whether its current way of operating still makes sense.
Has the way we make decisions kept pace with the decisions the organization now faces?
Have responsibilities evolved as the organization’s complexity has increased?
Can functions and business units coordinate effectively without excessive escalation?
Are senior executives providing direction—or increasingly compensating for limitations in the way the organization operates?
And ultimately:
Has the way the organization operates kept pace with what the organization has become?
Growth can create new opportunities.
But it can also expose limitations in the operating model that once enabled that growth.
The executive challenge is not to assume that the old way must be replaced.
It is to recognize when the organization has changed enough that the way it operates may need to change with it.