Every business has one.
Sometimes it’s the owner.
Sometimes it’s the office manager.
Sometimes it’s the employee who has been there forever.
The person everyone asks.
“When do we normally reorder that?”
Ask Sarah.
“Did anyone follow up with that customer?”
James usually does it.
“Who sends the figures at the end of the week?”
Mary knows.
“What happens after we receive this?”
Ask the boss.
And somehow, everything works.
Customers get called.
Orders get placed.
Problems get handled.
Reports appear.
People get reminded.
Things happen.
It can look remarkably like a functioning business system.
Except sometimes…
the system is actually a person remembering things.
Memory works beautifully—until it doesn’t
Human memory is extraordinary.
It’s also busy.
People are remembering customers, conversations, appointments, deadlines, family responsibilities, passwords, shopping lists and what they walked into the kitchen to get.
Yet businesses routinely add:
“Remember to check that every Tuesday.”
“Remember to call them after seven days.”
“Remember that this customer gets the special rate.”
“Remember to tell me when we’re running low.”
“Remember what we did last time.”
Usually, people do remember.
Until they’re busy.
Or distracted.
Or on holiday.
Or sick.
Or promoted.
Or they leave.
Then the business discovers something uncomfortable:
What looked like a process was actually knowledge living inside somebody’s head.
The dangerous sentence: “Only ___ knows how to do that”
There are certain sentences worth paying attention to in a business.
This is one of them:
“Only Jane knows how to do that.”
Jane may be fantastic.
That’s not the problem.
The problem is the word only.
If something important can happen only when one particular person is available, the business has created a dependency.
That dependency might remain invisible for years because the person is reliable.
In fact, the more reliable they are, the easier the problem is to miss.
They remember.
They fix things.
They answer everyone’s questions.
They quietly keep everything moving.
So nobody has much reason to question the arrangement.
Until Jane takes two weeks off.
Suddenly everyone realizes exactly how much of the business went on holiday with her.
Your most dependable employee shouldn’t have to be your backup system
There’s another side to this problem that businesses sometimes overlook.
Being the person who remembers everything isn’t necessarily a privilege.
It can become exhausting.
You can’t properly switch off because somebody might call.
You can’t take leave without preparing an enormous handover.
People interrupt you constantly because you’re the fastest route to an answer.
You become involved in tasks that shouldn’t really require you.
And because everyone depends on you, delegating becomes strangely difficult.
The business may interpret this as:
“We couldn’t survive without her.”
The employee may experience it as:
“Apparently I can never turn my phone off.”
That’s not resilience.
That’s dependency wearing a compliment.
A process shouldn’t disappear when a person does
People leave businesses.
That’s normal.
They change jobs.
They get promoted.
They relocate.
They retire.
They take parental leave.
They get sick.
Sometimes they simply take a well-deserved holiday.
A healthy business shouldn’t treat any of these ordinary events as an operational emergency.
That doesn’t mean everyone should be interchangeable.
People have experience, relationships, judgement and expertise that cannot—and shouldn’t—be reduced to a checklist.
But the basic ability of the business to function shouldn’t disappear because one person’s chair is empty.
The goal isn’t to make people less valuable.
It’s to make the business less vulnerable.
Systems don’t have to mean bureaucracy
Mention “business systems” and some people immediately imagine enormous procedure manuals.
Forms.
Policies.
Flowcharts.
Meetings about meetings.
That’s not what we’re talking about.
A system can be very simple.
It is simply a reliable way for something important to happen without depending entirely on someone remembering it.
The more important question is:
Does the business know what is supposed to happen?
And:
Could it still happen if the usual person wasn’t there?
If yes, excellent.
If not, you’ve found something worth examining.
“That’s just how we do it” isn’t quite a process
Businesses develop habits.
Over time, those habits begin to feel like systems.
“Every Friday I normally…”
“When that happens, I usually…”
“She generally checks…”
“I keep a note so I remember…”
There is nothing inherently wrong with any of this.
Informal processes are often exactly how young businesses get things done.
The problem appears when the business grows but the process doesn’t.
More customers.
More employees.
More locations.
More transactions.
More things to remember.
The same informal method that worked perfectly with two employees can become surprisingly fragile with twenty.
Growth doesn’t always create operational problems.
Sometimes it simply reveals the ones that were already there.
Try the Two-Week Absence Test
Choose an important person in the business.
Perhaps even yourself.
Then imagine they were unavailable for two weeks.
Not answering their phone.
Not checking email.
Not available for “just one quick question.”
What would happen?
Would customers still be looked after?
Would important work continue?
Would employees know what needed to happen?
Would someone know where important information was?
Would routine decisions still get made?
Would deadlines still be remembered?
Would the business know what had already been done—and what hadn’t?
Don’t use the exercise to judge the person.
Use it to examine the business.
Every time the answer is:
“We’d have to ask them…”
write it down.
That’s a dependency.
Pay particular attention to the owner
There’s an awkward version of this problem.
Sometimes the person the entire business depends upon is the business owner.
Everything comes through you.
Approvals.
Questions.
Customer issues.
Decisions.
Information.
Exceptions.
Employees may be perfectly capable, but the business has gradually learned:
When in doubt, ask the owner.
That can feel reassuring.
You know what’s happening.
You’re involved.
You’re in control.
But eventually the business reaches a strange point where the person most responsible for growing it is also the person preventing anything from happening without them.
That’s worth examining.
Because there’s a difference between:
being important to your business
and
being required for your business to function.
Those aren’t the same thing.
A business needs a memory of its own
Every business accumulates knowledge.
What worked.
What didn’t.
How things are normally handled.
Why a particular decision was made.
What customers expect.
What needs checking.
What happens next.
That knowledge is valuable.
But if it exists only inside individual people, the business doesn’t fully possess it.
The people do.
A stronger business gradually develops what we might call a business memory.
Not necessarily an enormous library of documents.
Simply enough shared understanding that important knowledge doesn’t vanish when somebody closes their laptop.
The objective isn’t to record everything anyone has ever learned.
It’s to protect the knowledge the business cannot afford to lose.
Don’t systemize the humanity out of the business
There’s an important balance here.
Not everything should become a rigid process.
A wonderful employee may know exactly how to calm a difficult customer.
A manager may recognize when someone on the team needs encouragement.
An experienced salesperson may instinctively know when to stop selling and start listening.
That judgement matters.
Businesses need people precisely because people can notice, interpret, adapt and care.
The objective isn’t to turn employees into machines.
It’s to stop using human beings as reminder systems.
Let people contribute judgement.
Experience.
Creativity.
Relationships.
Problem-solving.
Leadership.
And wherever possible, stop making the business depend on somebody remembering that Tuesday is the day we normally do that thing.
Try the “What Happens If They’re Away?” Audit
This week, listen for three phrases:
“Only ___ knows…”
“___ normally remembers…”
“We need to wait for ___…”
Every time you hear one, write it down.
Then ask:
How important is this to the business?
What happens if it doesn’t happen?
Could someone else continue if necessary?
Does the business know enough to carry on?
You don’t need to fix everything immediately.
Start with the dependencies where failure would cause the most disruption.
And remember:
The goal isn’t to eliminate valuable people.
It’s to make sure their value comes from what they contribute—
not from being the only person holding the business together.
Build a business that can remember without you
There’s a wonderful moment in the development of a business when the owner realizes something happened correctly…
and they weren’t involved.
The customer was helped.
The problem was handled.
The work got done.
The right decision was made.
Nobody called.
Nothing collapsed.
For some entrepreneurs, that can initially feel slightly unsettling.
Then you realize:
That’s not losing control.
That’s building a business.
A business becomes stronger when knowledge survives absence, responsibilities are clear and important work doesn’t depend entirely on someone’s memory.
People should be able to take holidays.
Employees should be able to grow into new roles.
Owners should be able to step away occasionally.
And the business should keep moving.
Because ultimately, a business shouldn’t just employ people who know how things work.
The business itself should know how it works.
Try the Two-Week Test
Choose yourself or one key member of your team.
Imagine they disappear from the business for two weeks.
No calls.
No WhatsApp.
No email.
No:
“Sorry to bother you while you’re away, but…”
Then ask:
What stops?
Those answers may tell you more about the strength of your business systems than any procedure manual ever could.
What does your business keep in someone’s head?
If there’s an important part of your business that depends too heavily on one person remembering, knowing or being available, that’s worth understanding.
You don’t need to design the solution.
Tell MakeBizEasy