What can go wrong ? The following is a list of 36 common reasons why computerized system implementations fail - in no particular order.

1. Poor quality vendor assistance.

2. Not enough vendor assistance.

3. Inadequate reference checks.

4. Inexperienced project manager.

5. No depth of expertise on project team.

6. Insufficient size of project team.

7. Unclear roles and responsibilities for implementation.

8. Lack of top management support.

9. No buy-in from Operations.

10. Lack of commitment of workers

11. No buy-in from other stakeholders such as Information Systems or Accounting.

12. Inadequate training.

13. Unrealistic timeline.

14. Big bang implementation.

15. Unrealistic business case.

16. Inadequate budget for implementation.

17. Poor communication to stakeholders throughout implementation.

18. Poorly articulated goals and objectives.

19. Unclear performance measures and targets.

20. No personal incentives for smooth implementation.

21. Poorly understood consequences if implementation fails.

22. Poor fit of the computerized system to business needs.

23. Lack of seamless integration with other business applications.

24. No formal process for issue resolution.

25. No risk management process.

26. Poor system design and architecture.

27. Inadequate process design pre-work.

28. Unforeseen job design changes resulting from new processes or system.

29. Excessive package customization

30. Poorly planned and executed data conversion from old system.

31. Poorly understood policies and procedures.

32. Inadequate testing.

33. Lack of proper pilot implementation.

34. Inadequate facilities for system hardware.

35. Insufficient resources to operate the system.

36. Excessive start-up effort, setting parameters, preferences, etc.

About The Author - Dennis Sommer