Growth is often viewed as a capacity challenge.
More customers require more people, more demand requires more equipment, more volume requires more resource. And organisations invest accordingly, hiring, upgrading, expanding. But capacity is rarely what prevents organisations from scaling successfully.
The real challenge is complexity.
Every Organisation Has a Complexity Threshold
At low volume, informal systems work. Decisions get made quickly because the right person is in the room. Problems get solved because the person who spots them has the authority to fix them. The system functions because proximity compensates for the gaps.
Growth changes that.
As volume increases, the informal networks that kept things moving begin to stretch. The leader who used to know everything happening on the floor now gets filtered information. The team that once flagged problems instinctively now waits to be asked. What felt like a well-run operation starts to show the cracks, ot dramatically, but in the accumulation of small delays, recurring issues, and decisions that should have been made three levels down but somehow still land at the top.
“Growth doesn’t create operational weaknesses. It reveals them. Putting pressure on any system, demanding higher or faster outputs, exposes bottlenecks, weak links, and error-prone activities.”
James Cuthbert, MD, Henkan
Part of what makes this threshold difficult to navigate is that the instinct in the moment is usually wrong. When complexity increases, leaders tend to reach for more structure, more process, and more technology. The solutions that worked before.
But the challenges that come with scale are often a different kind of problem entirely.
A complicated problem has a right answer, but a complex problem doesn’t. It requires experimentation: trying things at smaller scale, sensing what works, and adapting. Applying a complicated solution to a complex challenge tends to add more weight to a system that’s already struggling to hold.
The signs of an organisation approaching its complexity threshold are usually consistent across sectors: decisions are slow, the same problems recur week after week, leaders become the default bottleneck for things that shouldn’t need them, and communication starts to require effort it didn’t before.
The question isn’t whether that point will arrive. It’s whether the organisation has built what it needs to get through it.
The Three Capabilities That Allow Organisations to Scale
Three capabilities determine whether an organisation gets through that point, or gets stuck at it.
1. Visibility
Can leaders see what matters quickly enough to act?
When organisations are small, the answer to this question is almost always yes, because leaders are physically close to the work. As they scale, that proximity disappears and is rarely replaced by anything deliberate. Leaders start relying on instinct, lag indicators, and the version of events that makes it up through the hierarchy.
By the time a problem reaches them, it has typically compounded. Decisions get made on incomplete information. Problems get addressed reactively rather than preventively. The same data gets debated rather than used. Most organisations never replace what that proximity gave them.
The organisations that scale successfully replace proximity with something deliberate: structured visibility. That means KPI cascades that connect shop floor performance to strategic priorities, daily management rhythms that surface problems at the right level, escalation pathways that distinguish between issues that need immediate action and ones that need longer-term resolution, and visual management that makes performance legible at a glance.
For example, when Henkan worked with Armacell across 23 plants in 16 countries, one of the first priorities was building a daily control system that gave leaders real-time visibility rather than lagging indicators. Problem-solving shifted from quarterly reviews to immediate intervention. Equipment breakdowns reduced to zero in key areas. The operation didn’t just get more efficient, it became one that leaders could actually see and respond to as volume increased.
A useful test: take any significant operational problem from the last three months and trace when leadership first became aware of it. If the gap between the problem emerging and leadership knowing about it was more than 48 hours, you have a visibility gap. Not a people problem, but a system problem.
“Having data driven business rules around metric reporting and corrective action is a good way to automate responses. If your performance reports are unwieldy, complex and don’t tell you the ‘So What’, then they need streamlining and simplifying.”
James Cuthbert, MD Henkan
2. Structured Problem-Solving
Can the organisation solve problems permanently?
Most operational organisations are competent at managing problems. The issue is that managing a problem and eliminating it are fundamentally different activities. Managing means containing the symptoms well enough to keep production running. Eliminating means understanding root cause well enough to prevent recurrence.
Organisations that scale successfully build the discipline to distinguish between the two, and invest in the second.
Structured problem-solving methods, such as A3 thinking, 5 Why analysis, or more formal root cause frameworks, ensure that when a problem surfaces, the response isn’t just “fix it and move on” but “understand why it happened and make sure it can’t happen again.”
The difference in outcome is compounding. An organisation that manages problems accumulates them. The same issues resurface at every new volume level, taking up the same bandwidth, requiring the same workarounds. An organisation that eliminates problems gets progressively lighter as it scales, because each root cause removal reduces the ongoing drag on the system.
Working with GKN Aerospace, Henkan implemented a structured TPM asset care programme focused on building exactly this capability. The results were significant: an 88% reduction in equipment breakdowns and a 500% increase in Mean Time Between Failures. The shift wasn’t just technical, it was a change in how the organisation approached problems, from managing failure to eliminating it. That shift started with a model area: a focused pilot where new methods were proven at small scale before being deployed more widely. When leaders could see evidence that the approach worked, commitment followed, and the organisation moved from one that managed failure to one that eliminated it.
“This is not simply a matter of method. It requires a shift in culture: from an environment where speed of resolution is the measure of success to one where permanence of resolution is.”
James Cuthbert, MD Henkan
That shift is what determines whether an organisation can genuinely answer yes to the question: Can the organisation solve problems permanently?
3. Capability Building
Can the organisation improve itself?
Most organisations, when they think about capability, think about training. They send people on courses, bring in specialists, run workshops. The knowledge enters the organisation and then, gradually, dissipates because it was never anchored to the way work actually gets done.
Real capability building is different. It’s about ensuring that the skills, standards, and improvement disciplines required to run and improve the operation are embedded in the people doing the work, not held by a specialist team, not dependent on who happens to have been on the right programme, and not sitting in a consultant’s toolkit that leaves when the engagement ends.
That requires being deliberate about three things.
First, where capability is concentrated. Every operation has people who carry disproportionate knowledge. The team leader who knows every quirk of the line, the maintenance technician who can diagnose a fault in minutes, the manager who holds the institutional memory of why certain decisions were made. When those individuals are present, the operation performs. When they’re not, it struggles. Scaling requires moving critical knowledge out of individuals and into the system: through standard work documentation that captures how things should be done, skill matrices that make capability gaps visible, and cross-training programmes that deliberately spread knowledge across teams. The goal is an operation that performs consistently regardless of who is in the building.
Second, how improvement capability is transferred. The ability to solve problems is a learnable one. Organisations that scale successfully build this capability at every level, from frontline operators who can identify and flag abnormalities, to team leaders who can facilitate a daily improvement discussion, to managers who can coach rather than just direct. This isn’t about creating a pool of CI specialists. It’s about making structured improvement a normal part of how work gets done at every level.
Third, the discipline to protect it. Capability built through a programme can be quietly eroded by operational pressure. When volume increases and the temptation is to deprioritise development activity, the organisations that hold their capability gains are the ones with structures that protect them Leader Standard Work that ensures leaders spend defined time coaching and developing, not just directing; improvement routines embedded in daily and weekly rhythms, not treated as optional; and performance systems that make capability development visible alongside operational metrics.
Henkan’s work with Heineken illustrates what happens when this is built properly. The challenge wasn’t simply deploying TPM to more sites, it was ensuring that each new site could sustain and improve its own performance without depending on central expertise being flown in. The answer was standardised training, structured knowledge transfer, and locally embedded coaches who could develop others. The programme scaled from 28 to over 180 breweries worldwide by scaling the capability within the organisation itself. Each new site inherited a system it could own and run.
The measure of success isn’t whether the operation improved while the support was in place. It’s whether it keeps improving after it leaves.
How to Know If You’re Ready for the Next Stage of Growth
Before the next volume increase arrives, the honest question isn’t whether the ambition is there. It’s whether the system underneath it is ready. If you’re not sure, these questions tend to surface the answer:
- Could the operation sustain current performance if your most experienced manager was unavailable for a week? If the answer is no, or you’re uncertain, that knowledge is concentrated in individuals, not in the system.
- When a problem recurs, does the response address the symptom or the root cause? If the same issue appears in three consecutive reviews without a structural fix, it is being managed, not resolved?
- As volume has increased, has performance improved, stayed flat, or deteriorated? The trend is more informative than the number.
- Are your leaders spending more time this quarter improving how work gets done, or working around the limitations of how it currently gets done?
- Is there a daily rhythm in the operation through which problems are surfaced, reviewed, and escalated at the right level, or does problem identification still depend on who happens to notice?
- Ask three members of your leadership team what the top operational priority is this quarter. If you get three different answers, alignment has already started to drift in ways the plan can’t see.
Most leadership teams can answer these honestly within a single conversation.
The uncomfortable ones, where the answer is clearly no, are rarely surprises. They are the problems already present, waiting for the next volume increase to make them unavoidable.
The Organisations That Scale Successfully Build the System First
Scaling often fails because complexity grows faster than capability. But the organisations that scale successfully are the ones that deliberately build the visibility, problem-solving, and capability required to absorb complexity as they grow, before growth demands it.
They treat these not as improvement initiatives to run alongside the business, but as the operational foundations the business runs on.
If the challenges in this piece feel familiar, Henkan works with operational leaders to build the visibility, problem-solving capability, and organisational foundations needed to scale sustainably.
If you’d like to explore what that could look like in your organisation, get in touch.
