Growth is one of the clearest signs that an organization is doing something right. More customers, more employees, new markets, additional products, larger teams and more ambitious programmes all suggest that an organization is moving forward. Yet growth brings another, less celebrated consequence: complexity.
What worked when an organization was smaller can become increasingly difficult to sustain as it expands. A leadership structure that once allowed decisions to be made quickly may become a bottleneck. Informal ways of working that relied on a small group of people knowing how everything gets done may become unreliable. Processes introduced to create consistency may multiply until employees spend more time navigating the organization than delivering for it.
This is often the point at which leaders begin to ask whether the organization needs to be redesigned.
Importantly, organizational redesign is not necessarily an indication that something has gone wrong. In many cases, it is a natural response to growth. The organization has changed, but the way it is organized has not changed at the same pace.
The more useful question, therefore, is not simply whether an organization has grown. It is whether the way work is organized still supports what the organization is trying to achieve.
Read also: Growth multipliers: How micro-decisions affect scaling outcomes
Consider what happens when an organization expands from a relatively small team into a larger, more specialized operation. New departments are created, management layers are introduced, responsibilities are distributed across teams and additional controls are put in place. Each decision may be entirely reasonable on its own. But over time, the interaction between these decisions can produce friction.
A client issue that once required one conversation may now require input from several departments. A decision that could previously be made by a manager may now require multiple approvals. Employees may become uncertain about who owns a particular responsibility. Information may sit in different systems or within different teams. Meetings increase because coordination becomes harder. Leaders find themselves involved in operational matters that should have been resolved elsewhere.
The organization has more people and more capabilities, but it may also be becoming slower.
This is one of the paradoxes of growth: an organization can become more capable while becoming less agile.
Decision-making is often one of the first areas where this becomes apparent. As organizations grow, authority does not always grow with responsibility. Senior leaders can gradually become the default decision-makers for an increasing number of issues, while managers and teams wait for approval before acting. The result is a leadership team that is overloaded and an organization that becomes dependent on escalation.
The problem is not necessarily that there are too many decisions. It may be that decisions are being made at the wrong level.
The same applies to functional specialization. Growth often requires organizations to develop expertise in areas such as finance, human resources, technology, marketing, risk, procurement and sustainability. These functions are important, but specialization can also create silos. Each team may become focused on its own objectives while the organization struggles to manage the connections between them.
Marketing may focus on generating leads, sales on conversion, operations on delivery and finance on cost control. Each function can perform well according to its own measures while the overall customer experience becomes fragmented.
This is where organizational design becomes more than an exercise in changing reporting lines. The real question is how work moves across the organization and whether people have the authority, information, systems and capabilities required to deliver outcomes collectively.
Role ambiguity is another strong signal. As organizations evolve, responsibilities often accumulate faster than structures and job descriptions are updated. A manager who originally oversaw one area may gradually take responsibility for several others. Two departments may both believe they own the same process, while another critical activity falls between teams because nobody has clear accountability for it.
When people repeatedly have to ask, “Who owns this?”, the issue may not be individual performance. It may be a structural problem.
Processes can create similar challenges. As organizations become more complex, additional controls and approvals are often introduced for good reasons. But controls can accumulate without being reviewed. A process that originally required two steps can gradually require six. Reports can continue to be produced long after their original purpose has disappeared. Meetings can multiply because teams need to coordinate activities that were once naturally connected.
Eventually, the organization may find itself spending considerable energy managing its own machinery.
That does not mean complexity itself is undesirable. A large organization operating across multiple markets will naturally require more coordination than a small organization. A regulated institution will require controls that would be unnecessary in a smaller business. The objective of redesign is therefore not to eliminate complexity altogether.
It is to distinguish between complexity that the organization genuinely needs and complexity that has accumulated without creating corresponding value.
This distinction is particularly important when an organization’s strategy changes. An organization may decide to enter new markets, introduce new products, serve different customer segments or pursue a more ambitious growth strategy. Yet its structure, processes and decision-making mechanisms may still reflect the organization it was several years earlier.
The strategy has moved forward.
The organization has not.
A meaningful redesign begins by examining how value is created and how work actually happens. It asks where decisions are made, where they should be made, where processes slow down, where accountability is unclear, where information gets lost and where teams depend unnecessarily on one another.
It also asks whether the organization’s systems support the behaviours and processes that leadership expects from its people.
These questions can reveal that the solution is not always a major restructuring. Sometimes the organization needs clearer decision rights. Sometimes it needs to simplify processes, strengthen cross-functional collaboration or clarify accountability. In other cases, it may need to rethink the operating model itself.
The important point is that organizational redesign should respond to the organization’s actual needs rather than becoming a reaction to isolated frustrations.
There is also value in recognizing these signals before performance deteriorates significantly. Organizations often wait until growth has created serious operational problems before reconsidering their design. By then, inefficiencies may be deeply embedded, employees may be frustrated, customers may already be experiencing the consequences and leaders may be forced to redesign under pressure.
A more proactive approach treats organizational design as something that should evolve alongside the organization.
As strategy changes, capabilities change. As capabilities change, processes change. As processes change, structures and systems may need to change with them.
The strongest organizations understand that there is no single organizational design that remains effective forever. What is fit for purpose at one stage of growth may become a constraint at another.
The real question leaders should therefore keep asking is simple: is the way we are organized still fit for the organization we are becoming?
If decisions are increasingly slow, accountability is unclear, teams are operating in silos, processes are becoming unnecessarily complicated, leaders are overloaded with operational decisions or strategic priorities are becoming difficult to execute, growth may be exposing the limits of the current design.
That does not necessarily mean the organization is broken.
It may simply mean that the organization has outgrown the way it used to work.
And recognizing that distinction matters. Organizational redesign should not be viewed only as a corrective measure for organizations in difficulty. It can also be a strategic tool for organizations preparing for their next stage of growth.
Because growth should increase an organization’s capacity to create value, not the amount of effort required to coordinate itself.
The organizations that navigate growth effectively are not those that avoid structure or complexity altogether. They are those that continuously examine whether their strategy, structure, systems, people and processes are working together—and are willing to redesign when they are no longer aligned.