Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » System Implementation infoKit » Planning a System Implementation » Why do System Implementation Projects Fail?

Why do System Implementation projects fail?

A Warning for All

In The Computer Weekly on 22 June 2004, Tony Collins reported, 'Too many costly government IT projects come to grief or badly fail to live up to expectations'. In his report, he examines the common factors and explains why more accountability is needed to reduce the waste of taxpayers' money.

An extract of his report entitled 'Lifecycle of a Public Sector IT failure' appears below. These words refer specifically to Government Information Technology projects, but are nevertheless wise and pertinent.

'The design accords with the best practice project principles, but there is an expansion of the objectives and costs as interested parties give their views on what the new systems could do.

An invitation to tender is issued, but the commitment to the timescales and design is too great to heed warnings from perspective end-users, unions or one or two reputable prospective suppliers that the timetable is too tight or the scope unrealistically ambitious.

After contracts are awarded fuller consultation with potential end-users begins but is inadequate or self- selective.

The supplier begins to realise it has over-estimated its ability to understand the customer's business and convert this into IT systems, while the customer realises it has over-estimated the capability of the supplier.

More often than not the supplier realises too that it has not asked enough questions before signing the contract, and the customer has not understood its business sufficiently to explain its work practices, the complexities of the project, the risk of failure and real costs to the supplier.

The timetable begins to lengthen and the projected costs increase but the commitment is too great to allow any indecision or U-turn.

As the project begins to founder, the cover-up begins. Failure is depicted as success. MPs do not get well-rounded answers to questions.

Failure can no longer be hidden because the public or the departmental end users are affected by the contract's being abandoned, changed, re written or re-awarded.

Years later there are sometimes reports by the National Audit Office and the commons Public Accounts Committee.

The department says it has learned from the mistakes of the past.

Those who give these assurances that lessons have been learned move on and are replaced by new personnel who embark on projects which repeat the mistakes of the past.

The cycle begins anew.'


Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)