20 things you should never short-change when buying/implementing HR Technology

1. the “what's in it for me” perspective of each class of user; e.g., employees, applicants, line managers, executives
2. considering the downside of “imposing across-the-board standardization” when it unduly compromises other key business objectives
3. the change management effort in planning & executing the implementation
4. the training effort in planning & executing the implementation
5. the process & technology integration effort in planning & executing the implementation
6. subscribing to the “trust but verify” approach with respect to vendor / product claims
7. IT buy-in and having their criteria for support understood and transparent
8. end-user buy-in and having their criteria for support understood and transparent
9. exec buy-in and having their criteria for support understood and transparent
10. leveraging your company’s brand / value as an end-customer in making expectations known to your vendor partner; e.g., expectation to have some input to product direction or priorities if possible/practical
11. your organization’s previous experience with new technology adoption and roll-out
12. critical linkages between the various pillars of the Talent Management value chain, including those that are “focus areas” more than processes; e.g., employee engagement
13. internally marketing the benefits of implementing the new HR/HCM system or module --- before, during and after the system is implemented
14. the importance of “quick wins” to create support and momentum in the early stages
15. the importance of end-users being in control of (and being accountable for) data quality
16. focusing on business drivers, how they might be changing over time, and how the HR/HCM system aligns with those drivers
17. lessons learned from similar companies with similar implementations
18. the contingency plan for transitioning away from each HR/HCM vendor you partner with
19. creating & maintaining a “risk and opportunity” log from before Day 1; i.e., during the planning stage --- thru post-implementation
20. using a meaningful decision-support process and tool for prioritizing system enhancements needed -- or (if there's no other viable options) customizations pursued