There is a particular kind of organisational problem that I find myself inside more often than any other. It is not a crisis. It isn't even obvious dysfunction. It is quieter and yet more expensive than either.
An organisation has grown. Revenue is up. Headcount has expanded. The customer base has broadened. By every external measure, things are working. And yet, somewhere in the second or third year of that growth, the senior team starts to notice something has changed.
Decisions are taking longer. Meetings are multiplying. The same conversations are happening in different rooms and arriving at different conclusions. Execution that used to feel natural is now effortful. Everyone is working harder than before, and less is getting done.
This is what growth friction feels like from the inside. And it is one of the most misdiagnosed conditions in organisational life.
When leaders feel this friction, the instinct is almost always to look for a people problem. Someone isn't performing. A team isn't communicating. Leadership isn't aligned. Though these things may be true, they are symptoms, not causes.
The actual cause, in the majority of cases I've seen, is structural. The organisation grew, but the operating model didn't grow with it.
What I mean by operating model is the underlying architecture of how work moves through the organisation, which is in how decisions get made, how information flows, how roles relate to each other, how processes connect across teams. Early in an organisation's life, this architecture is informal and that's fine. Small teams compensate. Smart people fill gaps. Proximity substitutes for process.
But as the organisation scales, those informal workarounds become load-bearing and then, they calcify. And the organisation that once moved quickly because it was small now moves slowly because it is carrying the weight of its own accumulated informality.
The organisation grew, but the operating model didn't grow with it. That gap is the source of almost all growth friction.
The costs are rarely visible on a single line of a budget. They are distributed and in time lost to unnecessary escalation, in decisions deferred because accountability isn't clear, in technology that sits underutilised because the process it was supposed to support was never actually redesigned.
I worked with a prominent service provider a few years ago that had doubled in size over three years. They had added people, expanded services, and invested in a new case management system. By the time we arrived, the system had been live for eighteen months and almost none of the efficiency gains it had promised had materialised.
The technology worked. The problem was everything around it. The workflows had been designed for the old system's logic. Roles hadn't been redefined to reflect what the new system made possible. Data was being captured for compliance, not for the decisions that actually needed to be made.
The organisation had grown. The operating model had not. The technology had arrived into that gap and been absorbed by it.
In my experience, growth friction tends to concentrate in three specific places. Recognising them is the first step toward addressing them deliberately.
The first is decision architecture. As organisations grow, the informal decision-making that served them early with the founder deciding, the senior team aligning over a lunch, well, that no longer scales. But formal decision rights are rarely designed explicitly. Instead, they emerge through precedent and hierarchy. The result is that decisions travel upward by default, escalation becomes the norm rather than the exception, and senior leaders find themselves in the weeds of operational calls they shouldn't be making.
The second is process coherence. Growth typically happens faster than process redesign. New services get bolted onto existing workflows. Exceptions become standard practice. Teams develop their own ways of doing things that are locally efficient but collectively fragmented. By the time anyone notices, the end-to-end process has become genuinely difficult to describe. That's because it no longer exists as a single coherent thing.
The third is role clarity at the boundaries. In small organisations, ambiguity at the edges of roles is covered by relationships and goodwill. As the organisation grows, those edges become fault lines. The work that sits between teams, the handoffs, the shared responsibilities, the things that belong to everyone and therefore to no one, that is where execution most often breaks down.
The organisations I've seen navigate scaling well are not the ones that move fastest. They are the ones that pause, with some regularity, to ask a question that is deceptively simple: is how we are organised still fit for what we are trying to do?
That question is harder to ask than it sounds. Growth creates momentum, and momentum resists examination. When things are working, when revenue is growing and clients are happy and the team is busy, it feels counterintuitive to stop and interrogate the operating model. That interrogation is, by definition, going to surface things that are uncomfortable.
But the cost of not asking is higher. Friction that is addressed at the point of first emergence costs a fraction of what it costs eighteen months later, when it has become embedded in culture, in process, and in the expectations of the people who have adapted their working lives around it.
Friction addressed early costs a fraction of what it costs once it has become embedded in how the organisation operates.
I am not describing a transformation programme. I am describing a discipline.
Organisations that grow without friction or the ones that recover from it quickly when it emerges, have made a habit of periodically reviewing their operating model with the same rigour they apply to their strategy. They treat decision architecture, process coherence, and role clarity as things to be actively maintained, not assumed.
In practice this means: being explicit about who makes which decisions and at what level. It means designing processes end-to-end rather than team by team. It means reviewing role boundaries when the organisation restructures, not after the problems appear. And it means ensuring that technology is introduced into a process that has been redesigned to receive it, not dropped into a process that is already under strain.
None of this is glamorous. But in my experience, it is where the real work of sustainable growth happens -- in the unglamorous, un-newsworthy discipline of keeping the operating model current with the organisation it is supposed to serve.
Growth creates complexity. Design converts that complexity into capability. The difference isn't how fast you move. It's whether you've built the infrastructure for the speed you're attempting.
Sudharsan Raghunathan | Founder, LeanCX.
Sudharsan works with enterprise leaders to redesign how their organisations actually function by aligning people, process, and technology so transformation sticks.
Leancx.com.au
