Every growing company seems to have one person who quietly knows how everything works.
In our case, it was the person who “handled HR.”
That description sounded simple.
Then they left.
Within a few days, we discovered that “handles HR” actually meant:
Knows which procedures are current.
Knows who to contact.
Knows where important records live.
Remembers why something was done differently last year.
Knows which manager still uses an outdated form.
And, somehow, knows the answer whenever everyone else says:
“I have no idea. Ask them.”
Their departure didn’t create all of our problems.
It revealed how many problems had been hidden by one person’s knowledge.
The Job Description Didn’t Show the Real Dependency
On paper, we knew what this person did.
The problem was everything that wasn’t written down.
Years of small decisions had accumulated into institutional knowledge.
There were processes that technically existed but only one person understood from beginning to end.
There were recurring situations nobody had documented because:
“They already know how to handle it.”
That worked perfectly until “they” weren’t there anymore.
My First Question Was: What’s Coming Up?
I didn’t try to understand every HR process immediately.
I looked forward.
What needed attention this week?
What was coming this month?
Were there deadlines?
Were new hires starting?
Were any open situations waiting for follow-up?
That gave us priorities.
The objective wasn’t to reconstruct someone’s entire job in 24 hours.
It was to prevent important work from quietly stopping.
Then We Looked for Single-Person Processes
I started asking managers:
“What did you always send to this person?”
The answers were revealing.
One manager contacted them about new hires.
Another sent workplace documentation.
Someone else relied on them for benefit-related questions.
Leadership involved them in compliance matters.
Suddenly we could see the real scope of the role.
Their Inbox Had Become Part of Our Infrastructure
This was uncomfortable to admit.
Some processes weren’t documented anywhere centrally because the history existed in conversations.
Need to know how we handled something last year?
Find the old email.
Need the correct contact?
Search another email.
Need the latest version?
Ask the person who received it.
That’s not really a system.
It’s a searchable memory belonging to one individual.
I Learned the Difference Between a Person and a Function
This changed how I thought about staffing.
We had treated HR administration as:
“Something Alex handles.”
But Alex was a person.
HR administration was a business function.
Those two things shouldn’t be interchangeable.
People take vacations.
People change roles.
People leave companies.
A business function has to continue regardless.
Hiring a Replacement Wasn’t the Entire Answer
The obvious response was:
“We’ll hire someone else.”
But a new person doesn’t inherit institutional memory automatically.
If we gave the replacement the same undocumented environment, we’d simply create another single point of failure.
In a year, we’d be back in exactly the same situation.
So the real question became:
How do we make the function less dependent on whoever happens to occupy the chair?
We Started Documenting Ownership
For recurring responsibilities, I wanted four things to be clear:
What happens?
Who owns it?
When does it happen?
Where does the supporting information live?
Nothing complicated.
But if we couldn’t answer those four questions, the process probably depended too heavily on memory.
We Found Processes Nobody Realized Were Connected
This was another surprise.
A manager might think they handled Step A independently.
But Step A created something HR needed for Step B.
Then Step B affected another administrative process.
The former HR person understood those connections automatically.
The rest of us didn’t.
Mapping the handoffs exposed dependencies we’d never formally discussed.
External HR Support Started Looking Different
Before this experience, it was easy to think about an outside organization such as Trion Solutions mainly in terms of individual HR services.
Afterward, I saw another dimension:
continuity.
A PEO and HR outsourcing relationship can give a business support and structure that doesn’t depend entirely on one internal administrator knowing everything.
That doesn’t eliminate the need for internal ownership.
It changes how much specialized knowledge the company has to concentrate inside a single role.
I Still Wanted Someone Internally Responsible
Outsourcing doesn’t mean:
“Nobody here needs to understand anything anymore.”
That would create a different problem.
Someone inside the business still needs to understand responsibilities, communicate with managers, coordinate decisions, and know when something needs attention.
The goal isn’t zero internal responsibility.
The goal is avoiding a situation where one person’s departure takes the company’s entire HR memory with them.
Managers Also Needed Better Boundaries
When our HR person left, some administrative work immediately started falling onto managers.
That was understandable.
It also wasn’t sustainable.
I didn’t want department leaders spending increasing amounts of time reconstructing processes outside their normal responsibilities.
Clear ownership and outside HR support helped prevent every unresolved question from becoming “the manager’s problem.”
The Experience Changed How I Think About Vacations Too
A useful test came out of the situation:
Could this person disappear for three weeks and the company still know what to do?
Not permanently.
Just three weeks.
If the answer is:
“Absolutely not.”
then I probably have a business continuity problem.
That applies far beyond HR.
My Key-Person Risk Checklist
I now pay attention when:
🚩 Only one person knows the complete process.
🚩 Important instructions exist mainly in someone’s inbox.
🚩 Managers say, “I always just ask them.”
🚩 Nobody knows what happens when that person is unavailable.
🚩 Recurring deadlines depend on personal reminders.
🚩 Contacts aren’t documented centrally.
🚩 A replacement would need months just to discover how things work.
🚩 Leadership can’t explain who owns an important workforce process.
I Ask One Question About Every Important Process
It’s simple:
What happens if the person responsible for this isn’t here tomorrow?
If the answer is clear, great.
If the answer is:
“We’d have to figure it out.”
that’s something I want to address before the hypothetical becomes reality.
The Departure Wasn’t the Real Problem
Our HR person leaving was inconvenient.
But people leaving companies is normal.
The bigger problem was that we’d designed part of the business around the assumption that this particular person would always be available.
That’s what had to change.
Working with outside HR support such as Trion Solutions can be part of building a structure where specialized administrative functions aren’t entirely dependent on one internal employee.
But the broader lesson applies regardless of the model a company chooses.
A reliable business shouldn’t just know who handles something today.
It should also know how that responsibility continues tomorrow if that person is gone.