“We thought the vendor was doing that.”
It’s a phrase we’ve heard more than once during HR system implementations.
Not because anyone was avoiding responsibility. More often than not, it’s because nobody realised there was a responsibility to assign in the first place.
When organisations plan an HR system implementation, most of the focus naturally goes on selecting the right technology, agreeing timelines and planning the rollout. What sometimes gets overlooked is one of the biggest factors in determining whether a project runs smoothly: being crystal clear about who owns what.
In our experience, the projects that stay on track aren’t necessarily the ones with the biggest budgets or the most sophisticated systems. They’re the ones where everyone involved understands their role from day one.
Why responsibility gaps happen
A typical implementation might involve HR, Payroll, IT, Finance, managers, system administrators, the software vendor and sometimes an external implementation partner.
With so many people involved, it’s easy to assume that someone else is taking care of a particular task.
The problem is that many implementation activities sit in the space between teams.
- Who is responsible for checking the quality of employee data before migration?
- Who decides how a process should work in the new system?
- Who signs off testing?
- Who approves changes to scope?
- Who communicates updates to the wider business?
If these responsibilities aren’t agreed early, projects can quickly slow down because of confusion, duplication, or unexpected gaps.
1. Define ownership, not just involvement
One of the most common mistakes we see is confusing participation with accountability.
Just because someone attends a workshop doesn’t mean they’re responsible for the outcome.
For every major activity, it’s worth asking four simple questions:
- Who owns the decision?
- Who provides input?
- Who signs it off?
- Who is responsible for getting it done?
This applies across the entire project, from data migration and process design through to testing, training and communications.
A responsibility matrix can be useful, but the format matters less than the conversation itself. The important thing is making sure everyone leaves the discussion with the same understanding.
“If this task doesn’t happen, who would be accountable?”
If the answer isn’t immediately obvious, that’s usually a sign that more clarity is needed.
2. Be clear about where the vendor’s responsibilities end
This is where many organisations get caught out.
It’s natural to assume that because you’re paying a vendor to implement the system, they’ll take care of everything.
In reality, implementation is a partnership.
The vendor brings expertise in the technology. Your team brings expertise in your organisation.
The vendor might configure workflows, but they can’t decide how your business should operate.
They can migrate data, but they can’t always determine whether that data is accurate.
They can recommend best practice, but they can’t make business decisions on your behalf.
The most successful projects are the ones where these boundaries are discussed openly before the project starts.
A good implementation partner should be able to explain:
- What they are responsible for
- What your team is responsible for
- Where responsibilities overlap
- Which project activities need active involvement from internal stakeholders
Those conversations can save a lot of frustration later on.
3. Agree how decisions will be made
Ask anyone who’s been involved in a delayed implementation and they’ll often tell you the technology wasn’t the issue.
The challenge was decision-making.
Requirements can’t be agreed. Different stakeholders want different outcomes. Approvals take longer than expected. Nobody is quite sure who has the final say.
Before kick-off, it’s worth agreeing:
- Who approves key decisions
- Who can authorise changes to scope
- How disagreements will be resolved
- What escalation routes exist
- How quickly decisions are expected to be made
The goal isn’t to create layers of governance; it’s to avoid situations where important decisions sit idle because nobody knows who owns them.
The most successful implementations share one thing
Successful HR system implementations aren’t just well planned.
They’re well owned.
When responsibilities are clear, data gets prepared more effectively, decisions happen faster, risks are identified earlier and everyone understands what’s expected of them.
The technology still matters, of course.
But before focusing on configuration, integrations and go-live plans, it’s worth taking a step back and asking a simpler question:
Does everyone involved know exactly what they’re responsible for?
If you are preparing for your project and are worried about how you will be able to resource all of the elements you and your team need to own, speak with the ReThink HR team as this is the work we do with our clients day in and day out. We know the questions to ask, ways to document so all are clear and can provide additional capacity by acting as an extension of your team.
Recent Comments