1. Unrealistic expectations of required internal effort – an HR/Payroll project is a major thing to implement and should be resourced accordingly.
2. Supplier Delivery – don’t expect the supplier to do everything for you.
3. Sales & Reality – you may be sold a Rolls Royce that turns up a Mini.
4. Project Manager – HR & Payroll Specialists – Understand what your supplier Project Manager will be adding to the project.
5. Implement what has been purchased – you can only implement what you have purchased. Make sure all the things you want are included.
6. ‘As is’ & ‘to be’ processes – many customers expect the solution will change things. It won’t. You should map all the key processes as they are today and create the to be processes that fit with the new solution.
7. Understand your goals – do you know what you are trying to achieve and how you can measure how close you are to achieving them? If you don’t have a goal you won’t know if the project is successful.
8. Unrealistic timelines – a supplier may tell you it can all be done in a couple of months, you need to be realistic give yourself six months to implement core modules.
9. Know your technology limitations/preference – don’t underestimate your IT department as they will know your technology plans for the future.
10. Consolidated effort – IT, Payroll & People – this is team exercise and all stakeholders need to be involved and participate.
11. Don’t have multiple change initiatives – any known future changes such as structure should be planned and the solution set up to accommodate it.
12. Budget contingency – most projects run into some sort of challenge. Give yourself a contingency budget.
13. Scope creep – keep to the original plan. Don’t add in nice to haves.
14. Director / Staff – Clear vision from director cascading down to those who implement the software – Involve Directors as it is they who will encourage the staff to deploy the new solution.
15. Stakeholder management – The key player is the Project Stakeholder it is they who can make the difficult decisions and they need to be onside.
16. Understanding data – when converting data from one system it needs to be accurate and clean. It is no use replicating all the rubbish you have in the existing system.
17. B.A.U support – what will you do when the Project is live? What has beet set up for Business as Usual support?