Why workarounds can hide operational problems

From a leadership seat, things can look broadly fine.

Reports go out. Deadlines are met. Staff keep work moving. Nothing is visibly failing.

But sometimes that apparent stability depends on people quietly filling gaps every day.

Someone is chasing updates across email and chat. Someone else is correcting figures before a report goes out. A team member is remembering exceptions the process does not handle well. A separate spreadsheet exists because the main system does not quite reflect how the work actually happens.

What leadership usually sees is the output. What is easier to miss is the extra human effort holding it together.

This is not about blaming staff, and it is not a case for a major overhaul. It is about noticing a common pattern: workarounds can hide weaknesses in the way work is set up. If a process only works because people are constantly patching the gaps, it may be less reliable than it appears.

When things look fine on the surface

Small nonprofits and small organisations are often very good at coping.

When something does not quite work, people find a way around it. They keep a side spreadsheet. They send reminder messages. They check numbers manually. They hold key details in their heads because putting them into the formal process takes too long or does not match the reality of the work.

That can make an organisation look steadier than it really is.

From the outside, the funder report is submitted on time every quarter. Client or service data looks current enough. Finance, programmes, and leadership all receive the information they need.

Underneath, that result may depend on repeated follow-ups, manual reconciliations, separate notes, and informal clarifications every month.

The risk is not always immediate failure. More often, it is hidden strain.

Leadership sees that the work is getting done, so the setup can seem acceptable. Meanwhile, the real operating model may depend on one or two people doing the extra chasing, fixing, and remembering that stop things from slipping, a sign that operational growing pains may be turning into a deeper problem.

What this often looks like in practice

This pattern is usually easy to recognise once you start looking for it.

Staff may be chasing updates across email, chat, spreadsheets, and conversations because no single place reliably holds the full picture. The formal process exists, but people do not trust it enough to rely on it on its own.

The same people may be fixing data repeatedly, checking versions, filling gaps, or translating between how work is supposed to happen and how it actually happens.

A funder report may go out on time every quarter, but only because one staff member manually pulls figures from several spreadsheets and fixes inconsistencies before submission.

Client data may appear up to date, while frontline staff keep separate notes and reminder systems because the main setup does not fit day-to-day service delivery.

Finance, programmes, and leadership may all get the monthly information they need, but only after repeated follow-ups, manual checks, and back-and-forth clarification.

None of this needs to look dramatic to matter.

There may be no visible crisis. But handovers feel risky. New staff take longer to get up to speed. Progress depends too much on specific individuals. If one person is away, confidence in the process drops quickly.

That is often the point where it becomes worth asking whether the organisation is running on a dependable setup, or on accumulated workarounds.

Why this can be misleading

A process is not necessarily healthy just because the output appears on time.

If work succeeds because people are compensating for missing steps, unclear ownership, inconsistent data, or a process that does not fit the real work, then the reliability is coming from people rather than from the setup itself.

This is what makes workarounds easy to miss.

Capable staff absorb the weakness before it becomes visible. They spot the mismatch. They reconcile the numbers. They send the reminder. They remember the exception. They re-enter the detail where it is actually needed.

From leadership level, that can create the impression that the process is basically working.

In reality, the process may only be working because staff are carrying the gaps manually.

That matters because hidden weakness often stays hidden until something changes. A key person leaves. Someone is off sick. Two deadlines land at once. The organisation grows. A funder asks for data in a different format. Suddenly the workaround is no longer enough.

The issue here is not staff performance. In many cases, the staff involved are the reason the organisation still looks stable.

The issue is the design of the work.

If the same gaps have to be patched repeatedly, the problem is usually not that people are failing. It is that the process, handoff, ownership, or setup is asking people to do too much invisible repair work.

How to tell whether the problem is people, process, or setup

This is often where leaders get stuck.

If work feels fragile, it can be hard to tell whether the issue is a person, a tool, a process, the data, or simply the normal complexity of a small organisation.

A useful starting point is to look at where the extra effort sits.

If one person has to keep reminding everyone, checking exceptions, or stitching information together, that usually points to a process or setup weakness rather than individual underperformance.

If errors keep reappearing in the same places even when conscientious staff are involved, that is another sign of a structural issue. The workflow, handoff, or source information is not doing enough of the work.

If people are regularly copying information from one place to another, checking whether a version is current, or relying on side conversations to confirm what should happen next, the setup is probably not carrying its share of the load.

One simple test is this: if the key person who does the extra chasing and remembering stopped doing it for two weeks, would the process still hold up?

If the honest answer is no, that tells you something useful.

It does not mean the organisation is failing. It means the apparent stability depends on manual support that may not be visible until it disappears.

That is the difference between a process that is a bit imperfect but basically sound, and one that is quietly fragile.

If that question brings reporting to mind, this piece on When reporting depends too much on one person explores that pattern in more detail.

A simple self-check

If you want to test this without turning it into a major project, pick one routine process that seems to work reasonably well.

Choose something ordinary: a monthly report, a funder update, a client follow-up process, an approvals flow, or the way information moves between programmes and finance.

Then ask a few plain questions.

Where are people manually checking, correcting, reminding, or keeping separate notes to make this succeed?

Where does follow-up depend on someone remembering rather than on a clear handoff?

Where are duplicate trackers, exception lists, side spreadsheets, or unofficial notes doing work that the formal process is not doing?

Where does reporting depend on last-minute clean-up rather than information being usable as it goes?

And where would the process slow down or break if one specific person was not there to patch the gaps?

Many organisations look stable in leadership meetings because the outputs are still arriving. But when you look more closely, there are often one or two staff quietly doing the extra chasing, fixing, and remembering that keep everything moving. The organisation is coping, but coping is not the same as having a healthy setup.

That distinction matters. It helps you spot when “good enough” is really manual effort masking a weakness in the process or setup.

If this feels familiar, the most useful next step is usually a short diagnostic rather than a big solution exercise. Start by clarifying the pattern before deciding what needs to change. The articles in Spot the real problem are a good place to do that.

If, after that, you want to look at proportionate ways to reduce the manual glue work, Affordable automation for non-profits outlines practical options without assuming technology is the first answer.