Growth rarely makes a business simpler; more often than not, there is an increase in business complexity.
New customers bring different requirements. New services need supporting processes. More people require clearer roles, communication and oversight. Larger contracts introduce additional risk, governance and reporting. New systems are implemented to provide greater control.
Each decision may be entirely reasonable. Taken together, however, they can leave the organisation carrying far more business complexity than its growth genuinely requires.
Products remain available because somebody might still buy them. Customer exceptions become permanent ways of working. Reports continue long after the original question has disappeared. Additional approval points are introduced after individual problems. Systems overlap because replacing the old one feels harder than accommodating both. Meetings are created to compensate for gaps in ownership or information.
Nothing looks significant enough to challenge on its own.
Yet the combined effect can be substantial. Decisions take longer. Priorities compete for attention. Teams spend more time navigating the organisation and less time creating value. Customers encounter more handovers, caveats and inconsistent answers.
The business has grown, but the operating burden has grown faster.
Business complexity is not the same as capability
Some additional business complexity is an unavoidable consequence of growth.
A larger organisation cannot always rely on the informal conversations, individual memory and personal relationships that worked when it was smaller. Important customers may reasonably expect stronger governance. Regulation, security, financial control and contractual commitments may demand more rigorous processes. Different markets may require genuinely different products or delivery models.
Simplification does not mean pretending those realities do not exist.
The problem begins when leaders assume that every additional layer represents greater capability.
A new process may improve control, but it may also duplicate an existing one. A wider portfolio may create more routes to revenue, while spreading investment and expertise too thinly. More reporting may increase the volume of information without improving understanding. Additional management forums may create the appearance of oversight while slowing the decisions they were meant to support.
Capability helps the business perform better. Complexity merely gives it more to carry.
The two can easily become confused because both usually arrive through visible additions: another person, system, product, control, meeting, report or initiative. The organisation can point to what has been introduced, but may be less clear about the value that has resulted.
How business complexity accumulates without a deliberate decision
Few leadership teams consciously choose to make their business more difficult to run.
Complexity usually accumulates through a series of local decisions made for understandable reasons.
Products and services are added but rarely retired
A business launches a new offer to respond to a market opportunity, customer request or competitor move. The previous offer remains because existing customers still use it, sales may still find an occasional opportunity for it, or nobody wants to risk losing potential revenue.
Over time, the portfolio becomes harder to explain, sell, price, support and improve.
Customers may struggle to understand the difference between similar offers. Sales teams need more knowledge to qualify opportunities correctly. Marketing has more messages to communicate. Delivery teams support a growing number of variations. Product or service development investment becomes fragmented across old and new priorities.
The business appears to offer more, but may be achieving less focus from the resources behind it.
Customer exceptions become the operating model
An important customer needs a different process, commercial term, technical configuration or reporting arrangement. The business agrees because the relationship matters.
One exception is manageable. A growing collection of exceptions is not.
Each may create additional administration, system workarounds, knowledge dependencies and delivery risk. Teams have to remember which customer receives which version of the service. Standard processes stop being standard. New employees learn the documented way of working and then discover the numerous unwritten variations that exist in practice.
The organisation tells itself it is being customer-focused. In reality, it may be relying on operational complexity to compensate for weak choices about what it can consistently and profitably provide.
Controls are added after problems but not reviewed afterwards
When something goes wrong, leaders understandably want to prevent it from happening again.
Another approval is introduced. A new report is requested. An additional checkpoint is added to the process. More people are included in the decision. A meeting is created to improve visibility.
The response may be appropriate at the time. The problem is that temporary controls often become permanent without anyone testing whether they still serve a useful purpose.
As incidents, projects and customer issues accumulate, so do the mechanisms introduced to manage them.
Eventually, the business may have several layers of assurance but remain unclear about where real accountability sits. People become skilled at moving work through the controls rather than using judgement to deliver the right outcome.
Systems overlap and workarounds become normal
A new platform is introduced to improve visibility or automate part of the operation. The old system remains because historical information still sits within it, one team continues to depend on it, or the migration was never fully completed.
Spreadsheets appear between systems. Manual reconciliations compensate for inconsistent data. Teams create local tools because the central platform does not quite meet their needs. Different functions report their own versions of revenue, pipeline, delivery status, capacity or customer risk.
The business has invested in more technology but still relies on people to join the information together.
Technology has not removed complexity. It has digitised parts of it while leaving the underlying fragmentation intact.
Meetings multiply where clarity is missing
Meetings are frequently introduced to improve communication, coordination or control.
They can also become a response to unclear ownership.
A lack of decision-making authority draws more people into the conversation. Unreliable information forces teams to spend time reconciling different versions of reality. Unclear priorities turn meetings into repeated discussions about the same competing demands, while stalled actions often lead to yet another layer of review.
The calendar becomes evidence of organisational activity rather than organisational movement.
The cost is bigger than administrative inconvenience
Business complexity is often tolerated because its cost is dispersed.
There may be no single budget line labelled “unnecessary complexity”. Instead, the cost appears across the organisation:
- Senior attention absorbed by repeated clarification and intervention;
- Employees recreating information that already exists elsewhere;
- Duplicated roles, activities and governance;
- Longer decision and approval cycles;
- Investment spread across too many products or priorities;
- Customer requests moving through multiple teams;
- Experienced people compensating for weak processes;
- Transformation initiatives slowed by legacy commitments;
- Inconsistent delivery and higher cost-to-serve.
McKinsey reported in 2025 that two-thirds of executives considered their organisations overly complex and inefficient. Its work also suggested that cross-cutting management processes such as planning, forecasting and performance reviews can consume between 40 and 65 per cent of management and overhead time in some organisations.
Those activities are not inherently wasteful. Businesses need to plan, forecast and review performance. The question is whether the effort produces better decisions and outcomes, or whether the organisation is repeatedly processing information without changing what happens next.
Complexity becomes a growth barrier when maintaining the existing business consumes the attention and capacity needed to improve it.
Not all business complexity creates equal value
The objective should not be to make every part of the business as simple as possible.
Customers may have genuinely different needs. Products may require specialist expertise. Regulation may demand detailed controls. A complex service may be precisely what the customer values and is willing to pay for.
The useful distinction is between value-creating complexity and tolerated complexity.
Value-creating complexity helps the business meet a meaningful customer need, manage a material risk, create differentiation or operate effectively in its chosen markets.
Tolerated complexity remains because removing it would require effort, challenge an established interest or force the organisation to make an uncomfortable choice.
That difference matters.
A bespoke service for a strategically important customer may be entirely justified. Ten slightly different versions of that service, maintained because nobody has challenged them, may not be.
A rigorous approval process for a high-risk commercial commitment may protect the business. Applying the same process to every routine decision may simply create delay.
A detailed performance report may support important leadership decisions. Producing it because it has always been produced is not the same thing.
Complexity should have to earn its place.
Why subtraction is harder than addition
Adding something usually feels constructive.
- A new product creates possibility.
- A new system promises efficiency.
- A new role provides extra capacity.
- A new report offers visibility.
- A new initiative demonstrates action.
Removal feels different because it makes the trade-off visible.
Stopping a service means accepting that some potential revenue will not be pursued. Removing an approval requires trust that decisions can be made elsewhere. Retiring a report may challenge the person who requested it. Simplifying a customer arrangement may require a difficult commercial conversation. Ending an initiative means admitting that it is no longer important enough to justify continued attention.
The benefits of addition are often described in advance. The benefits of subtraction must usually be proved against something that already exists, has an owner and may still produce some value.
That is why businesses frequently optimise around the edges. They ask teams to work more efficiently, introduce automation or reduce costs, while leaving the underlying portfolio of work untouched.
People are expected to become more productive without the organisation deciding what they should no longer have to do.
Simplification is a strategic discipline, not a cost-cutting exercise
Poorly handled simplification can damage capability.
An indiscriminate cost reduction may remove experienced people while leaving unnecessary work behind. A management-layer review may change reporting lines without improving decision-making. Product cuts made without understanding customer needs may create confusion or drive customers towards competitors.
Real simplification starts with value, not cost.
Boston Consulting Group argues that leaders need to reduce complexity by aligning projects, products, roles and resources with strategic priorities, making the difficult trade-offs at the top rather than passing ambiguity down through the organisation. Removing only the lowest-revenue products rarely changes performance materially. Stronger results come from examining the whole portfolio, understanding customer needs and making deliberate choices about where resources will create the greatest value. The question is not simply, “Where can we cut?”
It is: What complexity is essential to the value we create, and what complexity are we maintaining because we have never made a deliberate decision to remove it?
That produces a very different conversation.
Five questions that expose unnecessary business complexity
Leadership teams do not need to launch a major restructuring exercise every time the business feels heavy. A more useful starting point is to examine where complexity has accumulated and whether it still deserves the resources required to maintain it.
1. What would we not introduce if we were designing the business today?
This question removes the defence of history.
A process, product, report or meeting may once have made sense. That does not mean it remains the best way to operate now.
Starting from today’s customers, strategy, risks and capabilities helps leaders distinguish what is still necessary from what has merely survived.
2. What continues because of habit rather than value?
Some activities are so embedded that nobody remembers why they began.
Teams may continue producing reports that are rarely discussed, attending meetings where few decisions are made, or maintaining services that no longer fit the direction of the business.
The fact that work is familiar does not make it valuable.
3. Where have exceptions quietly become the standard?
Exceptions reveal where the formal operating model no longer reflects reality.
Leaders should look for customer arrangements, pricing decisions, delivery variations, approval routes and manual workarounds that were intended to be unusual but have become common.
The answer may be to standardise the exceptions, redesign the underlying model or stop agreeing to variations the business cannot support well.
4. Which activities create internal work without improving customer or commercial outcomes?
Not every internal activity needs to be directly visible to the customer. Good governance, compliance, financial control and capability development all matter.
However, the organisation should be able to explain what risk is reduced, decision is improved or outcome is enabled by the work.
When that connection cannot be made, the activity deserves closer examination.
5. What must stop to give our stated priorities enough capacity to succeed?
Businesses often claim to have a small number of strategic priorities while continuing to resource everything that came before them.
A priority without a corresponding stop decision is usually an addition to the workload rather than a genuine choice.
This may be the most important subtraction question of all. What the organisation stops reveals how seriously it takes what it says matters most.
Building subtraction into the growth model
Complexity management cannot be a one-off clean-up.
Without a deliberate discipline, products, processes, systems and governance will begin accumulating again as soon as the immediate simplification exercise ends.
Growing businesses can reduce that risk by building challenge into the way additions are approved and reviewed:
- New products and services should have clear success measures and retirement criteria.
- Customer exceptions should have named owners, commercial justification and review dates.
- Reports and meetings should be periodically tested against the decisions they improve.
- New systems should include credible plans for migration, integration and decommissioning.
- Strategic priorities should be accompanied by explicit decisions about what will stop or receive less attention.
- Temporary controls should not become permanent without review.
- Complexity should be assessed across the whole business rather than transferred from one function to another.
That final point matters.
A process may be simplified for sales while creating more work for delivery. A product range may be expanded to increase customer choice while adding disproportionate operational cost. Automation may save time in one team while generating additional checking and reconciliation elsewhere.
Local simplification can create organisational complexity when the wider consequences are ignored.
The test is whether the business becomes easier to understand, operate, change and buy from as a whole.
Growth requires the discipline to remove
Growth will always introduce some complexity. A business serving more customers, employing more people and operating across more products or markets cannot remain exactly as simple as it was when it began.
The aim is not to resist every addition.
It is to prevent yesterday’s reasonable decisions from becoming tomorrow’s permanent burden.
Leaders need to recognise when capability has genuinely increased and when the organisation has simply added more work, more variation and more coordination. They need to protect the complexity that customers value and risks require, while challenging the complexity that consumes attention without strengthening outcomes.
That requires judgement and, occasionally, courage.
Adding another initiative may feel safer than ending an existing one. Introducing another process may feel more responsible than removing an unnecessary control. Keeping every product, customer variation and legacy commitment may appear commercially cautious.
Yet a business that refuses to subtract eventually loses its capacity to add anything well.
Growth is not only a test of what an organisation can build.
It is also a test of what its leaders are prepared to simplify, stop and leave behind.
If your business is growing but everyday work is becoming heavier, slower or more fragmented, Oak Consult can help you identify where complexity is supporting value and where it has become a barrier to progress.