When Only One Person Knows How It Works
1. Introduction
“Ask Sarah.”
That was the answer to everything.
How do we process this order?
Ask Sarah.
Why does this report show a different number?
Ask Sarah.
What happens when this customer has an exception?
Ask Sarah.
Then Sarah went on leave.
Suddenly...
Nobody knew.
The process was running.
But the knowledge wasn't inside the process.
It was inside Sarah.
2. Problem
Every organization has experienced people.
That is valuable.
The risk begins when important operations depend entirely on what one person remembers.
The special rule.
The workaround.
The customer exception.
The reason something is done differently.
None of it is documented.
The employee becomes the system.
3. Explanation
This creates a hidden single point of failure.
Everything works while that person is available.
Then they take leave.
Change roles.
Resign.
Or simply forget.
Suddenly the organization discovers how much operational knowledge was never captured.
The problem isn't having experts.
The problem is making expertise impossible to transfer.
4. Practical Example
A production planner has managed the same customer for eight years.
She knows that Product A cannot run after Product B.
She knows one customer accepts partial deliveries.
She knows which machine performs better for certain jobs.
None of these rules exist in the system.
A new planner takes over.
The data is available.
The procedures are available.
But the decisions are different.
Why?
Because the most important knowledge left with the previous planner.
5. AxTrace Perspective
Operationally mature organizations preserve more than data.
They preserve context.
What decision was made?
Why was it made?
What evidence supported it?
What exception applied?
Who made the decision?
When operational knowledge becomes traceable, experience can become organizational knowledge instead of remaining individual memory.
6. Key Takeaway
If only one person knows how the process works, you don't have a process.
You have a dependency.
7. FAQ
1. What is key-person dependency?
It occurs when important knowledge or processes depend heavily on one individual.
2. Why is undocumented knowledge risky?
Because it can disappear when employees leave, change roles, or become unavailable.
3. Does documenting procedures solve the problem?
It helps, but procedures alone may not capture exceptions, decisions, and the reasoning behind them.
4. How can organizations preserve operational knowledge?
Capture important decisions, evidence, exceptions, ownership, and reasoning as part of everyday operations.