Insights

How Do You Know Your Charity Has Outgrown Its Systems? Seven Signs to Look For

Low-poly illustration of a large navy tree bursting out of a small cracked plant pot, roots spreading across the ground - a metaphor for a charity outgrowing its systems

The call usually comes after a funder asks a simple question. How many people did we reach last quarter? What did that programme actually cost? And somewhere in a twenty-person charity, three people spend four days assembling an answer from nine spreadsheets – all of them slightly different, none of them wrong exactly, and nobody sure which one to trust.

Nobody rings me because a system fell over. Charity systems rarely fall over. They fray. The organisation grows from eight people to twenty, the tools and habits that worked when everyone sat around one table keep limping along, and the cost shows up everywhere except an error message: in evenings, in rework, in decisions that wait a week for information that should take a minute.

So how do you tell the difference between normal growing pains and an organisation that has outgrown the way it works? Here are the seven signs I see most often – and what I’d do about them.

1. Simple questions take days to answer

The clearest sign. If “how much have we spent against this grant?” or “how many volunteers were active last month?” triggers a scramble rather than a lookup, your information is living in the wrong places. The question isn’t hard – your systems are making it hard.

2. Nobody is sure which version is right

Two budgets with the same name and different totals. A beneficiary list on someone’s desktop that’s three weeks ahead of the one in the shared drive. One organisation I worked with had more than a decade of impact data spread across dozens of disconnected spreadsheets – real, valuable evidence that couldn’t be used because no single view of it existed. Version doubt corrodes every decision built on top of it.

3. The same information gets typed in more than once

A donation arrives. Someone records it in the fundraising tracker, again in the finance sheet, and a third time in the report for trustees. Every duplicate entry is a chance for the copies to disagree – see sign two – and a slice of somebody’s week that the mission never gets back.

4. Everything still runs through one person

Usually the founder or CEO. Approvals, passwords, the only accurate picture of the finances, the unwritten knowledge of how things are done. In a small team this is manageable – which is exactly why it rarely gets dealt with head on. Nothing is visibly broken, so the dependency deepens with every year it goes unquestioned. Then the team grows, and what was manageable becomes unsustainable – and a risk the board should be asking about. If a week of your absence would stall the organisation, that’s not dedication – it’s a design flaw.

5. New starters take weeks to learn “how we actually do things”

Not the work itself – the workarounds. Which spreadsheet is the real one, who to ask before touching the newsletter tool, why invoices go through a specific inbox. When process lives in people’s heads rather than anywhere written down, every departure takes institutional memory with it and every arrival pays a tax to rebuild it.

6. The workarounds have become the process

Somebody once exported the data to fix a one-off problem, and now the export is how it works. Growing organisations accumulate these patches the way old houses accumulate wiring – each one reasonable at the time, the whole increasingly hard to touch. If your team’s honest answer to “why do we do it this way?” is “because that’s how we’ve always got round it”, the patch has been promoted to infrastructure.

7. You’ve started saying no to growth

The most expensive sign, and the least visible. A funder hints at a bigger grant and your stomach drops, because you know the reporting would break you. A partnership opportunity gets a slow reply because nobody has capacity to absorb it. When operational strain starts vetoing mission decisions, the systems have stopped serving the organisation and started steering it.

Why this happens – and why it isn’t a failure

None of this means anyone did anything wrong. Your systems were built for the organisation you were – probably by committed people doing their best with no budget and less time. Then the organisation changed shape and the systems didn’t. Growth is the one problem every mission-led organisation hopes to have; outgrowing your systems is simply what it feels like when you get it.

I’ve been the embedded operations partner inside organisations going through exactly this – including one that grew twelvefold without delivery falling apart, because the operational foundations were rebuilt deliberately, ahead of the growth rather than after it. There’s more on how that work looks in practice on the case studies page. That’s the difference between organisations that scale and organisations that swell.

What to do about it – and one thing not to do

The thing not to do first: buy software. New tools bolted onto unclear processes give you the same confusion at a higher subscription price – and AI makes this worse, not better, because AI amplifies whatever operation you already have. Messy in, messy out, faster.

Start instead by looking honestly at where the friction actually is. Map how work actually flows – not how the org chart says it flows. Decide what the organisation you’re becoming needs, not what patches the organisation you were. Then, and only then, choose tools – fewer of them, connected, and sized for a team of your scale and budget. I’ve replaced one organisation’s dozens of disconnected spreadsheets with a single integrated stack that runs on under £5,000 a year. Good operations for a small charity is not an enterprise IT project.

If several of these signs felt uncomfortably familiar, that recognition is worth acting on while it’s fresh – before the strain chooses for you which opportunities you can afford to take.


Wondering where your organisation stands?

The Operational Maturity Assessment benchmarks your charity, NGO or social enterprise across six dimensions of operational maturity in two to three days – or start with the free self-assessment, which uses the same framework and takes a few minutes.

Get in touch for a no-obligation conversation about what might work for your organisation.

Leave a Reply

Discover more from Scale Impact

Subscribe now to keep reading and get access to the full archive.

Continue reading