Why systems matter, but people matter more
.jpg)
Growth sounds exciting on paper—and it is! In practice, it also brings a lot of spreadsheets, vendor calls, compliance reviews, and very human questions.
I work for a rapidly growing healthcare company, and we acquire, on average, two to three sizable groups per quarter. My role is to lead HR integration across those acquisitions. From payroll and benefits transitions to retirement plan mergers or terminations, employee handbook alignment, and training managers through the change, my team has navigated it all. It’s operational and technical, but it’s also deeply relational work.
If you’ve ever been part of an integration, you know it’s equal parts structure and improvisation. Over time, a few lessons have stuck with me.
If there’s one thing I feel strongly about, it’s this: build the plan.
It won’t stay perfect. It won’t survive untouched. But you need it.
Integrations move fast. You’re coordinating with finance, IT, legal, and operations. You’re aligning payroll timelines, confirming benefit effective dates, evaluating retirement plan options, updating policies, and drafting communications. There are lots of moving pieces, and ambiguity compounds quickly.
I rely heavily on RACI frameworks. Not because I love process for process’ sake, but because clarity reduces stress.
Distinguishing each person’s role in the project matters when timelines tighten or the unexpected surfaces, which it inevitably will. Close dates shift. You discover that the legacy practice has been handling eligibility differently than expected. An individual employee situation requires an exception. A system constraint changes your sequencing.
The plan gives you a baseline and creates shared expectations. When you do need to pivot, you’re pivoting from alignment, not chaos.
The smoothest integrations I’ve led weren’t the ones where nothing went wrong. They were the ones where everyone knew their role well enough to adjust quickly.
In an acquisition-heavy environment, vendors aren’t background players. They’re in the trenches with you.
Your payroll provider. Your benefits broker. Your retirement advisor. These partners can make integration feel either coordinated or incredibly reactive.
When you’re merging or terminating retirement plans, navigating ERISA requirements, aligning eligibility, or managing compressed enrollment windows, you need more than technical competence. You need responsiveness and sound judgment.
Not every vendor thrives in M&A. Some are fantastic at steady-state administration but struggle when timelines are fluid and information is incomplete. Integration work requires flexibility and a willingness to problem-solve in real time.
I’ve learned to vet partners differently. I ask about their acquisition experience and how they manage transitions when data is messy. I pay attention to how proactive they are in communication.
Price matters, but partnership matters more.
The best vendors I’ve worked with anticipate employee questions before we even draft the communication. They flag risks early. They help me think through not just what’s compliant, but what’s practical.
When you’re acquiring multiple groups per quarter, that level of partnership isn’t a luxury. It’s essential.
There’s a particular kind of pressure that comes with HR integration. You’re responsible for things that deeply affect people—their pay, their healthcare coverage, their retirement savings. The stakes feel high because they are.
It’s easy to start carrying everything.
What’s helped me is getting clear on what’s within my control.
I can create processes that work. I can build repeatable checklists. I can document decisions. I can create structured project plans with tools like Asana or Smartsheets. I can standardize communication templates so we’re not reinventing the wheel every quarter.
Strong internal systems create breathing room. They reduce decision fatigue. They make growth feel manageable instead of overwhelming.
What I can’t control? Every system limitation. Every regulatory nuance that pops up mid-process. Every emotional response to change.
Early on, I took those things personally. If something felt messy, I assumed I had missed something. Over time, I’ve realized that some messiness is inherent in growth. By definition, integration is a transition. And transitions are rarely perfectly tidy.
Letting go doesn’t mean lowering the bar. It means recognizing the difference between ownership and over-responsibility. In turn, that allows for sustainability, which matters just as much as execution when you’re running at this pace quarter after quarter. This work is a marathon, and you don’t serve your organization or the employees you’re integrating if you’re running on empty.
It’s easy to frame integrations as operational projects, but they’re also trust-building moments.
Behind every payroll conversion is an employee hoping their paycheck lands correctly. Behind every benefits transition is a family making decisions about coverage. Behind every handbook update is a manager trying to lead confidently through change.
For many employees, the integration process is their first real experience with your organization’s culture. Are you organized? Are you transparent? Do you communicate clearly? Do you follow through?
Those signals matter.
I’ve come to see HR integration not just as a logistical exercise, but as a foundational one. Done well, it builds credibility. It reassures people that even in the middle of change, there is thoughtfulness and care.
In high-growth healthcare environments, change isn’t slowing down. But the way we manage it by creating clarity, building partnerships, and modeling steadiness shapes what that growth feels like.
So , have the plan. Choose strong partners. Build good systems. Take care of yourself.
Also remember: Every checklist item represents a person on the other side of it. That’s the part of integration work that makes it worth doing well.