Why Good Processes Break Under Growth — And How to Redesign for the Next Scale

There is a moment in the growth of almost every business when things that used to work stop working — not catastrophically, but persistently. Decisions that used to be made quickly now take days. Quality that was consistent becomes variable. New hires that were effective in their first weeks take months to reach independence. Communication that kept everyone aligned starts to fragment. The instinctive response is to attribute these problems to the additional complexity of being bigger. The more accurate diagnosis is that the processes designed for the previous scale have been carried forward unchanged into a new scale for which they were not designed.

What a process is actually designed for

A process is not designed in the abstract. It is designed for a specific organisational context: a specific number of people, a specific information environment, a specific distribution of authority and expertise, a specific communication density. A five-person team can coordinate through conversation because everyone talks to everyone. The process designed for that team is implicitly informal and dense with interpersonal communication. At fifty people, the same approach fails — not because conversation is bad, but because the density of conversation required to coordinate fifty people is simply not achievable. The process needs to change. This seems obvious stated plainly, but it is consistently ignored in practice. The reason is that changing a working process feels like fixing something that is not broken. At the moment the redesign is needed — when the business is growing and the team is busy — the process still appears to be working, because the problems it is creating have not yet become acute. By the time they are acute, the organisation is operating under serious strain, and the redesign must happen under pressure rather than in advance.

The three assumptions that stop scaling

Most process designs that break under growth share one or more of three implicit assumptions that no longer hold at larger scale. The first is the assumption of shared context: that everyone involved in the process knows what everyone else knows. This assumption holds in a small team where information circulates naturally. It fails as the team grows and information fragments across functions and individuals. The fix is to make the shared context explicit — documented, accessible, and updated — rather than assumed. The second assumption is the assumption of available expertise: that the person with the knowledge needed to execute the process is always accessible. In a small team, the expert is usually a few steps away. At larger scale, the expert is often unavailable, on leave, or simply one of dozens of simultaneous demands on their time. The fix is to make expertise accessible through systems rather than dependent on a specific person's presence. The third assumption is the assumption of informal authority: that everyone knows who has the authority to make which decisions. In a small team, this is understood through proximity and relationship. As the team grows, the ambiguity of informal authority becomes a source of escalation and delay. The fix is to make authority explicit — who decides what, under which conditions, without needing to ask.

How to redesign for the next scale

Redesigning a process for the next scale requires answering three questions explicitly. What information does this process depend on, and is that information accessible to everyone who needs it — or only to the people who happen to know where it lives? What decisions does this process involve, and do the people executing it have the authority to make those decisions — or do they need to escalate? And what expertise does this process require, and is that expertise accessible at the moment it is needed — or only when the right person is available? Answering these questions reveals the specific assumptions the current process makes that will not hold at the next scale. Redesigning the process means addressing those assumptions directly: making information accessible, making authority explicit, and making expertise accessible through documentation and intelligent systems. The redesign does not need to be complex — it needs to eliminate the assumptions that growth will violate. Processes designed with those assumptions removed scale not because they were built for a larger business, but because they were built without the constraints of a smaller one.

For further reading on this topic, check out our guide on How to manage employees who refuse to enrol in PF.

For further reading on this topic, check out our guide on How to prepare your company for a bank loan application.