How to tell if the problem is your setup, not your team

When work feels harder to run than it should, it is easy to assume the team is the problem.

Often, it is not.

In many small organisations, the work still gets done. Reports go out. Services keep running. Deadlines are mostly met. But behind the scenes, people are holding things together with reminders, spreadsheet workarounds, memory, and extra effort.

That is often a sign that the setup is doing more damage than anyone has named yet.

This post is a practical way to tell the difference. If you are trying to work out whether the issue is capability, capacity, or the way work is organised, here are some signs to look for before you jump to hiring, restructuring, or changing tools.

When work gets done, but only because people keep rescuing it

This pattern is common in small organisations.

The work is getting finished, but only because people are constantly stepping in around the process. Someone reminds others what is due. Someone checks which spreadsheet version is current. Someone chases an approval, pulls figures together by hand, or remembers the step that is not written down anywhere.

On paper, there is a process. In practice, it only works because dependable people keep nudging it along.

This is often what operational strain looks like before anyone calls it that. Reporting feels heavier than it should. Routine admin takes too long. Handoffs are awkward. Everyone seems busy, yet simple recurring work still feels fragile.

That does not automatically point to a people problem. Often, capable staff are absorbing the strain. They fill gaps, patch cracks, and keep things moving, which makes the underlying problem harder to see.

What this usually looks like

The signs are usually quite ordinary.

The same information gets entered more than once because systems do not line up cleanly. A staff member updates a spreadsheet, then copies the same detail into a form, then emails someone else so they can update another tracker. None of that looks dramatic on its own, but it adds up.

Important tasks may depend on one person knowing what happens next. They remember who needs to approve something, where the latest version lives, or which figures need checking before a report goes out. If they are away, progress slows quickly.

Monthly reporting is a common example. It is often late not because anyone is careless, but because figures have to be pulled from multiple spreadsheets, checked manually, and matched across different versions. The effort sits in the gaps between steps, not in the competence of the people doing the work.

You may also notice that work moves through informal coordination rather than a reliable process. Things happen because someone sends reminder messages, follows up by email, or catches a colleague for a quick chat. Deadlines get met, but often through last-minute effort and rework rather than through a clear way of working.

Why this is often a setup problem

If work only succeeds because people are being unusually careful, helpful, and persistent, the issue is often structural rather than personal.

That is the key distinction.

When success depends on heroics, memory, workarounds, and manual patching between systems, you are usually looking at a setup problem, not a staff problem. The team may be doing a good job in difficult conditions.

Small nonprofits can misread this pattern. Repeated chasing can look like a performance issue. Painful reporting can look like a staffing issue. Heavy reliance on one dependable person can look like proof that they are simply better than everyone else.

Sometimes that is true. Often, though, good people are carrying a process that no longer works well.

The people described as “indispensable” are often holding together unclear ownership, messy handoffs, and manual fixes that should not depend on them in the first place. They are not just doing their job well. They are quietly compensating for work that has never been properly joined up.

Seeing that clearly matters because it makes it easier to fix the real cause instead of blaming the team for strain built into the way the work runs.

How to tell whether it is a team issue, a capacity issue, or a setup issue

These problems can look similar from a distance, so it helps to separate them.

A team issue is more likely when the process is already clear, documented, and workable, but performance is still inconsistent across people doing the same task.

A capacity issue is more likely when the process makes sense, but there is simply too much work for the time and resource available. The team knows what to do, but there is not enough room to do it sustainably.

A setup issue is more likely when good people can only get the work done by compensating for unclear steps, duplicate effort, weak handoffs, and inconsistent reporting. The process may exist in fragments, but it is not reliable enough to run without constant human patching.

A simple test is to ask this: if a capable new person joined tomorrow, would the work become straightforward quite quickly, or would they inherit the same confusion, chasing, and workaround habits as everyone else?

If the friction is built into the flow of work, the problem is probably not the individual.

A quick self-check

You do not need a full review to start spotting the pattern.

Ask yourself:

• Would routine work still happen smoothly if one key person were off for two weeks?
• Are staff spending a lot of time chasing updates, reconciling spreadsheets, re-entering data, or rebuilding reports by hand?
• Do the same problems keep showing up in the same places, such as approvals, reporting, handoffs, or client data?
• Are deadlines regularly met through extra effort and reminders rather than through a clear, repeatable process?
• Does important knowledge live mostly in people’s heads rather than in a shared way of working?

If several of those feel familiar, there is a good chance your setup is creating the bottleneck.

That does not mean your organisation is failing. It usually means the way work has evolved no longer matches what the organisation needs. People have adapted around that, often very well, but the cost shows up as friction, dependency, and avoidable manual effort.

What to do before you hire, restructure, or buy new tools

Before making a bigger change, name the pattern clearly.

Start with one recurring area of friction. Pick something concrete, such as monthly reporting, approvals, or how client or programme data gets updated and shared. Then map it from start to finish in plain English.

Where does work depend on memory? Where is information duplicated? Where do people have to bridge gaps manually between systems or steps? Where is ownership unclear? Where is one team member informally keeping the whole thing together?

This does not need to be a formal project. You are simply trying to see the bottleneck more clearly.

Once you can see it, the next decision is easier. You can work out whether the right response is to improve the process, clarify role ownership, add capacity, or make a selective change to tools.

If this is sounding familiar, a good next step is a simple operational signs checklist. It can help you work out whether you are dealing with a setup problem before assuming the issue is staffing or performance.

If useful, you can also explore our process improvement and ways of working support or read more on operations, reporting, and reducing manual work.