Your organisation isn't broken. It's just running on a model that made sense three years ago.

The impact sector has had a rough few years operationally, and not always for the reasons people say out loud. Yes, funding is tighter. Yes, demand is up. But the quieter problem, the one that doesn't make it into board reports, is that a lot of organisations are now running on infrastructure built for a simpler version of themselves.

They've grown, or diversified, or taken on contracts that pulled them somewhere new. The team has changed. The compliance picture has changed. The funders have changed, and with them the reporting requirements, the due diligence expectations, and the frequency with which someone senior has to drop what they're doing to answer a question that should be straightforward but somehow isn't. The way the organisation actually runs, though, the systems, the reporting lines, the decision-making, the processes, has often stayed roughly where it was. So things get slower, stickier, harder to explain. Not broken. Just misaligned.

This is not a failure of leadership. It is what happens when an organisation grows faster than its operational design. The machinery hasn't kept up with the work. And the longer that goes unaddressed, the more energy the organisation spends compensating for it rather than getting on with things.

What misalignment actually looks like

It shows up in recognisable ways, though people don't always call it misalignment when they're living inside it.

Meetings that exist to compensate for unclear ownership. Not because the team is disorganised, but because nobody ever explicitly decided who holds what, so the default is to get everyone in a room and work it out in real time. That works when you're small. It becomes expensive, and quietly demoralising, when you're not.

Reporting that takes longer than it should because the data lives in three places and someone has to manually reconcile it every month. The person doing that reconciliation probably doesn't flag it as a problem because they've been doing it long enough that it just feels like their job. It isn't their job. It's a gap in the system that got assigned to a person because that was easier than fixing the system.

Staff who are capable and motivated but who spend too much of their time navigating internal friction. Chasing sign-offs. Waiting on information that should be readily available. Redoing work because the brief wasn't clear, not because the brief was anyone's fault, but because the process for scoping and approving work was never really designed, it just evolved.

Leaders who know something needs to change but aren't sure what, or where to start, so they don't. Or they pick the most visible problem and fix that, only to find six months later that something else has surfaced, because the visible problem was a symptom and the underlying cause is still sitting there.

None of this is dramatic. The organisation is still delivering. The mission is still being served. But internally it feels harder than it should. And that feeling, that low-grade sense of running on more effort than the outputs justify, is usually the signal that something in the operational design needs attention.

Why the impact sector is particularly exposed

Impact organisations are often built around mission first and infrastructure second. That's not a criticism. It's frequently the right call in the early stages. You prioritise the work, prove the model, build the team around the delivery. The systems come later. Except that later has a way of never quite arriving, because there's always another funding round, another contract, another partnership that needs attention. The infrastructure gets deprioritised repeatedly until it's genuinely struggling to support the weight of the organisation sitting on top of it.

Funding structures compound this. When your income is project-specific and time-limited, it's genuinely difficult to invest in core operations. You can't always justify a systems upgrade or a process review to a funder who wants to see direct delivery costs. So you make do, and making do works until it doesn't.

Governance adds another layer. CICs, social enterprises, and CDFIs often have boards with legitimate oversight requirements, but the internal reporting infrastructure to meet those requirements efficiently sometimes lags well behind the expectation. The result is that a disproportionate amount of senior staff time goes into producing information for governance purposes rather than using it to actually run the organisation.

Then there's the people dimension. The impact sector attracts people who are genuinely committed to the work, which is a strength, but it also means people will absorb operational dysfunction rather than escalate it. They don't want to be seen as making a fuss, or they assume everyone else is managing fine and the difficulty is somehow personal. It isn't. It's structural.

The instinct to over-diagnose

When organisations do recognise that something isn't working, the instinct is often to reach for a large solution. A restructure. A new strategy. A wholesale systems replacement. A consultant on a six-month engagement with a fifty-page report at the end of it.

Sometimes that's the right answer. But more often, the organisation doesn't need rebuilding. It needs a specific bit of it fixed, and it needs that fix to be proportionate to the actual problem rather than the anxiety around it.

The challenge is knowing which bit. Because by the time the friction is visible enough to act on, it's usually been building long enough that it feels tangled, and the temptation is to treat the whole thing as one interconnected problem requiring a comprehensive solution. That instinct is understandable but usually counterproductive. Comprehensive solutions take a long time, cost more than anticipated, and often disrupt the delivery capacity of an organisation that is already under strain.

The more useful question is: what is the one thing, if we fixed it, that would make the most difference to how we run? Not the most impressive thing. Not the most ambitious thing. The most impactful thing, right now, given what we actually have capacity to do.

Fixing the right thing first

This is harder than it sounds, because the most painful problems aren't always the most important ones to fix. Pain is a function of visibility and personality as much as it is of operational significance. The thing causing the most noise might be a symptom of something quieter and more structural. The thing nobody's talking about might be the thing costing the most time and energy.

Getting to the right answer requires honesty that organisations sometimes find difficult. Honest about where the real friction is, not just where it's most visible. Honest about what the leadership team is actually spending its time on, versus what it should be. Honest about which processes are genuinely serving the organisation and which ones exist because they were set up four years ago and nobody's reviewed them since.

It also requires a willingness to start small. Identify one thing, fix it properly, move on to the next. That feels less satisfying than a comprehensive transformation programme, but it tends to actually work. It builds confidence in the organisation's ability to change, produces visible results quickly, and doesn't require absorbing more disruption than the organisation can handle alongside its existing delivery commitments.

What this looks like in practice

A CDFI that's grown from five to fifteen staff in three years and is still running its compliance monitoring on a spreadsheet designed for the original team. The spreadsheet works, technically, but it takes two hours a week to maintain, it's held by one person, and if that person is off sick the information is inaccessible. The fix isn't a full systems overhaul. It's a decision about the right tool, a migration that takes a few days, and a clear protocol for who maintains it. Six weeks of focused attention and a significant operational risk is closed.

A CIC with a board that receives detailed quarterly reports but has been quietly asking for more frequent financial oversight. The finance function is producing the information, but in a format designed for historical reporting rather than forward-looking decisions. Nobody has sat down with the board to understand what they actually need, or redesigned the output accordingly. Two days of work, one conversation, a reformatted dashboard. The board gets what it needs, the finance team stops getting ad hoc requests between cycles, and the CEO gets fewer calls.

A social enterprise where three senior staff each believe they are responsible for a particular client relationship, with the result that the client is sometimes contacted three times and sometimes not at all. Not a people problem. A design problem. Clear it up once, document it, done.

None of these are transformational. They're practical. But collectively, over time, they change how an organisation feels to work in and how much of its energy is available for the mission rather than consumed by the machinery.

The messy middle is not a crisis

That's what gets lost when organisations are in the middle of it. It can feel like one, particularly to the people absorbing the most friction. But the messy middle is a sign that the organisation has grown, taken on more complexity, and not yet updated its operational design to match. That's a normal part of organisational development. It's also fixable, without drama, if you're willing to be honest about where the friction is and disciplined about addressing the right thing first.

The organisations that come out of it well are not the ones that launch the most ambitious transformation programmes. They're the ones that get clear about the problem, start with something specific, and keep going until the machinery is running well enough to support the work it's carrying.

That's what The Messy Middle is here for.