Most leaders believe growth is a reward like more customers, more staff, bigger budgets and louder visibility. In boardrooms, growth is treated like a moral good where questioning it sounds timid, even irresponsible.
That belief is quietly breaking organizations. In my work across banks, regulators, utilities, and fast-growing technology firms, I have learned that growth is not a prize but a stress test.
And most organizations fail it not because they lack ambition, but because they misunderstand what growth actually does.
A farmer once told me that a banana plant that grows too fast produces weak fruit. The stem looks impressive, the leaves are wide, but the bunch bends and snaps before harvest. Experienced farmers slow the growth, prune early, and strengthen the stem. Only then do they allow the plant to carry weight. Organizations are no different.
Executives often measure growth by what can be seen, like headcounts, branches, new products, and new systems. These are comforting signals because they are easy to present and difficult to argue against. But visible growth hides invisible strain.
I was engaged to support a mid-sized organization that had doubled its staff in three years. On paper, the story was impressive. Expansion into new regions. A modern technology stack and youthful workforce. Inside, the organization was brittle.
Approvals took longer. Accountability was blurred. Senior leaders were firefighting instead of leading. Cybersecurity incidents were quietly increasing, not because people were careless, but because access controls designed for fifty people were now stretched across two hundred.
Growth did not expose incompetence but exposed design flaws.
Growth amplifies weakness before it creates strength
Leaders often expect growth to solve problems, and more people will reduce workload, more systems will improve efficiency, and more structure will bring order. In practice, growth magnifies what already exists.
Weak processes become slower, poor decision rights become political, unclear strategy becomes noise, and culture becomes inconsistent because it was never explicit to begin with.
In one case, a well-meaning executive introduced new performance targets to “support growth.” Managers responded by optimizing for numbers, not outcomes. Risk reviews were rushed, controls became box-ticking exercises, no one was malicious, but everyone was rational. The system rewarded speed over judgment.
This is where boards often misread the situation. They ask for acceleration when the organization is asking, quietly, for redesign. Technology scales risk faster than value. From a cybersecurity and digital risk perspective, growth is ruthless. Every new hire is an access point, every new system is an attack surface. Every rushed integration is a control gap waiting to be exploited.
I have witnessed organizations invest heavily in modern platforms while ignoring basic discipline. Role-based access was loosely defined. Exceptions became permanent. Incident response plans existed on paper but had never been tested under pressure.
Growth exposed the truth: technology does not create resilience, and governance does.
If your organization cannot explain who can access what, why, and for how long, growth is not progress. It is a liability.
Culture does not happen by accident; culture is often treated as a soft issue, something to be addressed once growth stabilizes. That is backward. Culture is the operating system that determines how decisions are made when leaders are not in the room. Growth multiplies moments when leaders are absent.
In the organization I mentioned earlier, new staff learned quickly that silence was safer than challenge. Speed was rewarded more than judgment. Escalation was seen as incompetence. None of this was written. All of it was learned. Culture did not collapse. It behaved exactly as designed, by default.
Here is what disciplined leaders do differently
High-performing leaders think about growth the way engineers think about load. Before adding weight, they reinforce structure. They redesign processes before hiring, clarify decision rights before expanding teams, test controls before scaling technology, and teach culture deliberately, through stories, consequences, and example.
Most importantly, they slow down at the right moments. I advise leaders to run a simple exercise. Freeze hiring for ninety days. Map one critical process as it truly operates today, not as it appears in policy. Identify delays, handoffs, risks, and informal workarounds. Then ask a hard question. If this process doubled tomorrow, would it break?
That answer tells you whether you are ready to grow.
The board’s role in responsible growth
Boards play a critical role, and they often get it wrong with good intentions.
They push for targets without asking whether the organization’s operating model can absorb them. They approve investments without demanding evidence of control maturity. They celebrate expansion while early warning signs are dismissed as operational noise.
Future-ready boards ask different questions. Where does growth increase risk concentration? Which controls are no longer fit for scale? Which decisions are still centralized when they should be distributed, and which are distributed when they should be controlled?
Growth governance is not about restraint but about sequencing. Growth is not momentum; it is design under pressure. Organizations that endure treat growth as a disciplined act, not an emotional one. They accept short-term discomfort to avoid long-term fragility. They build stems before bunches.
If growth feels chaotic, it is not because people are failing. It is because the system has outgrown its design. The solution is not more energy. It is a better architecture.
That is the difference between organizations that expand and organizations that last.
Case study: when growth exposed the cracks
I was asked to support a mid-sized financial services institution that had grown quickly over five years. New products. New regions. A young, ambitious workforce. From the outside, it looked like a success story.
On my first morning, I did what I always do. I sat quietly. I listened.
By 10 a.m, I could feel the tension. Phones ringing. Managers pacing. A senior leader, tall, sharp, always in a fitted jacket, moved from desk to desk solving problems personally. He was proud of his accessibility. He was also the bottleneck.
What growth looked like on paper
Headcount had tripled, systems had been upgraded twice, revenue was growing, but margins were thinning. The board wanted more speed. On slides, growth looked clean. In reality, work had become heavier, not easier.
A junior analyst, soft-spoken, eyes glued to her screen, explained how approvals worked. One transaction needed four sign-offs, two systems, and a manual spreadsheet “just to be safe.” No one trusted the system fully, so everyone kept their own version of the truth.
That is what uncontrolled growth creates. Parallel realities.
The silent breakdown of processes
I asked the operations manager, experienced, calm, visibly tired, to walk me through a simple customer request. What should have taken one day was now taking five.
Why?
Because growth had layered complexity without redesign. Every new risk incident had added a control. Every new audit finding added a checklist. No one had stepped back to simplify. Controls multiplied, but clarity disappeared.
People were working harder, and outcomes were getting worse.
Technology is scaling the wrong things
The technology team had done what they were asked. They rolled out new tools to support growth. Access was granted quickly so work could move. But no one had reviewed who still needed access and who did not.
One afternoon, during a routine check, we discovered that a staff member who had changed roles six months earlier still had system rights that could override transactions. Not because of fraud. Because offboarding processes had not scaled with growth.
This is how cyber risk actually grows. Quietly.
Culture under pressure
What struck me most was not the systems. It was behavior.
In meetings, people avoided difficult questions. Everyone was polite. Decisions were deferred upward. Mistakes were hidden until they became incidents.
I asked a middle manager, confident and articulate, why issues were not escalated earlier. She paused, then said, “We did not want to slow growth.” That sentence tells you everything.
Growth had become a belief. Challenging it felt disloyal.
The turning point
Instead of pushing for more expansion, leadership did something rare. They paused. Hiring was frozen for sixty days. Each department was asked to map one critical process exactly as it ran, not as designed and lived. The maps were messy, with red arrows, sticky notes, and handwritten exceptions, but for the first time, everyone saw the same reality.
Decisions were clarified, controls were simplified, and access rights were cleaned up. Managers were trained to decide, not escalate.
Growth resumed later, slower, stronger, and safer.
The lesson leaders miss
This organization did not fail at growth. It failed to redesign before scaling. Growth did not cause the problems. It revealed them. That is the lived truth of growth. It is not an achievement. It is exposure. And disciplined leaders treat it that way.
Copyright Summit Consulting Ltd 2025. All rights reserved.
