Remember, however, by starting, you may get the R.O.I. before you have to move forward to the new product. There is, however always a risk. You also have to recognize that end-users don't like change, so starting in one direction and changing later may lead to a great deal of resistance. There are six reasons central to project failure. The needs were not clearly spelled out and there were not defined goals to measure.
Project scope too large to manage by the corporate team.
Sales Team resisting change, i.e., benefits are not clear. Changes take much longer than anticipated. The end-users were not at the center of the design. This can happen when the IS staff takes control and does not draw the Sales team adequately into the process. End-users were not adequately trained.