When the Work Depends on One Person
If the work only moves when one person is present, the problem is not commitment. It is structure.
A lot of good work is held together by one very capable person.
They know where everything is.
They remember what happens next.
They know who to call.
They know the password.
They know the workaround.
They know the thing that always goes wrong on Thursday.
And because they are good at what they do, the system appears to work.
Until they are gone.
Then everything slows down.
Questions pile up.
People wait.
Someone starts digging through old emails.
Another person texts the one person who was supposed to be off.
That is usually the sign that the work is not supported by a system yet.
It is supported by a person.
DEPENDABLE PEOPLE CAN HIDE BROKEN PROCESSES.
This happens easily in small teams.
Someone sees a need and steps in.
They figure out a process.
They improve it over time.
Before long, they are the person who knows how the whole thing works.
That can be a strength.
It can also become a problem.
Because knowledge that only lives in one person's head is hard to share.
A process that depends on memory is hard to repeat.
And a task that always has to pass through one person eventually becomes a bottleneck.
The goal is not to make people less important.
It is to make the work less fragile.
LOOK FOR THE REPEATED QUESTIONS.
One of the easiest ways to spot a weak system is to listen for the same questions.
Where is that file?
Who is handling this?
What do we do next?
Did anyone follow up?
Who has the login?
How did we do this last time?
If the same questions keep showing up, the problem may not be that people are not paying attention.
The information may simply not be easy to find.
That is a systems problem.
And systems problems usually need more clarity, not more reminders.
GET IT OUT OF YOUR HEAD.
A good place to start is simple.
Write it down.
Not a fifty-page manual.
Just enough for someone else to understand what happens next.
What needs to happen?
Who owns it?
Where does the information live?
What should happen if something goes wrong?
What is the next handoff?
The goal is not documentation for the sake of documentation.
The goal is to make the work easier to repeat.
If someone else can step in and keep moving without calling you six times, you are making progress.
SIMPLIFY BEFORE YOU DOCUMENT.
Sometimes the reason a process is hard to explain is because the process itself is too complicated.
If it takes ten steps, three text messages, two spreadsheets, and one person remembering a detail from six months ago, writing it down will not suddenly make it good.
Before you document the process, ask whether every step is necessary.
Can something be combined?
Can one person clearly own the next move?
Can information live in one place instead of four?
Can a recurring task become a checklist?
Can a decision be made once instead of every week?
A good system does not need to be impressive.
It needs to be clear.
ASSIGN OWNERSHIP.
One of the fastest ways for work to stall is when everyone assumes someone else has it.
A system should make ownership obvious.
Who is responsible for the next step?
Who makes the decision?
Who follows up?
Who knows when the work is complete?
Shared responsibility sounds collaborative.
In practice, it can easily become unclear responsibility.
A clear owner does not mean one person has to do everything.
It means someone knows the work is theirs to move forward.
TEST WHETHER IT ACTUALLY WORKS.
There is one simple test:
Can someone else run it?
Give the process to another person.
Do not stand beside them explaining every step.
See where they get stuck.
The places where they stop, hesitate, or need to ask a question are usually the places where the system is still depending on what you know instead of what the team knows.
Fix those places.
Then try again.
That is how a process becomes transferable.
THE GOAL IS NOT TO REMOVE PEOPLE.
This is where systems can get a bad reputation.
Good systems are not about turning people into machines.
They are not about removing judgment, creativity, or relationship.
They are about removing unnecessary dependence.
A good system gives people more room to do the work that actually needs them.
Instead of answering the same question every week, they can solve the next problem.
Instead of hunting for information, they can help someone.
Instead of rebuilding the process every time, they can improve it.
The system carries the repeatable part.
The person brings what only a person can bring.
MAKE THE WORK STRONGER THAN ONE PERSON.
There will always be people who carry a lot.
Every team has them.
But the healthiest version of that person is not the one who becomes impossible to replace.
It is the one who leaves the work clearer, stronger, and easier for someone else to carry.
So look at the things that always seem to run through one person.
The repeated questions.
The workarounds.
The information nobody else knows.
The tasks that stop when someone takes a day off.
Then start small.
Document it.
Simplify it.
Assign it.
Test it.
A good system does not make people less valuable.
It makes good work less dependent on one person carrying all of it.
If this was useful, Field Notes is where I share more of it.
Practical ideas on strategy, communication, systems, and helping good work go further.
