|
36
Reasons Why Software Implementations Fail
By Dennis Sommer (www.dennissommer.com)
Despite several decades of experience in implementing
software packages, in general, companies still are seeing
less than satisfactory results. Project failure rates
still remain extraordinarily high. Based on a survey of
417 IT executives and managers, we have compiled a list
of 36 risk factors to avoid or mitigate during a system
implementation.
There are so many things that can go wrong, as illustrated
by the long list below. But awareness of these pitfalls
can be one of the first steps towards a successful implementation.
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
Dennis Sommer
is the founder and CEO of Executive Business Advisers,
a management consulting firm specializing in business
growth, sales and profit improvement. www.executivebusinessadvisers.com
Dennis helps companies increase sales revenue, reduce
sales and marketing costs, improve marketing ROI, and
drive new business growth by improving and optimizing
their sales, marketing, company strategy and financial
health.
Dennis is a highly sought after business keynote and seminar
speaker www.dennissommer.com
and author of several highly popular sales, marketing,
leadership and professional development international
articles and books www.advisersecrets.com
.
Contact Dennis at 800-627-6512.
|
|
|
