People do not usually embrace change merely for the sake of it. There is always risk involved in changing existing practices — to paraphrase an English saying “If it is not broken, do not fix it!”.

The simplest reason might be that people like the look or sound of new technology and a company wants to be seen at the “cutting edge” of technology. Installing a new hi-tech software system shows the company off to good advantage. Companies can use this opportunity to reap some of the other benefits that a new system might bring.

Or a company may realise that new technology brings new processing facilities and methods within their reach.

More normally, companies develop new software systems as a result of external forces. Costs may be rising and new software could reduce overheads. There may be competitive pressures and unless changes are made to the business processes, a company will lose its competitive edge.

More mundane reasons for change includes new legislation requiring an update to business processes. A shortage of appropriate staff can also drive the need for new software.

Whatever the reason, once a company decides to install new software, it makes sense to maximise the return on the investment. Not only should the system address the problem at hand, but it should also bring as many other benefits as possible. It is this escalation of requirements which can transform a hi-tech business solution into a software catastrophe. We discuss this next.