Scott Foster · Shape Executive · M&A, Integration & Scale
The most dangerous thing in a business is often the thing you want to remove.
The Wall Everyone Wants To Remove
Anyone can walk through an old house and identify a wall they would like removed.
Open-plan living looks better.
The space feels larger.
The flow improves.
The house feels more modern.
The wall appears unnecessary.
An inexperienced renovator sees a wall.
An experienced builder sees a load path.
Before a single tool comes out, they want to understand what the wall is carrying.
Because removing the wall is often the easy part.
Understanding the consequences is harder.
The wall may not simply be dividing two rooms.
It may be carrying the roof.
It may be part of a truss structure transferring load elsewhere in the building.
It may be supporting something that is not immediately visible.
From the outside, most people see the pitched roof.
Very few understand the truss structure underneath it.
The roof is visible.
The load path is not.
Businesses are remarkably similar.
The Mistake Many Businesses Make
Investors, founders, advisers, boards and management teams are constantly identifying things they would like to remove.
Management layers.
Founder involvement.
Inventory buffers.
Approval processes.
Reporting routines.
Manual interventions.
Long-standing workarounds.
On the surface, many of these things appear inefficient.
And often they are.
But some inefficiencies exist for the same reason a load-bearing wall exists.
Not because somebody wanted it there.
Because something above it still needs support.
The Load-Bearing Inefficiency Principle
Most people can identify a pitched roof.
Far fewer understand the truss structure underneath it.
Businesses behave in much the same way.
What appears to be founder dependency may actually be compensating for capability gaps elsewhere in the organisation.
What appears to be excess inventory may be protecting customers from unreliable forecasting.
What appears to be unnecessary process may be preventing expensive mistakes from occurring every day.
What appears to be manual intervention may be compensating for systems that are not yet capable of delivering the required outcome.
The inefficiency is visible.
The load path is not.
That is why some inefficiency is load-bearing.
What Strong Operators See Differently
In my experience, this is where many businesses are misunderstood.
I have seen founders carrying pricing governance because nobody else truly understood the commercial architecture.
I have seen inventory carrying forecasting weakness because demand planning capability had never been properly developed.
I have seen customer service teams manually correcting errors every day because broken order-to-cash processes had become accepted as normal.
I have seen warehouse supervisors carrying years of undocumented operational knowledge because the business had never captured it anywhere else.
I have seen management layers criticised as bureaucracy when they were actually compensating for capability gaps lower in the organisation.
I have seen businesses reduce inventory only to discover that inventory had been compensating for poor supplier performance and weak forecasting discipline.
I have seen founders step back before accountability had been transferred into the organisation, leaving teams with responsibility but no decision-making confidence.
I have seen businesses flatten structures, remove management layers and reduce cost, only to discover six months later that decision quality had deteriorated and execution had slowed.
On paper, every one of these looked inefficient.
In reality, they were carrying load.
The Problem With Removing The Wall
Many transformation programs, restructures and post-acquisition value creation plans focus heavily on removing the wall.
Very little time is spent understanding what the wall is actually holding up.
The intended benefits are easy to model.
Lower costs.
Simpler structures.
Reduced working capital.
Improved accountability.
Greater efficiency.
The unintended consequences are harder to see.
Service levels deteriorate.
Decision quality falls.
Customers become frustrated.
Execution becomes inconsistent.
Key people become overwhelmed.
The business starts to wobble.
Not because the wall should have remained forever.
But because nothing had been built to carry the load once it was removed.
The damage rarely appears where the change was made.
It appears where the load transfers.
Just as a ceiling may crack in a different room after a structural wall is removed, businesses often experience consequences somewhere completely different from where the original change occurred.
The First 90 Days
This is one of the reasons the first 90 days after an acquisition are often misunderstood.
There is usually pressure to demonstrate progress.
Pressure to execute the investment thesis.
Pressure to realise synergies.
Pressure to create momentum.
All understandable.
But an experienced builder does not buy an old house on Friday and start removing walls on Monday.
They spend time understanding the structure.
What has been built.
What has been modified.
What is carrying load.
Where the risks sit.
What unintended consequences may emerge if changes are made too quickly.
Experienced operators approach businesses in exactly the same way.
The first 90 days should not be dominated by demolition.
They should be dominated by observation.
Listening.
Learning.
Understanding.
Identifying risk.
Testing assumptions.
Mapping dependencies.
Understanding where operational load is actually being carried.
Because the business that was acquired is rarely the business described in the investment memorandum.
This is not an argument for moving slowly.
It is an argument for understanding first.
Once the load path is understood, operators should move decisively.
The objective is not to preserve inefficiency.
The objective is to transfer the load before removing what carries it.
That distinction matters.
The Operator's Question
Experienced operators do not start by asking:
“How do we remove this?”
They start by asking:
“What is it carrying?”
Because every inefficiency is solving a problem.
The real question is whether the underlying problem has also been solved.
If founder involvement is carrying the load, what capability will replace it?
If inventory is carrying the load, what forecasting discipline will replace it?
If management oversight is carrying the load, what governance structure will replace it?
If manual intervention is carrying the load, what process or system capability will replace it?
The load never disappears.
It simply transfers.
The best value creation programs understand this.
The objective is not to remove cost.
The objective is to remove dependency.
Cost reduction is often the outcome.
Load transfer is the mechanism.
Final Thought
Move too quickly and the ceiling plaster starts to crack.
Move too slowly and the value of the house never increases.
The best builders understand this.
The best operators do too.
Most people see the wall.
The best operators see what it is holding up.