Payroll data and processes reach far and wide into an organization, so the decision to change payroll and HCM systems is not a small one.
Organizations spend a lot of time and money to just evaluate such a change, and when faced with risk, they often choose status quo — why change if the current process works most of the time and the organization has found workarounds for when it doesn’t?
The problem is that the status quo doesn’t account for operational erosion. Your business isn’t static, so operational processing has to adapt to support changes, and this often leads to inefficiencies.
But before operational erosion gets to the point of breaking, you can fortify your processes and infrastructure through payroll and HCM change.
To get started, you'll need:
- A solid understanding of your current system, infrastructure, and processes
- Open channels of communication with all stakeholders
- Definitive answers to questions from supporters and dissenters alike
Step 1: Consideration
Before beginning any payroll and HCM system change, first make sure your organization has fully taken stock of all the possible impacts. Here are examples of some of the checks to assess across your organization:
- Does your current payroll provider match your HCM system?
- What payroll data exists in your HCM today?
- Do you have bank details?
- Are organizational structures loaded?
In-country provider status
- When do your current in-country provider contracts expire?
- How tight are the terms of the current contracts?
- Are there exits?
- What special conditions are in the agreements?
- What specialized, per-country knowledge does current staff have for which you may have to account?
- What unique workflows have evolved that may not be part of the existing documented process
- What is the impact on processes and workflows for HR, payroll and finance teams?
Step 2: Pre-launch
Once you’ve prepared your data and infrastructure, you can turn your full attention to your people. A key part of this step is communication. The more you proactively communicate and actively solicit and incorporate feedback from stakeholders across the organization, the more they will avail themselves to make the project succeed.
Understand your stakeholder dependency
The payroll process at your organization may include stakeholders from finance, treasury, IT, HR and other divisions. Work to build a dependency map for every part of the process. Once you understand each dependency, it’s important to also map the implications down the reporting line. Use your dependency map to tailor your messaging to stakeholders:
Explain the project function
Describe precisely what is changing and all parts affected. It’s not enough to reference a “payroll system” or “HCM system” change. Be explicit about what is changing and speak the language of your audience. Different departments refer to the same systems and processes differently.
Sell why it is good for the business
Outline why the company is making the decision and why it makes good sense for the organization.
Describe the benefits relevant to your audience
Some stakeholders just care why a change is good for them. Understand the different needs and perspectives and sell the value to each individual. This step is one of the most overlooked elements of change management communication plans. Explaining how a change helps stakeholders directly goes a long way in securing buy-in.
Confront objections head-on
Don’t hide from the uncomfortable conversations about the changes, especially the changes that are disrupting the status quo. Address them early and often. Listen to the feedback, explain the reasons and plan, and explain again.
How to communicate: Provide a feedback loop
Communication has to be a two-way street. Identify gaps in your plan and solicit input from stakeholders to solve potential issues.
Be sure to respond to every piece of feedback, because passive dissenters may use a lack of response as fuel and evidence of future project failure.
When responding to feedback, explain to stakeholders why something will or won’t be included and work with them to understand the logic of the decision. This helps to create buy-in.
Be inclusive, craft the right message for the right audience:
- In-country providers
- HR tech team, including integration development resources and data management
Step 3: Cutover
As you get ready for implementation, it’s critical that all of your stakeholders are ready to support the transition.
- Train stakeholders on short-term workarounds from the expected implementation as well as pre-existing processes.
- Reinforce your training through an internal communications campaign.
- Print out procedure cards and distribute them to stakeholders to remind them of the essentials.
- Administer certification tests.
- Put up posters to remind folks of the cutover date.
By now any resistance to change should have been converted or neutralized. If you still have active and passive dissenters, your organization may not be ready and your cutover is at significant risk. Stop and convert as many as you can before moving forward. Otherwise, it’s likely you will have to add even more time and resources to the project.
Step 4: Post-launch
Now is the time for ongoing care and maintenance to ensure the newly implemented processes run smoothly.
Keep the feedback loop open
The feedback loop is just as significant post-launch as it was in development. You probably didn’t get everything right out of the gate, and that’s OK. By putting in escalation procedures to respond to feedback on the new processes, solutions can be found more quickly and efficiently.
Protect against rogue parallel processing and workarounds
When stakeholders stray from the defined operational process, remember that most just want to do a good job and don’t intend to undermine the project. However, the reasons don’t matter as much as your response. Be ready to manage the problem and steer stakeholders back:
- Keep an eye out for people reverting to the “old way.”
- Catch issues with the new process, as they may seek to discredit the “new way” and exploit them.
- Conduct a post-implementation audit to gain a clear picture of the change’s impact.
Keep stakeholders updated on the bigger picture of the implementation as they work on their individual parts. The project was ultimately hugely successful and they should share in the victory for the organization.