In a small team, it can be easy to miss this at first.
The work gets done. Reports go out. Payroll happens. Invoices are sent. Volunteer or client follow-up keeps moving. But underneath that, one experienced person is carrying a lot in their head.
They know the deadlines, the exceptions, the relationships, the file locations, the reporting steps, and the unwritten rules. Other people check with them before they act. When they are away, work does not stop completely, but it becomes slower, less certain, or easier to get wrong.
If you are a CEO or Executive Director, you may recognise the strain without being fully sure what to call it. Is this just normal for a small organisation? Is it a staffing issue? A documentation gap? A training problem?
Often, the clearest diagnosis is simpler than that: important work depends too much on one person’s memory and informal rescue work.
That does not mean the person is the problem. It means the way the work is set up relies too heavily on what they know, remember, and quietly fix. That is an operational design issue, and it is common.
When “we’d be stuck if they were off for a week” starts to sound normal
Most leaders recognise this sentence straight away:
“We’d be stuck if X was off for a week.”
It is often said as a compliment. And often it is one.
But it can also point to a process that is not visible enough yet.
If routine work becomes risky, confusing, or slow when one person is unavailable, that usually means something important is being carried by memory rather than by a shared way of working.
You might notice signs like these:
- people pause until one person confirms the next step
- deadlines are tracked in someone’s head or personal calendar rather than a shared system
- routine tasks depend on someone knowing the “usual way” to handle exceptions
- work slows down when that person is on leave, in meetings, or overloaded
- staff say things like “just ask Sarah” or “Tom will know where that is”
None of this means your team is failing. It usually means the organisation has grown around habit and experience, and some important parts of the work have never been made fully visible.
What this looks like day to day
This pattern rarely shows up as a major crisis to begin with. More often, it appears in ordinary moments.
A staff member wants to submit something but checks with the same colleague first because they are not sure which spreadsheet is current.
A report is based on existing data, but only one person knows where the figures are kept, which numbers can be trusted, and how to reconcile differences when two reports do not match.
Payroll or invoicing gets done each month, but smoothly only because one person remembers the exact sequence, the exceptions, and a deadline that is not clearly tracked anywhere.
Client, service user, or volunteer coordination keeps moving because one experienced team member remembers preferences, follow-ups, and unwritten steps that are not recorded anywhere others can see.
From the outside, the work can look stable. But that stability is often coming from repeated acts of remembering, checking, chasing, and correcting.
Common signs include:
- the same person is regularly asked where files live, what to do next, or who needs to approve something
- important steps happen through inbox searching, personal reminders, and habit rather than a visible process
- handoffs are informal, so follow-up depends on someone remembering rather than a clear trigger
- other staff hold back until they can check exception rules with one person
- when that person is away, others spend time guessing, waiting, or piecing together what usually happens
The bottleneck is not always the software. Often it is the hidden knowledge around the work: what counts as complete, what to do when a case is unusual, where the reliable source of truth is, and which checks prevent errors.
The issue is not the person. It is work that relies on memory.
In plain English, this kind of dependency means critical work has been built around personal memory instead of a shared, reliable process.
That can happen gradually.
In a small organisation, work often evolves under pressure. A report is needed quickly, so someone creates a workaround. A spreadsheet gets patched because the original version no longer fits. A finance or funding task passes from one person to another without being fully explained. An exception comes up often enough that one experienced staff member simply starts handling it from memory.
None of that is unusual.
The problem is that, over time, the real process becomes harder to see. What officially exists and what actually happens start to drift apart.
Then important work begins to rely on things like:
- remembered deadlines
- known exceptions
- personal file maps
- unwritten approval routes
- informal checks before submission
- knowledge of which data can be trusted
- relationships that sit with one person rather than in the workflow
At that point, you are not just relying on a capable colleague. You are relying on knowledge that has never been made properly shared.
How to tell whether this is staffing, training, or process design
These problems can look similar from the outside, so it helps to separate them.
If one person is overloaded, that does not automatically mean the process is the problem. And if others keep asking questions, that does not automatically mean they need more training.
A few distinctions can help.
It may be a staffing or capacity issue if
The work is already fairly visible.
The steps are clear. The deadlines are known. Files are easy to find. Someone else could pick the work up without too much detective work, but there is simply too much volume sitting with one person.
In that case, the main pressure point is capacity.
It may be a training or onboarding issue if
The process exists and is reasonably clear, but newer or less confident staff do not yet know it well enough to act independently.
They may still need support, practice, or reassurance, but the work itself is not hidden.
In that case, the issue is more about transfer than design.
It is likely a process design issue if
The work depends on one person to remember timing, interpret exceptions, locate the right files, explain what normally happens, or catch mistakes before they go out.
That usually means the process is not doing enough of the work.
A useful test is this: if that person were unexpectedly unavailable for a week, would someone else be able to follow the work with reasonable confidence?
If the answer is no because too much sits in that person’s head, you are probably looking at a process problem first.
If you want to separate a tool problem from a process problem more clearly, this may help: Tool vs process: how to tell what’s causing the friction.
That distinction matters because the wrong diagnosis leads to the wrong fix.
If you treat a hidden-process problem as a staffing issue, you may add capacity without reducing the risk.
If you treat it as a training issue alone, you may train people into a process that is still unclear, inconsistent, or dependent on unwritten exceptions.
What to look at first
You do not need to start with a full redesign.
The most useful first step is usually to choose one recurring area of work that becomes fragile when one person is absent.
That might be:
- funding or impact reporting
- payroll, invoicing, or finance admin
- approvals and sign-off flows
- volunteer or service user coordination
- routine cross-team coordination where follow-up is easy to miss
Pick one area where the risk is easy to observe.
Then look at what that person is actually holding together.
Not their job title or how hard they work. The practical things they are remembering and resolving.
For example:
- deadlines no one else can see clearly
- decision rules that exist only as habit
- file locations or naming conventions others do not understand
- exceptions that always need the usual workaround
- relationships or contact details that are not recorded in the process
- checks that catch errors before something is submitted or approved
- handoffs where the next step only happens after someone asks what to do
This is often where the real pattern becomes clearer.
The problem is not simply that one person knows a lot. It is that memory is doing work that the process should be doing.
If reporting is one of the areas where this shows up, Signs your reporting process is held together by workarounds gives some useful examples.
A simple next step
If this feels familiar, it can help to do a quick check of where your organisation is relying on memory rather than shared process.
That can help you get clearer on:
- what is normal in a small team and what is becoming a real risk
- whether the issue looks more like staffing, training, or hidden process
- which area of work to look at first
- where deadlines, handoffs, checks, and exceptions are still living in someone’s head
It does not need to be a big systems exercise. The aim is simply to see the pattern more clearly so you can reduce the risk, one area at a time.
Want to get started today? Use this quick self-check to see where work is quietly depending on one person to remember everything.
