Growing pains in organisations

There's a moment in the life of a growing organisation when someone says: "We need to get ahead of this." Maybe headcount has doubled in eighteen months. Maybe a merger has brought two teams together. Maybe demand for services has outstripped what the current ways of working can comfortably deliver. Whatever the trigger, the instinct is the same - the organisation needs to scale its operations, and the leaders want to do it well.

That instinct is worth trusting. What's interesting is what happens next.

What most scaling operations advice focuses on

The default playbook for scaling operations is well established. Better processes. Clearer structures. Defined governance. More reporting. New systems. This is the operational machinery that a growing organisation needs - and most of it is genuinely necessary. An organisation at fifty people can't run the way it did at twenty. The infrastructure has to evolve.

But here's something worth noticing before any of that work begins. Each of those interventions - the new process, the restructured team, the governance framework - will land in an organisation that already works in a particular way. Information already flows along certain pathways. Decisions already get made through particular relationships. Trust already operates within certain boundaries. The culture already transmits itself through proximity and shared experience.

These aren't soft, intangible things. They're the operating conditions of the organisation. And they're the thing that determines whether any new structure, process, or system actually works as intended.

The two layers that determine how organisations scale

A useful way to think about this: every organisation runs on two layers at once.

The operational foundations are the visible layer. Processes, structures, governance, reporting, systems. This is the layer that appears in scaling plans, project boards, and consultancy proposals. It's tangible, it's designable, and it's genuinely important. A growing organisation needs operational infrastructure it didn't need before - clearer processes, better coordination, more deliberate ways of working.

The conditions underneath are the layer that rarely makes it into a plan. How decisions actually travel through the organisation - not the org chart version, the real version. How information reaches the people who need it, at the speed they need it. How trust works across the boundaries between teams. How new people absorb not just what the organisation does, but how it thinks. How much autonomy people have to solve problems at the point of delivery.

The conditions layer is what determines whether the operational foundations hold. A governance framework works when there's trust across the boundaries it creates. A new reporting structure works when information flows to the right people at the right speed. A coordination process works when the teams it connects understand each other's pressures and priorities.

When leaders start thinking about scaling, the operational foundations are usually where the attention goes first. That makes sense - they're visible, they're actionable, and the organisation clearly needs them. The risk is building the machinery without understanding the conditions it's landing in. Structure designed without seeing the whole system doesn't just miss things - it can create new friction while solving old problems.

How growth changes the conditions inside an organisation

Think about growth rings in a tree. Each ring doesn't just record a year of growth - it records the conditions the tree was growing in. Strong conditions produce wide, dense rings. Stressed conditions produce thin, compressed ones. The strength of the whole tree depends not just on its size, but on the quality of every layer underneath the bark.

Organisations grow in a similar way. Each stage of growth changes the internal conditions: who knows what, how quickly decisions move, whether the culture holds together or fragments, how much the informal connections that used to carry the organisation can still bear the weight.

When an organisation scales deliberately - addressing both layers together - each stage of growth genuinely strengthens the whole system. The operational foundations are designed for the conditions they're landing in. The conditions are evolved to support the new ways of working. The organisation gets stronger at the new size, not just bigger.

When only the machinery gets attention, something else happens. The structures are logical. The processes are sound. But decisions slow down because the trust to make them locally hasn't been built into the design. Information doesn't reach the right people because the informal networks that used to carry it were disrupted by the restructure. New hires have clear role descriptions but can't absorb how things actually work here, because the culture used to transmit itself through proximity and there's less of that now.

The organisation gets bigger. It doesn't get stronger.

Scaling operations in mission-driven organisations

Most scaling advice comes from the commercial growth world - enterprise value, revenue operations, exit preparation. For organisations driven by mission - housing associations, charities, social enterprises, public sector bodies - that language doesn't translate well.

The challenges are different. You're scaling impact, not revenue. You're accountable to residents, beneficiaries, or communities, not shareholders. And the culture that drives your work - the thing that makes people choose to work here, that shapes how services are delivered, that holds the organisation's identity together - is often the thing most at risk when growth puts the conditions under pressure.

Deloitte research has found that 65% of fast-growth companies identify culture dilution as their biggest concern during scaling. Not financial performance. Not market position. Culture - the thing that's hardest to see, hardest to measure, and hardest to rebuild once it thins out.

The Startup Genome Project's research on over 3,200 high-growth startups found that 74% failed due to premature scaling - expanding faster than the organisation's internal conditions could support. While that research focused on technology companies, the pattern is recognisable in any growing organisation. The issue isn't growth itself. It's growth that outpaces the conditions the organisation needs to function well at the new size.

For mission-driven organisations, getting this right matters more, not less. The quality of a repairs service, the consistency of support for vulnerable tenants, the culture of a frontline team - these things depend on conditions that have to be deliberately evolved as the organisation grows. They won't survive on autopilot.

What separates growth from scaling

The distinction between growth and scaling is worth holding onto. Growth is what's happening to the organisation - more people, more demand, more complexity. Scaling is the deliberate work of making the organisation function well at the new size. And that deliberate work has to address both layers, not just the visible one.

McKinsey's research on organisational growth suggests that companies which invest deliberately in their operating model during periods of expansion are significantly more likely to sustain that growth than those which focus purely on scaling headcount and output. The difference isn't more resources. It's better conditions for the resources to work within.

The leaders who tend to scale well are the ones who ask a particular kind of question early: not just "what operational infrastructure do we need?" but "what conditions need to evolve so the whole organisation works at the next size?" That second question is harder. It doesn't produce a neat project plan. But it's the question that determines whether the organisation's design supports the work or quietly works against it.

A practical starting point for scaling well

If you're at the beginning of thinking about scaling - or in the early stages of building the operational foundations for growth - here's a useful exercise. Pick a part of the organisation that's already feeling the pressure of growth. Ask two questions:

First: what operational infrastructure does this area need that it doesn't have? That's the machinery question. Better processes, clearer roles, stronger coordination - the tangible things.

Second: what conditions is this area depending on that might not hold at the next size? That's the question underneath. The informal knowledge that lives in three people's heads. The trust between two teams that was built through years of working together. The decision-making speed that depends on everyone being in the same corridor.

Most leaders find that the second question surfaces things the first one misses entirely. And those are usually the things that determine whether the scaling work actually lands.

The organisational maturity model can help map where these two layers stand across the organisation - not as a scorecard, but as a way of seeing where the growth rings are strong and where they might need attention before the next stage of growth begins.