The business is bigger than it was three years ago. It is working harder. The margin is thinner. Input costs are part of the story. They are not all of it.
It usually surfaces around the end of the financial year.
Revenue is up. Sometimes significantly. The business has more customers, more contracts, more work moving through than it did three years ago. By the measure of activity, things are going well.
Then the numbers come back and the margin per dollar of revenue has compressed. Not collapsed — the business is profitable. But the return on all of that additional effort and scale is smaller than it should be. The business is working harder and earning less proportionally.
Input costs get the explanation first. Labour costs have increased. Energy is more expensive. Materials pricing has moved. Freight is up. These are real and they have bitten nearly every manufacturing business in Australia over the past several years.
But input costs don’t explain all of it. And the businesses that address only input costs and don’t examine the structural condition underneath them find the same pattern repeating in the next growth cycle.
What the structure is doing to the margin.
When a business grows without redesigning the architecture that organises the work, the overhead generated by that architecture grows faster than the throughput it enables. This is not a management failure. It is a predictable structural consequence.
Think about what happens when a business roughly doubles in size over five years. The number of decisions that need to be made roughly doubles. The coordination required between teams, shifts, and functions roughly doubles. The volume of exceptions, quality issues, and supplier problems roughly doubles. The management attention required to keep everything running roughly doubles.
But the architecture — the way decisions are made, how authority is distributed, how coordination happens, how problems are resolved — was designed for the smaller, simpler version of the business. It has not been redesigned for the larger, more complex version.
The result is that the additional volume moves through an architecture that generates friction at every point of coordination. Decisions take longer because more people need to be consulted. Quality escapes require more rework because the checking systems were calibrated for a lower volume. Management energy is consumed maintaining the existing architecture rather than developing the business. The owner’s attention — the most finite resource — is spread across a surface area that has doubled.
More work moves through. Less of the revenue from that work reaches the margin. The architecture is consuming what the growth created.
Why the instinctive responses don’t resolve it.
Cut costs. This is the first instinct and it has some validity — there are usually overhead items that grew with the business and can be trimmed. But cutting costs in a structurally inefficient business reduces the overhead without addressing the inefficiency. The next growth cycle recreates it.
Hire someone. Often the right move, but hiring into a structurally inefficient architecture adds cost before it adds throughput. The new person takes time to become effective, and their effectiveness is constrained by the same structural conditions that constrained everyone before them.
Work harder. The owner and the management team put in more hours to push more volume through. This works in the short term and is genuinely damaging in the medium term — it depletes the people and conceals the structural signal that should be prompting a design response.
None of these responses examine the architecture itself. They all assume that the existing structure is approximately correct and needs to be tuned. The structural question asks something different: is the architecture of this business designed for the volume and complexity we are now operating at, or are we running a larger business through a structure that was designed for a smaller one?
What structural capacity design means in practice.
For a manufacturing or production business, this is not a theoretical exercise. It is a practical examination of how work actually flows through the operation — where it slows, where it accumulates, where the architecture generates cost without generating value.
Where do decisions queue? Every decision queue in a business is a structural signal. It marks a point in the architecture where authority has not been adequately designed — where the volume of decisions arriving at a position exceeds the capacity of that position to process them. Often that position is the owner. Sometimes it is a senior manager who has become an informal bottleneck.
Where does coordination break down? In a larger business, the coordination between functions — production and procurement, sales and operations, quality and delivery — requires explicit architecture. The informal coordination that worked when everyone knew each other and could resolve things in a conversation becomes unreliable when the team is larger and the relationships are less dense.
Where is rework hiding? Rework is a margin killer that rarely appears as a line item. It lives in the time spent correcting mistakes, redoing work that didn’t meet specification, resolving customer complaints about quality or delivery. Its structural source is almost always in the gap between the volume of work moving through and the capacity of the checking and correction architecture to keep pace with it.
Addressing these conditions requires examining the design of the business, not just the performance of the people in it. The people are often doing exactly what the architecture asks of them. The architecture is asking them to do things it was not designed to support at the current scale.
The question the numbers are asking.
Margin compression in a growing business is a signal. Not a signal that the business is failing — the business is growing. It is a signal that the architecture has not kept pace with the scale and that the gap between them is generating cost that shows up in the margin before it surfaces anywhere else.
The businesses that address this signal structurally — that examine the design of how work moves through the operation and redesign the architecture to support the current volume — recover their margin and sustain it through the next growth cycle. The ones that address only the surface conditions find the same pattern repeating.
If you doubled revenue tomorrow, would your margin improve — or compress further?
OXXEGENHorizon is a structural advisory practice within the OXXEGEN Group, working with the Hidden Champions of Australian manufacturing and industry.
Direction before the decision.
oxxegenhorizon.com