When HR Lives in One Person's Head
- Bonnie Sims
- 2 days ago
- 3 min read
When nobody knows the why behind your HR processes, your business becomes more vulnerable than you think.
One of the most common patterns I see in growing companies starts the same way. Someone who has been "doing HR" leaves, and suddenly leadership realizes how much of the business depended on one person's knowledge. The systems still exist. The checklists are still there. But nobody knows why anything is done the way it is.
In one situation, the person handling HR had become the primary administrator for payroll, benefits, onboarding, background checks, and nearly every people system the company used. When they left, leadership discovered there were no backup administrators, no documented processes, and no one who understood why things had been set up the way they were.
The issue wasn't the person. It was the system. They'd built processes that worked, but the reasoning behind those decisions never left their head. When they left, the company didn't just lose a person. It lost the why.
The biggest risk is when nobody knows the why.
Across these situations, the conversations sound remarkably similar.
That's when the real problem becomes obvious. The issue isn't that processes exist. It's that nobody understands the reasoning behind them. When nobody knows the why, every decision becomes guesswork.
This is the cost nobody warns founders about. When HR evolves into "one more responsibility" for someone who was never expected to build an HR function, you don't get HR. You get a series of SOPs with no underlying logic. The process survives, but the purpose doesn't. Nobody knows the why anymore. And the second that person leaves, for any reason, good or bad, planned or not, the whole function evaporates. Because the why lived in their head, and now it doesn't live anywhere.
What It Actually Costs
The consequences are almost always the same. Vendor deadlines get missed. Employees have benefits questions no one can answer. Compliance issues surface. Leadership ends up spending days or weeks untangling systems instead of running the business.
What's striking is that this doesn't require a messy departure. Most of the time, these transitions are completely professional. People give notice, document what they can, and genuinely try to help. Even then, there simply isn't enough time to transfer years of institutional knowledge. If someone leaves unexpectedly, the risk only grows.
What "Trained HR" Actually Gives You
People often assume the difference between "someone who does HR" and a trained HR professional is experience or personality. It isn't. It's understanding the why behind every process. That's the difference. A trained HR professional doesn't just know what to do. They know why it's done that way, when to make an exception, and when the process itself needs to change.
A trained HR person knows why I-9 verification works a certain way, because there are federal requirements about who can verify, when, and how, and getting it wrong creates real exposure in an audit. A person without HR training just knows "we do it like this."
A trained HR person knows why benefits enrollment has hard deadlines, because carriers have contractual cutoffs, and missing the window means an employee goes without coverage for a full plan year. A person without HR training just knows "we do it every November."
A trained HR person knows what questions to ask when something weird shows up, because they've seen it before, or they've been trained to look for it. A person without HR training does their best with what's in front of them.
That's not a character flaw. That's a training gap. And founders who treat those two things as interchangeable are making a bet they don't realize they're making.
The good news is this problem is fixable.
I've helped companies rebuild HR infrastructure after transitions like these, documenting processes, establishing backup ownership, and, most importantly, capturing the reasoning behind every decision so the function no longer depends on one person.
Every leader I've worked with has said some version of the same thing afterward: "I wish we'd done this sooner." That's the real lesson. You don't build resilient HR after someone leaves. You build it before they do.
Processes can be documented. Context has to be intentionally transferred. That's the difference between having someone do HR and having an HR function that can survive change.
Founders often think the biggest HR risk is compliance. It isn't. The biggest risk is waking up one day and realizing nobody knows the why anymore. If you're a founder reading this and any of it is hitting close to home, don't wait for the wake-up call. The wake-up call is the worst possible time to discover the gap.