Accelerated Growth | | 8 minutes read

Why processes that work at twenty people collapse at a hundred

Written by

One of the questions I am often asked by founders is why a business that ran smoothly last year suddenly feels difficult to manage. Revenue is up, the team is bigger and customers are arriving, yet everything seems to take longer and cost more than it should. In my experience, growth rarely creates entirely new problems.

Office corridor walls with subtle lighting

More often it exposes weaknesses that were already there, hidden by the size and closeness of a smaller team. Understanding that transition is one of the more important parts of building a business that can scale sustainably.

Why small teams get away with it

In a business of twenty people, success often depends on flexibility. Questions are answered across the desk. Decisions are made informally. Experienced individuals carry a great deal of knowledge in their heads, and problems are solved through conversation rather than formal workflow. At that size, this works well and I wouldn't suggest otherwise. Introducing heavy process too early can be as damaging as introducing it too late.

The difficulty is that growth increases complexity on several fronts at once. Teams specialise, new departments appear and management layers develop. Customers become more varied, service delivery becomes more involved, and staff turnover becomes a fact of life. Processes designed for a tightly connected group are suddenly expected to support an organisation five times the size. These weaknesses rarely announce themselves. Processes continue to function adequately until a threshold is reached, and then bottlenecks, miscommunication and unclear accountability seem to arrive together.

Key considerations

Informal communication stops scaling

When people sit near one another, information travels naturally. As the organisation grows, relying on conversation creates inconsistency. Teams receive conflicting messages and decisions become hard to trace. Processes need to move from relying on who knows something to ensuring that anyone who needs the information can reliably find it.

Key person dependencies become operational risks

Smaller businesses often depend on a handful of experienced people who understand the systems, the customers and the suppliers. That is entirely understandable. At scale, however, knowledge that lives only in individuals leaves the organisation exposed to absence, turnover and unexpected change. Knowledge needs to become organisational rather than personal.

Manual workarounds reach capacity

Spreadsheets, email chains and manual approvals are often the right tools in the early stages. The problem emerges when volumes or complexity outgrow what they were designed to handle, and an efficient workaround becomes a daily bottleneck.

I saw this clearly with a food testing laboratory client of ours. Their data management relied on Microsoft Access and Excel logs, certificates were produced manually through a PDF creator, and many records were still on paper. There was no link between the testing operation and invoicing, so the same information was often entered two or three times. None of this had been unreasonable when the business was smaller. It simply could not support the business they were becoming.

The same pattern appeared at another client, who were processing gift card orders manually. Every gift card processor required a different format, so each order needed considerable intervention. As their client base grew, that approach consumed more and more time. A centralised ordering platform, with a portal for their operations team and API connections to the various processors, replaced it.

Decision making structures need to mature

In a small business, the founder or leadership team can comfortably make most of the significant decisions. As the organisation grows, that becomes a constraint. Teams wait for approvals, priorities become harder to manage and bottlenecks form around a few individuals. The answer is not necessarily to add management layers. It is more often to create clear frameworks that let people decide within agreed boundaries.

Visibility matters more than control

A natural reaction to growing pains is to introduce more controls. Some are necessary, but excessive oversight creates friction of its own. It is generally more effective to improve visibility through metrics, reporting and well designed workflows, so that leaders can understand performance without being involved in every decision.

Adding people is not the same as scaling

Organisations respond to operational strain by adding headcount. This can provide temporary relief, but it rarely addresses the process limitations that created the strain.

I think about this in much the same way as technical debt. Processes that were reasonable at twenty people accumulate a form of operational debt as the business grows. The cost of that debt is manageable when it is identified early and becomes far more disruptive when it is discovered during a period of rapid expansion.

Looking back on my own career, which began in large centralised IT departments in the 1980s, I have seen that the organisations coping best with growth were those that treated process design as a strategic capability rather than an administrative task. Context matters here too. A fifty person business does not need the governance of a five hundred person one. The aim is to anticipate the next stage, not to build for a scale that may never arrive.

What this means for the business

Failing to prepare for growth tends to show up as reduced productivity, inconsistent customer experiences, rising operational costs and slower decision making. It also affects people. Onboarding becomes difficult and capable employees become frustrated working around systems that no longer fit.

Organisations that design for scale tend to see the opposite: more consistent service, faster onboarding, better management visibility and more predictable operations.

The same applies to technology. When we worked with a school uniform and book bag manufacturer whose outdated systems were stalling growth, the move to an integrated eCommerce and back-office platform led to an 80% increase in operational output. It also improved the customer experience. The technology was the enabler. The real change was in how the business operated.

Questions worth asking

If you are leading a growing business, some practical questions are worth reviewing:

  • Which activities rely heavily on specific individuals?
  • Where does critical knowledge exist only in conversations rather than documented processes?
  • Which manual processes would struggle if transaction volumes doubled?
  • Where is leadership approval creating bottlenecks?
  • Does each key business function have a clear process owner?
  • Do you have the visibility to understand performance without getting involved in every decision?
  • Are processes reviewed against projected growth, rather than only current requirements?

Final reflection

Growth is a sign of success, but it also tests the foundations a business was built on. The processes that carried you to twenty people deserve credit for doing so, and they are worth revisiting before they are asked to carry you to a hundred.

The question organisations should consider is not whether their processes work today, but whether they will still work when the business is twice the size. Hopefully these reflections help.

Share

LinkedIn Facebook X


Get in touch

Find out how Reuben Digital can transform your business

info@reubendigital.co.uk
+44 (0) 1793 861443