Despite the best efforts of all the people involved, an IT project can fail. Either it will be completely unable to function or it will be overwhelmed by the needs of the organization that commissioned it. There are a variety of reasons for the failure and it is important to have an understanding of them in order to avoid the pitfalls when undertaking future projects. This article aims to outline some of the major issues that can cause a perfectly sensible business IT plan to fall flat on its feet.

Human beings will be at the heart of any business IT project. They will be the working capital that ensures it is commissioned and at the end that it is used for the purpose for which it was commissioned. They will bring their own judgments, skills and failings to the project and could ultimately bring it down.

There is no way of controlling human influence in a comprehensive manner. What managers tend to do is to attempt influence employee action using the various management incentives and sanctions available to them. However this does not always work and could ultimately push the employees even further away from their managers. The basic tenets of good management practice can still apply here. Things such as supervision and reward schemes can counter some of the more negative reactions to new technology.

Where the project has been outsourced, the personnel issues are compounded by the fact the in-house managers really have very limited control on external staff. They will have entered binding contracts with their parent organizations and will really be free to do as they please. They also bring with them their own way of working that may not fit in with the company philosophy. Furthermore they do not bear direct responsibility for things when they go wrong and they have to use faulty technology. This means that they have even less incentive to get it right the first time.

This leads us on to the issue of accountability. This is particularly the case where there is a large organization with different people working on different projects all feeding into one big IT group. This can lead people to view themselves as separate parts of an entity leading to isolation and inconsistencies in practice. Even where problems are being resolved there is no one person who coordinates strategy. Any attempts to get some type of responsibility descend into a blame game. People start going off sick with stress and avoiding the senior managers.

However the biggest cause of failure has to be planning. Many failing organizations have a conceptual idea of what they would like out of their IT project but they will not have detailed plans as to how they are going to achieve the objectives. Commissioning will often be based on the personal whims of a particular manager rather than being an overall long term business strategy. Issues will be simplified with the attitude that they can deal with whatever problems arise on an adhoc basis. Therefore without proper planning the project is almost certainly doomed to fail.