Signs Your Organisation Has Outgrown the Way Work Gets Done

If work takes more chasing than it used to, that does not automatically mean your team is underperforming.

In many small nonprofits and small organisations, growth happens gradually. The work expands around what is already there: spreadsheets, email chains, shared drives, verbal handovers, and a lot of staff memory. For a while, that can work well enough.

Then the strain starts to show.

Reporting takes longer. Simple tasks need more follow-up. People spend time checking which version is current, who is meant to do the next step, or whether something has already been done. The work still gets done, but often because someone is quietly filling the gaps.

That is often a sign the organisation has outgrown the way work is set up now.

This is not about blaming people or assuming everything needs a new system. It is about recognising when a way of working that once felt practical no longer fits the level of coordination the organisation now needs.

When ordinary work starts needing more effort

One of the clearest signs is that routine work starts taking more effort to keep moving.

Not necessarily more difficult work. Just more effort around the edges.

Tasks that used to move easily from one person to another now need reminders, checking, or extra clarification. Someone has to confirm whether a form was updated, whether the latest figures are correct, or whether a request in a shared inbox has been picked up.

Reporting is often where this becomes easiest to see. A board paper or funder report that should be fairly straightforward ends up taking days because the information sits across spreadsheets, inboxes, shared folders, and people’s heads. Staff have to pull figures together manually, compare versions, and double-check that the final numbers match what actually happened.

The work is still moving, but people are doing extra coordination to hold it together. They are reminding each other, copying information between places, cross-checking small differences, and carrying key details in memory.

That hidden effort is easy to normalise in a busy team. But when it becomes a regular part of how work gets done, it usually points to a process that no longer fits the work.

What this often looks like in practice

Usually, this does not show up as one obvious failure. It appears as a cluster of familiar frustrations.

A spreadsheet that started as a simple tracker begins doing several jobs at once. It becomes part record, part handover tool, part reporting source, part task list. Different people update it in different ways. Multiple versions appear. Ownership becomes unclear. People still rely on it, but not always with full confidence.

A shared inbox or long email thread can develop in much the same way. What began as a simple place to receive requests becomes the main handover point for important work. Over time, it gets harder to tell what is waiting, what has been completed, what needs a response, and who owns the next step.

You may also notice that things run smoothly only when certain people are around. An experienced staff member knows where the latest numbers are, which spreadsheet matters, how a referral should be logged, or what a particular funder expects in a report. When that person is away, progress slows quickly.

Another common pattern is information spread across different places. One update sits in a spreadsheet, another in email, another in a document on a shared drive. Handovers become inconsistent because each person is piecing together the picture from a different starting point. Staff then spend time checking what has already happened before they can confidently take the next step.

None of this means people are careless. More often, it means the organisation is still relying on informal ways of working that made sense when the work was smaller or simpler.

The issue is usually process fit

This is the useful thing to name clearly: often the problem is not the team, and not growth itself.

The problem is that the way work is organised no longer fits the level of coordination now required.

What once felt lightweight and practical can become harder to rely on when more people, programmes, reporting needs, funders, or stakeholders are involved. The old setup may still look familiar on the surface, but underneath it now depends on more remembering, more interpretation, and more manual effort than before.

That is why outgrown processes can be hard to spot. They do not always look broken. They often look busy. They look like capable people working hard to keep ordinary things on track.

Informal processes can work well at a smaller scale. In a small team, it is normal to rely on quick conversations, staff memory, or a spreadsheet that everyone understands. The difficulty comes when that same arrangement has to support clearer handoffs, reliable reporting, repeated coordination, and shared visibility across more moving parts.

A common example is a spreadsheet or shared inbox that stops being a simple tool and starts becoming a coordination workaround. Not because spreadsheets or inboxes are bad, but because they are now carrying work that depends on people remembering what entries mean, what has changed, and what needs to happen next. If that sounds familiar, this article on When your spreadsheet is doing too much work goes into that pattern in more detail.

For example, a small nonprofit managing referrals may cope for quite a while with a spreadsheet, inbox, and informal verbal updates. It can seem manageable because experienced staff know how to read between the lines. But when one of those staff members is away, nobody can easily see the full picture: which referrals are new, which need follow-up, what has already been done, and where the latest information sits. The absence does not create the problem. It reveals it.

The same pattern shows up in grant reporting. A team may continue producing reports through effort and goodwill, but if every cycle requires manual checking across several files and repeated clarification about whose numbers are final, the process is being held together by workarounds rather than by a clear, repeatable method.

How to tell whether this is growth strain, a people issue, or an outgrown process

It helps to separate normal busyness from a structural problem in how work is set up.

Every organisation has busy periods. Deadlines cluster. Staff cover for each other. Some friction is normal. But if the same operational problems keep repeating across different people, teams, or reporting cycles, it is worth looking beyond individual performance.

If several people run into the same confusion about where information lives, what the next step is, or who owns a task, that points to a setup issue rather than a single-person issue. If different staff members keep creating the same workarounds, they are usually adapting to the same underlying gap.

Repeated clarification is another useful sign. If routine tasks regularly require people to ask for updates, confirm status, chase missing details, or re-check what was already entered somewhere else, the process may depend too heavily on verbal handovers and informal knowledge.

You can also look at what happens when someone is unavailable. If work becomes noticeably risky whenever a key person is off sick, on leave, or leaves the organisation, that is a strong sign the process is too dependent on individuals. The risk sits not only in staffing, but in the fact that important coordination lives in memory rather than in a clearer shared method.

In other words, the question is not simply, “Are we busy?”

A better question is, “Does this work still run reliably without extra chasing, translation, remembering, and patching?”

If the answer is no, there is a good chance you are dealing with an outgrown process, not just a demanding month. For a closer look at that distinction, How to tell if it’s a process problem or an overloaded team is a useful next step.

A simple self-check

If this sounds familiar, the most useful next step is not to jump straight into a major overhaul. It is to look closely at where work has become too manual, too fragmented, or too dependent on specific people.

Start with a few practical questions.

Where does key work rely on one person knowing what happens next, where the latest information sits, or who needs to act? Where are people keeping things moving through manual reminders, duplicated data entry, spreadsheet workarounds, or inbox chasing? Where do approvals, handovers, reporting, or routine coordination become more difficult as volume grows, even though the work itself is not much more complex?

You are not looking for perfection. You are looking for pressure points.

Those pressure points usually show you where an informal process has stopped being flexible and started becoming fragile.

If important work also depends on one or two experienced people, read When Documentation Is Not Enough to Reduce Key-Person Risk. If the strain became more visible after new software or a system change, use the staff buy-in guide to check whether the real gap is training, workflow, setup or ownership.