What messy HR functions usually have in common
Lessons from inheriting more than a few HR functions, and why the fix is almost always infrastructure, not effort.
Over the course of my career, I've inherited more than a few HR functions that could politely be described as messy.
The reasons vary. Sometimes the company grew faster than its infrastructure could keep up. Sometimes HR was handled by whoever had capacity at the time.
How HR functions usually get here:
Fast growth
HR by whoever had capacity
Turnover
Leadership changes
A new HR system
A new broker
Years of layered processes
From the outside, things usually looked fine. Employees were getting paid, benefits existed, people were being hired, and there was an employee handbook somewhere.
But once I started pulling at the threads, it became clear how much was being held together manually.
After seeing the same pattern again and again, I've come to one conclusion:
Messy HR functions usually aren't messy because people didn't care. They're messy because the organization changed faster than the infrastructure supporting it.
Everything lives in someone's head
There's almost always one person who knows everything. That works right up until that person leaves, gets overwhelmed, or simply isn't available.
What that one person usually knows:
Payroll deadlines
Benefit exceptions
The approval process
State-specific requirements
Offer letter templates
Who still needs cleanup
If you can't answer "What happens when X occurs?" without naming a specific person, that process needs to be documented.
Good HR infrastructure shouldn't depend on someone having a great memory.
The systems exist, but the process is still manual
A company can have an excellent HRIS and still manage half of HR through spreadsheets, emails and workarounds. Workflows were never built. Integrations were never finished. Permissions are inconsistent and the data is messy. People keep working outside the system because that's how it's always been done.
Technology doesn't fix a bad process.
Sometimes a new system really is needed. But more often, the bigger opportunity is configuring the tools you already have correctly and eliminating the manual work that has piled up over time.
Compliance gets handled one problem at a time
This is especially common in growing multi-state organizations. A company hires in a new state, then another, then five more. Someone updates payroll. Someone else handles leave. A policy gets added whenever an issue comes up.
Eventually there are employees across multiple jurisdictions, and no one has stepped back to look at the full picture.
What you start finding:
Outdated policies
Incomplete I-9s
Classification concerns
Inconsistent leave practices
Missed state requirements
Usually, no single decision created the problem. It built up gradually.
The company outgrew its processes
Many HR processes were never "bad." They were simply designed for a much smaller organization.
The onboarding process that worked for 20 employees may not work for 100. The manager practices that worked when everyone knew each other can fall apart as the company scales.
Growth exposes processes that were never built to scale, and the answer isn't always more people. Often it's better processes, better systems, clearer ownership and less manual work.
Stabilize before you strategize
There's a lot of conversation in HR about being strategic, and HR absolutely should be strategic. But sometimes the most strategic thing you can do is fix payroll.
Or clean up employee data. Correct benefit enrollments. Rebuild onboarding. Figure out why managers are handling the same situation five different ways.
You can't build sophisticated people strategies on top of unstable operations.
My approach is simple:
Stabilize. Address whatever is affecting employees and the business today.
Correct. Fix the underlying process, system or compliance issue.
Build. Put the infrastructure in place that keeps you from ending up here again.
Good HR infrastructure is usually pretty boring
Some of the most impactful HR work isn't flashy.
The unglamorous work that changes everything:
Documenting processes
Standardizing templates
Cleaning up workflows
Creating approval structures
Building pay grades
Automating repetitive work
Clarifying ownership
Consistent manager guidance
None of that sounds revolutionary. But together, it changes how an organization operates.
HR spends less time chasing problems. Managers get clearer guidance. Employees get more consistent answers. Leadership gets better information. And HR finally has room to focus on bigger priorities.
The goal isn't to create more HR. It's to create HR that works.
The bottom line
Most messy HR functions aren't beyond repair. They're usually the result of a company growing, changing or moving quickly without rebuilding the infrastructure underneath it.
That's the work I enjoy most.
Is your HR function being held together manually?
Linka Consulting helps growing organizations identify what isn't working, then actually build the systems, processes and infrastructure to fix it.
Stabilize what's urgent. Correct what's underneath. Build what lasts.
Comments