HCM Implementations Aren't So Scary avanti.ca
©2014 Avan So ware Inc. All rights reserved.
3. DETERMINE THE RIGHT ROLL-OUT STRATEGY
Decide whether it will be best for your organization to roll-out the new solution all at once or take a staged approach.
Both strategies have pros and cons and it's important to understand what will be best for your company.
IMPORTANT CONSIDERATION
If you roll-out the entire implementation all at once as a single big event across the entire organization
you have higher risk but it tends to be more cost effective and implementation time is faster. If you stage
the roll-out – by module, department or location - learnings and experience from the first phase can
be incorporated into future phases to improve processes, and it is less risky as it impacts less people at
a time. It does tend to be more expensive in time & financial cost as the duration is longer (eg: more
training sessions, more vendor time).
4. CLEAN UP YOUR DATA BEFORE YOU CONVERT
Take a good look at your data before you move it into the new solution. Start by deciding what data you really need.
A new HCM software implementation provides the opportunity to assess the value of all the data you are storing. Often
companies store unnecessary data because they worry that someone, somewhere down the line just
might need the information. The problem with this is that converting all of your data over to a new
software system will take time, money and effort that can be better spent elsewhere.
Once you have decided what data to convert make time to work together as a functional team to
standardize items like naming conventions, validate the information, clean-up duplicate data and input
missing data.
IMPORTANT CONSIDERATION
When implementing an integrated solution much of the data will be converted from disparate systems.
An example we often run into is position naming, when HR tracks employee positions in one solution
and payroll tracks employee positions in their solution often there are discrepancies in the names
assigned to positions. Working together to have a single position naming convention in the new solution
streamlines reporting.
There's no one-size fits all
implementation strategy. Every
company has unique goals and
different cultures.
Without data cleansing,
companies face the prospect
of corrupt or incomplete bits
of data that will prevent them
from being able to get accurate
reporting or realizing all the
benefits of the new solution.
