Why Growing Organisations Still Feel Like They're Falling Apart

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

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. An organisation at fifty people can't run the way it did at twenty. The infrastructure has to evolve.

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 are the organisation's operating conditions. They decide whether any new structure, process, or system works as intended.

The two layers that determine how organisations scale

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. 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 them without understanding how the organisation already works. Structure designed without seeing the whole system can solve old problems and create new friction at the same time.

How growth changes the conditions inside an organisation

A tree's growth rings record each year it grew - wide and strong in good years, thin in hard ones.

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, it works on both layers together. Its leaders decide the few things all the teams hold in common, like which decisions can be made locally and which have to go up a level. Each team then works out what that means for its own work. The contact centre and the repairs team used to pass a tenant's repair between them with a quick word across the office. Once they're on different sites, they might agree how a repair passes from one team to the other, and who keeps the tenant posted. Neither team has to wait for a manager to settle it.

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.

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 trust between teams and on information reaching the right people. Both have to be rebuilt as the organisation grows.

What separates growth from scaling

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.

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 shows whether the organisation's design supports the work.

A practical starting point for scaling well

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.

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.