Friday, 13 October 2017

HR Technology Implementation Checklist

When an organization steps into Digital HR Transformation, its important that they apply appropriate assessment and evaluation techniques by which they land in the right HR Technology for Implementation.  Even if best of HR technology is chosen for your HR Transformation, it does not guarantee a successful rollout. Often times, many ERP / HR implementation projects face a lot of struggles in its way and by the time it gets implemented, a good amount of time and effort would have already gone in already. If the implementation fails, all the other decisions made during the process including the choice of technology gets into question. 

In my experience I have come across the best implementations as well as worst implementations with the same HR technology often making me wonder what went wrong.  When something works well in a particular customer, the same fails in another place which is a similar business in nature. Below are 2 contrastic examples that I have come across which truly validates the above statement. 

When I was leading a very crucial rollout for our client (one of the large private insurance company) in India, the key objective was to ensure that there is a lot of decentralisation to the entire HR Processes taking place while the necessary process and controls were designed and controlled by the corporate. For example, a regional head in their region would like to have the choice of his / her people subject to they clearing the necessary recruitment process and at the same time certain amount of flexibility needed to attract them via good compensation package and at the same time falling in line with corporate guidelines. This company went onto implement the solution with great success where they had rolled out offer letters to candidates in 3 minutes from 3 days earlier. This was a phenomenal success but there was a lot of thinking, hardwork and meticulous planning that took place to reap this benefit.  

On a contrasting note to the above, I was heading another project for another client of ours (a large retail food chain) with the involvment of Corporate HQ in United States of America. This was a project that had lot of complications ranging from technology integration to cultural integration of people involved in the project. We just could not move beyond Phase 1 of the project and the project was way beyond the timelines and certainly taught a lot of lessons for me personally and that too involving people of cross cultural nature. Here it is the same HR technology that worked well in one place but in another place it was botched up. Why? This led to some thinking and I thought we need to have some sort of best practices need to be employed in the future there by we see consistency in successful technology rollouts. 

Here are some best practices for your next tech implementation:

1) Any technology implementation that you start of is a Company project.  While this is a HR System, every department or every employee in the organization may well be impacted by this change especially when you rollout Payroll applications or integrating with other payroll applications or integrating with payroll service providers. It is important to include all the stakeholders thereby they will be part of the project and will be willing to contribute when their time comes. 

2) Often times, I have seen companies mix up process with technology.  They want the system to do everything for them and not willing to bend or tweak their processes. Its important that companies use this time to question the status quo of some of the policies and see if they are relevant in today's context and they see a need to continue with them in today's context. Not being flexible to modify some of the processes leads to lot of customizations thereby increasing the cost of overall solution, maintenance and support for future. 

3) Its important to have the right project team in place. We need to have the right people with right skills on the project team. Its important that the person who is driving the project (Client PM) is in a position to understand system intricacies, users expectation, project cost / timelines and balance between them.  This person need to carry certain authority as well so that they can take decisions rather than waiting for instructions from top to act.  

4) Keep the project sponsors involved throughout the life cycle of the project. Ensure regular status updates, steering committee discussions taking place thereby bringing everybody onto the same page and achieve the project goals.  Project sponsors can influence and can use their positional power to keep the implementation devoid of conflicts. 

5) Plan for change before you get there. Its important that organization gets prepared for this change and its important that these changes are buffered into the project plan.  

6) Develop a communication plan. Its important that the users need a clear commuincation plan as they are not involved in project day to day whereas the project team gets involved. Its the onus on the project team to communicate at regular intervals (over communicate if required) and effectively so that users do remember the information. 

7) Its important that the Project Manager of the project expects issues to come or mistakes to happen. The success of the project is in getting to the last mile of the project and that is the realisation of vision. Its important to have a solid training plan for the users and ensure the users get some orientation towards the product before they participate in the end user testing. 

8) User adoption is an important aspect in a HR Technology implementation.  Many a times the application usage is known to only a few administrators of the project and does not necessarily cascade down the line to the users.  I have sat in many review meetings with users where they come back with some obvious queries for which they do not know the answers.  I used to blink my eyes and say that its already available.  I have had many "already available' moments but deep inside the app administrators are more focused on resolving user queries and not increasing user adoption by evangelizing the solution that they took pride in implementing. Have constant user feedback sessions thereby helping them to adopt the system without much of an issue otherwise its doubtful that the organizations would have realised the ROI. 

9) Celebrate your success. For a project implementation of this nature that is muddled with lot of challenges, its important that the project team is highly energized. Celebrate every milestone that you pass through in this period as it gives lot of energy for next milestone and also communicate to the sponsors about these successes. 

10) Even after the implementation is over, the work continues and application maintenance will be way different compared to implementation.  Ensure the organization identifies and trains support people and setup a helpdesk for any user queries and resolution as part of the implementation life cycle itself.  At any point of time, the organization needs to have a minimum of 2 training application support engineers who know the nitigrities of implementation.  In my experience, I have gone through lot of people change in client places and suddenly the entire application is orphaned and nobody knows what exist and do not exist. It is at this stage the application loses its credibility and suddenly the HR technology partner is seen redundant and the organization feels they have not got the returns from investments made. 

Thank you for your patient read and I hope it was relevant for you and enjoyed it. In case of any queries, please feel free to share your feedback to swami@avaapyaconsulting.com

No comments:

Post a Comment