Post-GFC: project failure leads directly to bankruptcy
Posted in Governing Programmes and Projects, Practice Areas on August 17th, 2009 by Raymond Young – Be the first to commentHere’s a situation that may be playing out in companies globally:
A company is on the verge of bankruptcy. It has been particularly hard hit by the global financial crisis and is losing several million dollars a month. It desperately needs to reduce costs and their accounts are not up to the intense scrutiny. A number of key initiatives are being undertaken and the auditor has added the requirement to consolidate the accounting systems. The board has no choice but to agree, but there couldn’t be a worse time to do a new IT project. The chairman has overseen a number of IT projects and “not one of them has succeeded”.
IT said that the systems can be integrated in two months so the edict from on high is that it has to be done before Christmas. The new boss is claiming not to be on top of the detail and plans to delegate responsibility for the accounting system project to a manager. The manager understands the business processes but hasn’t been involved in the decision.
It wasn’t so long ago that the press was reporting on a similar IT project that failed just before Christmas. I helped Standards Australia produce a handbook for boards and top managers of lessons learned from a whole range of similar disasters (HB280-2006). In the case above, not one of the guidelines is being followed. It seems no one ever learns. The price this time will be jobs, followed soon after by bankruptcy.
For many, the GFC has all but removed any margin for error. Will boards also pay the price? The precedent was set in 2006 when the CFO, CEO and chair of the audit committee resigned from Australian Pharmaceutical industries following an IT project failure.
Where are the auditors?
My friendly advice in such cases is often rejected with the put down “have you ever implemented XYZ system?” There is little understanding that the real issues actually relate to governance. People fall into the trap of thinking they are IT projects, deferring to the vendor and assuming the business benefits will flow automatically from implementing a system. Fifty years of experience proves it doesn’t.
Perhaps we in the profession need to do more. It is disturbing that I often hear that auditors are not suggesting clients follow the 2006 guidelines in HB280 nor the related Standard on the corporate governance of projects (AS8016 forthcoming).
In the building industry, clients are not expected to know whether concrete has been poured correctly or the steel is of the right thickness. We have building inspectors to certify minimum standards have been met. It is completely dysfunctional to defer to vendors just because it is an IT project! Why aren’t our auditors providing ‘project inspectors’. It is not part of the formal auditor training, but it is common practice for audit firms to subcontract specialists when they don’t have the expertise. I’m arranging to provide these services for a mid-tier firm as I write, so clearly it can be done. Why is this not a common service?
Where were the directors?
Perhaps the most disturbing thing of all is that boards know projects have a high failure rate [i]. Why do they and senior management expect a different result when they continue to follow the same process? Governing projects is not rocket science. There are only six basic issues that have to be addressed:
- Make sure you know what success looks like (IT is generally only an enabler, it is rarely the real objective).
- Make sure you know what has to change for the benefits to be realised.
- Make sure you appoint a sponsor who is personally motivated to make the changes happen, and make them accountable for the benefits.
- Make sure you have a way to measure if the benefits have been realised (Do not use on-time on-budget. This is desirable but not the ultimate objective).
- Make sure you listen. Establish the right culture so that bad news is not filtered out.
- Make sure you monitor and intercede as necessary (Something always goes wrong and there are times decisions can only be made at the board and top management level. Political considerations cannot override the need to have the right person accountable. When the consequences include bankruptcy, we all lose).
This advice is usually enough for most people, but there are times more detailed help might be required. We have developed 6Q Governance™ to be the project inspector’s toolkit and when appropriate, we can work with you to transfer our skills.
[i] R.C. Young and E. Jordan, “Lifting the Game: Board views on e-commerce risk,” in IFIP TG8.6 the adoption and diffusion of IT in an environment of critical change, (Sydney: Pearson Publishing Service, 2002), pp. 102-113
