Category Archives: IT-related failures

Healthspace was failing in 2010 – why is it being kept alive?

By Tony Collins

“Too many failing projects are continued for too long” – Ian Watmore, House of Commons, 2009.

HealthSpace, a centrally-run system that has, for years, provided unneeded work for consultants based at Connecting for Health, software developers, civil servants, and IT suppliers,  at a cost of tens of millions of pounds, is to close “from” March 2013.

A report commissioned by the Department of Health and NHS Connecting for Health in 2010 found that the system had never worked satisfactorily. But the Department and CfH has kept the project going, paying consultants and IT suppliers, although it was clear from an early stage that the scheme was doomed.

Will the Department of Health continue paying consultants and IT suppliers for a system that is to be cancelled?

HealthSpace was designed to be a personal health organiser. It was based on a good idea – that some patients could benefit from access to their health records – but the technology was too complicated and never fit for the public to use. It is said that those involved in the project spoke in a technological, managerial and procurement language – and rarely mentioned patients.

The Guardian this week reports Charles Gutteridge, national clinical director for informatics at the Department of Health, as saying that Healthspace is “too difficult to make an account; it is too difficult to log on; it is just too difficult.”

The Department of Health later told The Guardian that Healthspace would be closed down “from” March 2013.

In 2010 a report by Trisha Greenhalgh and her team, The devil’s in the detail, which was commissioned by CfH, found that HealthSpace had involved professional advisers, software developers, security testing contractors, business managers who wrote the benefits realisation cases, lawyers who advised on privacy and regulatory matters and many others.

Yet the system was doomed from the start. Greenhalgh’s report in May 2010 revealed that:

“Project leads from participating NHS organisations repeatedly raised concerns with Connecting for Health in monthly management meetings about the low uptake of advanced HealthSpace accounts, since the benefits predicted, such as lower NHS costs and patient driven improvements to data quality, could not possibly be achieved unless the technology was used.”

Comment:

It’s not known how many millions has been wasted – and continues to be wasted – on Healthspace; and it is difficult to avoid the conclusion that the continuance of the scheme benefits nobody except those who are paid to work on it, which includes contractors and IT suppliers.

Why is the scheme to be cancelled “from” 2013, when it should have been cancelled when Trisha Greenhalgh and her team produced their report in May 2010?

Shouldn’t ministers have some control – especially given that we are supposed to be in an age of public sector austerity? Ian Watmore, Permanent Secretary at the Cabinet Office and former Government CIO, has said that failing projects are continued for too long. He said that in 2009. So isn’t it time ministers and particularly civil servants applied the principle of ‘fail early, fail cheaply‘?

Link:

In 2010 ComputerworldUK had an account of how Healthspace was being kept alive unnecessarily.

Fire ‘superstations’ without software cost £1m a month – The Times

By Tony Collins

The Times reports today that taxpayers are paying more than £1m a month on the rent and upkeep of fire control rooms across England that have never been used. The purpose-built control centres look ready for immediate use, with open-plan desks fitted with desktop monitors and keyboards, and huge screens on a wall at the front of the control rooms which are supposed to help fire and rescue crews mobilise appliances and manage incidents.

Only there’s no working software.  The Department for Communities and Local Government negotiated the end of a contract with the main contractor EADS for software to run the regional control centres in December 2010. Officials concluded that the software could not be delivered within an acceptable timeframe. The regional control centres were completed before the IT project was cancelled.

The cost of the centres has been uncovered after a request under the FOI Act. The Times devotes much of its page three to a story under the headline:

Revealed: scandal of the £1m-a-month fire service ‘superstations’ lying empty.

Only one of nine regional centres is in use. The other eight incur rent, electricity, water and repair costs at £1,134,566 a month. Costs will be incurred for years because there are no break clauses in the agreements to lease the buildings. Two leases come to an end in 2027, one in 2028, two in 2032, three in 2033 and one in 2035.

A spokesman for the Department said that agreement has been reached for a further two of the buildings to be used by local fire authorities. Officials are searching for public or private sector tenants to occupy the other regional centres.

Lord Prescott, the former Deputy Prime Minister, who authorised the start of the technology project in 2004,  said he had been kept in the dark by civil servants on the rising costs of the scheme. He said it had been on budget when he left the department in 2007.

Eric Pickles, the Communities Secretary, said the failure of Firecontrol was an “expensive reminder of why you can’t trust Labour to run anything”. But the Coalition’s coming to power has not stopped central government IT-related failures.

Why Firecontrol failed

Firecontrol  followed the same tracks to a cliff edge that have caught out civil servants, ministers and suppliers on other government  computer-related projects.

The National Audit Office and the Public Accounts Committee found that  the Firecontrol project was rushed, had little support from those who would use it, costs and complexity were underestimated, there was an over-reliance on consultants and a lack of accountability for decisions made  – or not made.

The idea was to replace 46 local control rooms with nine, linked regional centres, which would be equipped with new standardised computer systems to handle calls, mobilise equipment and manage incidents.

But the project was cancelled in December 2010 with ministers unsure the technology would ever work. The NAO estimates that £469m will be wasted on the project.

The NAO found that the scheme was “flawed from the outset”, largely because local fire and rescue officers did not want regional centres or major changes in the way they worked.  Introducing any large new system is difficult but with enthusiastic support serious problems can sometimes be overcome; but introducing a complex new system without support from those who would use it means staff will have little incentive to find ways around problems.

The NPfIT [National Programme for IT in the NHS] failed in part because it lacked support among GPs and NHS staff; and the complexity of introducing standardised technology in semi-autonomous hospitals – each one with different ways of working – was underestimated. It was the same with Firecontrol.

The complexity of introducing standardised systems in regional centres with no goodwill among staff – was underestimated.  From the start many local fire and rescue officers criticised the lack of clarity on how a regional approach would increase efficiency. “Early on, the Department’s inconsistent messages about the regionalisation of the Fire and Rescue Service led to mistrust and some antagonism,” said the NAO.

The technology project was rushed while local fire crews were excluded from project discussions. “The project progressed too fast without essential checks being completed. For example Departmental and Treasury approval was given without proper scrutiny of the project’s feasibility or validation of the estimated costs and savings,” said the Public Accounts Committee. The project went ahead before the full business case was written.

A review of the project as early as April 2004 found that the scheme was already in poor condition overall and at significant risk of failing to deliver. But the “Gateway” review report was kept secret for seven years.

Is the stage set for IT disasters in government to continue? So far the Coalition has decided, like Labour, to keep secret all internal reports on the progress or otherwise of its mega projects, including Universal Credit, though the policy on secrecy may be about to change, which Campaign4Change will report on separately.

Firecontrol – same mistakes repeated on other projects.

The real reason NHS Risk Register is a State secret?

By Tony Collins

Yesterday  (15 May 2012) the Information Commissioner Christopher Graham issued a finely-crafted report to Parliament on his concerns about the Government’s use of a ministerial veto to stop publication of the Transition Risk Register relating to health service reforms.

Graham’s concern is that the veto represents a new and worrying approach to Freedom of Information.

Graham cannot do anything about the veto but he can warn MPs when he feels the Government has gone too far. This he has done in his report which says that the previous three occasions on which the ministerial veto has been exercised related to the disclosure of Cabinet material under FOIA. Now the Government has applied the veto to information held by the Department of Health.

Says yesterday’s report: “ The Commissioner would wish to record his concern that the exercise of the veto in this case extends its use into other areas of the policy process. It represents a departure from the position adopted in the Statement of Policy and therefore marks a significant step in the Government’s approach to freedom of information.”

The Government’s decision to ban publication of the health service risk register is particularly relevant to IT-related projects. This is because the government uses exactly the same arguments to ban contemporaneous publication of Gateway reviews and other independent assessments of IT-related projects and programmes.

Risk registers and Gateway reviews of IT-enabled change projects are similar. They are designed to identify all the main risks associated with the project or programme and have a red/amber/green system of rating the risks.

The Government’s argues that risk registers (and Gateway reviews) are researched and written in a “safe space” that allows civil servants to give advice and recommendations in a frank way. This candour would be compromised if the civil servants thought their advice would be published, says the Government.

In issuing a veto on the health risk register Andrew Lansley, the Health Secretary said, in essence, that he could not trust civil servants to be entirely honest if they knew their reports would be made public.

Said Lansley:  “If risk registers are routinely or regularly disclosed at highly sensitive times in relation to highly sensitive issues, or there is legitimate concern that they could be, it is highly likely that the form and content will change: to make the content more anodyne; to strip out controversial issues or downplay them; to include argument as to why risks might be worth taking; to water down the RAG [red,amber, green] system.

“They would be drafted as public facing documents designed to manage the public perception of risk; not as frank internal working tools. These consequences (many of them insidious) would be to the detriment of good government.”

Lansley also wanted to ban publication to pre-empt sensational media coverage.  In this he was repeating the arguments made by civil servants under Labour who refused, under the FOI Act, to publish risk registers and Gateway reviews.  Said Lansley “I consider that the form and the frankness of the content of TRR [health service Transition Risk Register] would have been liable to create sensationalised reporting and debate.

“The content would also have been inherently highly open to misinterpretation by both the press seeking a headline and/or for political reasons. The likelihood of this occurring is particularly acute where the subject matter is, as with the Transition programme, controversial and the proposals at a highly sensitive stage.”

But the Commissioner did not accept that disclosure of the Transition Risk Register would affect the frankness and candour of future risk registers. The Commissioner also said that a ministerial veto should, by law, be made only in exceptional circumstances.  But the Government has failed to explain why there are exceptional circumstances in this case.  Said the Commissioner:

“The Commissioner does not consider that sufficient reasons have been given as to why this case is considered to be exceptional, particularly in light of the [Information] Tribunal’s decision dismissing the Department’s [Department of Health’s] appeal.

“The Commissioner notes that much of the argument advanced as to why the case is considered to be exceptional merely repeats the arguments previously made to Commissioner and the Tribunal and which were in part dismissed by the Tribunal.”

Graham concludes:

“In light of previous commitments he has made, and the interest shown by past Select Committees in the use of the ministerial veto, the Commissioner intends to lay a report before Parliament under section 49(2) FOIA on each occasion that the veto is exercised. This document fulfils that commitment.

“ Laying this report is an indication of the Commissioner’s concern to ensure that the exercise of the veto does not go unnoticed by Parliament and, it is hoped, will serve to underline the Commissioner’s view that the exercise of the ministerial veto in any future case should be genuinely exceptional…

“The arguments employed by the Department at the Tribunal and by the Secretary of State in explanation of the subsequent veto, both in the Statement of Reasons and in exchanges in the House of Commons around the Ministerial Statement, certainly use the language of ‘exceptional circumstances’ and ‘matter of principle’. But the arguments are deployed in support of what is in fact the direct opposite of the exceptional – a generally less qualified, and therefore more predictable, ‘safe space’.

“As such, the Government’s approach in this matter appears to have most to do with how the law might be changed to apply differently in future. This question falls naturally to consideration by the Justice Committee who have been undertaking post-legislative scrutiny of the Act.”

Comment:

The reason for the veto in the case of the health service risk register has little to do with protecting a safe space for frank discussion.

Civil servants already compile risk registers, Gateway reviews and similar reports on the basis that they may, at some point, be published. Officials are no more likely to be frank if they know their reports will be confidential than more guarded if they know the documents will be published. They will do what their job entails. Their job requires honesty. They will do that job whether or not reports are published.

The real reason for the veto – and the refusal of departments to publish all contemporaneous internal reports on large and complex programmes, particularly those with a large IT element – is that some new schemes within Government operate at a shambolic level.

Any new government, whatever its hue, soon learns to keep secret the fact that such programmes are sometimes characterised by near anarchy.

One outsider to the UK government, Australian David Pitchford, discovered the truth when he became Executive Director of Major Projects within the Efficiency and Reform Group which is part of the Cabinet Office. Pitchford may not have realised his comments would be reported when he told a project management conference in 2010 that “nobody in the UK Government seems to know how many projects they have on the books, nor how much these are likely to cost”.

He found that projects were launched, and continued, without agreed budgets or business cases.  Today, there is better scrutiny of major projects, by the Cabinet Office’s Major Projects Authority. But the MPA is limited in what it can do or scrutinise. Which leaves government in a general mess when it comes to implementing anything new.

Evidence for this mess comes from the National Audit Office. Its auditors tend to investigate departments as a whole more than they do specific projects but when they do the careful reader can see that projects such as the Rural Payments Agency’s Single Payment Scheme (a scant regard for public funds, said the NAO) and the C-NOMIS project for the prison service (kindergarten mistakes, said chair of Public Accounts Committee) were without a structure. Chaos prevailed – and ministers were among the last to know.

Publication of project reports encourages professionalism. Departmental heads can be held to account if Parliament knows what has gone wrong. That’s precisely the reason departmental heads don’t want risk registers and other project reports published. It’s why all internal reports on Universal Credit, the government’s biggest IT-related project, are kept secret in spite of FOI requests.

The ministerial veto in the case of the NHS risk register is the government and civil service colluding in keeping the public and Parliament in ignorance of internal management’s inability to run complex new projects and programmes in a professional way.

Ministers and permanent secretaries don’t especially mind media criticisms that are based on speculation. They don’t want their critics having authoritative internal reports. That’s why the Cabinet agreed the health service veto – and it’s one reason the government has a not-very-hidden aversion to the FOI Act.

The coalition cannot justly claim to cherish open government while it is refusing so many requests under FOI to publish contemporaneous taxpayer-funded reports on its major schemes.

We agree with the Information Commissioner that use of the ministerial veto is a step too far. No number of announcements by the Cabinet Office on open government will gloss over the fact that the coalition is even more secretive about mega-projects than Labour. That’s saying something.

Australian payroll IT project cost grows from $64m to over $400m

David Bicknell

In Australia, the state government in Queensland is coming to terms with a failing IT project whose cost has grown from $64.5m to $412m.

The payroll system for Queensland Health first went live in early 2010, prompting thousands of employees to be underpaid, overpaid or not paid at all, and triggering a subsequent critical report by the state’s Auditor General. 

Late in 2010, the Bligh government said $209m would need to be spent to fix the system in the following three financial years, on top of the original $64.5 million implementation cost.

Now, according to The Brisbane Times, the cost of the failed payroll system will reach an estimated $412 million by the end of June this year, with further costs likely to be incurred in the future.

Failure to prepare: Government slammed over health payroll bungle

Smart state’s technology spending up in the air

Whitehall defies NAO and Cameron on publishing status of big projects

By Tony Collins

Government action to cut the number of failures of big projects including those with a major ICT component has made a difference, the National Audit Office reports today.

In its report “Assurance for major projects”  the NAO is largely supportive of actions by the Government, , the Cabinet Office’s Major Projects Authority and the Treasury in setting up reviews of major high-risk projects, including ICT-based programmes, to ensure that if they are failing they are put back on track or cancelled.

The NAO says the Government’s decision to “dismantle” the NPfIT was taken after the project was assessed by the Major Projects Authority.

But the report also shows how civil servants have managed to defy a mandate from the Prime Minister, and a separate NAO recommendation in 2010, for information on the status of big ICT and other high-risk projects to be published.

Says the NAO report

“The ambition to publish project information, as part of the government’s transparency agenda, has not been met.

“Our 2010 report recommended that the government should publicly report project status. We consider that public reporting of project information is key to providing greater accountability for projects and improving project outcomes… Regular transparent reporting of performance which highlights successes and non-compliance would also help to build an enduring assurance system.”

Separately in the report the NAO says

“There has been a lack of progress on transparency.  The [Cabinet Office’s Major Projects] Authority has not yet met its commitment to publish project information in line with government’s transparency agenda. The Authority cannot deliver this objective on its own. Senior level discussions are ongoing, between Cabinet Office, HM Treasury and departments, on the arrangements for public reporting.”

Should ministers intevene to force publication?

But the NAO report does not raise the question of why ministers have not intervened to force civil servants to publish the status information on high-risk projects.

Campaign4Changehas argued that publishing status reports on big ICT projects and programmes would be the most effective single action any government could take to reduce the number of failures. (see “Comment” below)

Prime Minister’s 2011 mandate

The NAO’s 2010 recommendation for status information on major projects to be published was backed by a mandate from the Prime Minister in January 2011 which included the undertaking to “require publication of project information consistent with the Coalition’s transparency agenda”.

The House of Commons’ Public Accounts Committee has recommended that departments publish information on the state of their major IT-based projects and programmes; and the Information Commissioner has rejected civil service arguments for not publishing such information.

In addition Francis Maude, the Cabinet Office minister, said, when in opposition, that the Conservatives, if they gained power,  would publish “Gateway” review reports soon after they are completed.  Gateway reports are similar to the assurance reviews carried out for the Major Projects Authority.

Yet none of this has happened.

The “rebel” civil servants

How is it that a group of civil servants who are opposed to publishing information on the status of large risky projects can defy the Prime Minister, Francis Maude, the National Audit Office, and the all-party Public Accounts Committee? Those recalcitrant civil servants argue that assurance reviewers would not tell the whole truth if they knew their assessments would be made public.

But how do we know they tell the whole truth when the reports are kept confidential? The Information Commissioner has pointed out in the past that civil servants have a public duty to be candid and honest. If they are not because their reports are to be published, they are failing in their public duty.

Today’s NAO report says there are differences of opinion among civil servants over whether to publish status information on projects.

Says the NAO

“There has been some support for greater transparency from departments who believe that tracking and publishing major milestones could create helpful tension in the system.

“However, concerns have been raised that increased transparency could limit the value of assurance, as it could inhibit assurance reviewers and project staff holding full and frank discussions.

“Some senior project staff also have concerns that public reporting could have a negative commercial impact, and would prefer delayed rather than real-time public reporting.”

The Cabinet Office told Campaign4Change in 2010 and 2011 that instead of publishing status reports on each major project, it will publish an annual report on the state of its programmes.

But that hasn’t happened either.

Says the NAO:

As well as the objective to publish project information, the [Major Projects] Authority has not yet met its objective to publish an annual report on government’s major projects.

“The Authority initially expected to publish an annual report in December 2011 but is now expecting the report to be published in May or June 2012. The format of the annual report, and the information it will contain, has yet to be decided.”

Comment:

Many times over the last 20 years I have said that publishing status reports on major IT-based projects and programmes would be the most effective single action any government could take to deter departments from going ahead with overly ambitious schemes that are doomed to fail. If, against good sense, impractical schemes are approved, publishing status information will make all the difference.

Permanent secretaries will not lose sleep over a failing project, but they will not want information on it published – which is why that information should be published.

Publishing status information would give civil servants a good reason to tackle weaknesses as they developed.  Permanent secretaries may not mind losing public money on a failing project or programme. They will always fear embarrassment, however.

Who is really in control of Whitehall – civil servants or No 10? David Cameron’s office has issued a mandate that requires status information on projects to be published. The NAO has issued a similar recommendation. How long can the civil service hold out against the political will?

Links:

NAO report – Assurance for major projects

Firecontrol – same mistakes repeated on other projects

New York’s new CIO to create centre of excellence to prevent failing IT projects

By David Bicknell

New York’s recent problems with IT projects have been well documented.

Its latest solution: appoint a new CIO, with a wide remit that includes innovation and the setting up of a ‘centre of excellence’  to nail down failing projects.

Rahul Merchant joins with a background served at US mortgage and housing specialist Fannie Mae and at financial services company Merrill Lynch.

He will become the first Citywide Chief Information and Innovation Officer and Commissioner of the Department of Information, Technology and Telecommunications reporting to New York’s mayor Michael Bloomberg.

His role will involve overseeing New York’s information technology development and management, with a focus on delivering technology projects on-time and on-budget.

Merchant will succeed Carole Post, who recently announced she will be leaving for a position at New York Law School.

“By bringing the City’s IT infrastructure and development under one office, we can ensure we are using best practices across agencies, leveraging the City’s enormous IT infrastructure to our maximum advantage and holding contractors accountable for delivering results,” said Bloomberg. “Rahul is a seasoned executive who has proven himself time and again as a leader and an innovator in the industry.  He is going to do an outstanding job as New York City’s first Chief Information and Innovation Officer and we are excited to add him to our talented team.”

Merchant will be responsible for New York City’s IT infrastructure, as well as oversight of the implementation of key technology initiatives that enable the City’s various agencies to serve 8.4 million New Yorkers.

What will be worth watching is seeing how he tackles New York’s reputation for troubled IT projects by creating a Centre of Excellence that will  “standardise business processes for the implementation of large technology projects, institute a system of vendor evaluation to hold contractors accountable for meeting project milestones, and update the City’s technology contracts to focus on the delivery of established milestones to meet agency business needs.”

According to Bloomberg, Merchant will work closely with agency commissioners and chief information officers “to ensure that IT projects leverage existing infrastructure and software to the maximum possible extent, and that the City’s overall IT budget meets core agency business needs and the City’s overall technology objectives.”

He will also spearhead the New York’s efforts to remain a leader in technology innovation, by leveraging its  technology assets and partnerships with academic institutions, technology firms, and entrepreneurs.

He won’t be short of people to help. Merchant will lead a 1,200-strong staff responsible for managing the City’s information technology infrastructure as well as serving the information technology needs of 45 mayoral agencies, dozens of other governmental entities, and nearly 300,000 employees.

Here’s how local sites reported Merchant’s appointment:

Crain’s New York Business: Major taps Merrill Lynch vet to tame tech projects

Tech President: New York City just radically changed who manages its IT projects

Government Technology: NYC names Rahul Merchant to CIO and Innovation role

FDA: “Much work remains” to modernise its IT systems, says US oversight team

By David Bicknell

Sometimes you have to applaud how seriously the US government takes accountability in its departments over their approach to IT projects.

One of the latest by the Government Accountability Office (GAO) is on the IT management at the Food and Drug Administration (FDA).

In a title, ‘Why the GAO did this study’, it points out that the FDA, an agency within the Department of Health and Human Services (HHS), relies heavily on IT to carry out its mission of ensuring the safety and effectiveness of regulated consumer products. Specifically, it says, IT systems are critical to the FDA’s product review, adverse event reporting, and compliance activities.

Recognising the limitations in its IT capabilities, the FDA has undertaken several initiatives to modernise its systems, with the GAO now being asked to assess the FDA’s current portfolio of IT systems, including the number of systems in use and under development, and their purpose and costs; assess the status and effectiveness of the FDA’s efforts to modernise the mission-critical systems that support its regulatory programs; and examine the agency’s progress in effectively integrating and sharing data among key systems.

In its report, the GAO argues that while the FDA has taken several important steps toward modernising its IT environment, much remains to be done.

According to the GAO, the FDA reported spending about $400 million for IT investments in the last  financial year (2011). But, it says, the agency currently lacks a comprehensive IT inventory that identifies and provides key information about the systems it uses and is developing.

It points that both Office of Management and Budget (OMB) and the GAO’s own guidance calls for federal agencies to maintain such an inventory in order to monitor and manage their IT investments. The inventory should include information on each system, such as costs, functionality or purpose, and status. However, the GAO says, the FDA does not have such a comprehensive list of its systems, although budget documents included information on 44 IT investments for fiscal year 2011. 

Until the agency has a complete and comprehensive inventory, the GAO says, it will lack critical information needed to effectively assess its IT portfolio.

GAO goes on to point out that “much work remains on the FDA’s largest and costliest system modernisation effort, the Mission Accomplishments and Regulatory Compliance Services program.” The program is estimated to cost about $280 million and is intended to enhance existing applications and develop new systems that provide information for inspections, compliance activities, and laboratory operations.

However, the GAO argues, much of the planned functionality has not been delivered and its completion is uncertain. Moreover, the program lacks an integrated master schedule identifying all the work activities that need to be performed and their interdependencies.

The FDA’s CIO stated that the agency is now reevaluating the scope of the initiative. As a result, it is uncertain when or if FDA will meet its goals of replacing key legacy systems and providing modernised functionality to support its mission.

In addition, FDA has not yet fully implemented key IT management capabilities essential for successful modernisation, previously recommended by GAO. These include developing an actionable IT strategic plan, developing an enterprise architecture to guide its modernisation effort, and assessing its IT staffing needs.

One of the problems for the FDA has been changes in its management structure, which has meant that since 2008, the agency has had five different CIOs, hampering its ability to plan and effectively implement a long-range IT strategy.

The GAO recommended that the FDA should develop both a comprehensive inventory of its IT systems and an integrated master schedule for a major modernisation effort, and assess its  information needs to identify opportunities for greater sharing.

GAO Report

Are your IT projects ‘drivers’ or ‘supporters’?

By David Bicknell

An article by Art Langer in the Wall St Journal argues that IT projects are either ‘drivers’ or ‘supporters’.

Drivers are those projects and activities that affect the relationship with an organisation’s clients i.e. projects that drive revenue directly or indirectly. Supporters, on the other hand, are those everyday activities that are more operational in nature.

Langer cites the work that Dana Deasy has done firstly at Siemens  and more recently at BP.

He writes: “We all know that executives are more interested in implementing technologies to drive the business, than they are in using cutting-edge technology for its own sake. For Deasy, the biggest challenge was mostly building internal consensus about  how the technology would help  customers–and how Siemens could be more competitive in the marketplace.

“Deasy also had to show his executives that the evaluation of investments in these projects would be different than evaluations of other kinds of IT work. With e-business, the market reaction to different product and service offerings can be less certain.

“So Deasy established the concept of “revalidation.” Approved technology projects were reviewed every 90 days to determine whether they were indeed providing the planned outcomes, whether new outcomes needed to be established, or whether the technology was no longer useful.

“Siemens was moving from a traditional process of analyse-develop-deliver to a new process of sensing what a customer might want, and then responding to it more dynamically.”

Langer concludes by saying that, “The idea that all IT projects must succeed is outdated and unrealistic in true “driver” initiatives. CIOs must learn from Deasy’s lesson: If you are engaging in true “driver” initiatives, you cannot evaluate them on the “supporter” method of simple success rates.”

Interesting piece – worth a read.

How to Develop and Evaluate Strategic IT Projects

New York’s CTO to leave as row deepens over city’s handling of IT projects

By David Bicknell

New York, New York (So Good They Named It Twice) – as the song goes -though not so good at delivering successful IT projects, it would seem.

According to The New York Times, the city’s chief technology official Carol Post has resigned after clashing with a deputy mayor over the management of several costly, ambitious IT projects.

According to the newspaper, city government spokespeople said Ms. Post, who is the commissioner of the Department of Information Technology and Telecommunications, should not be blamed for the mismanagement of the $2.3 billion 911 project, whose problems predated her arrival in the job. She is reported to be leaving to take up a new position at the New York Law School. 

Post’s departure  was announced a day before New York’s mayor, Michael Bloomberg said the city would challenge a judge’s order to release a report by consultants McKinsey on an overbudget, much-delayed modernisation of the city’s 911 emergency calls and dispatching system.

According to The New York Times story, concerns have been expressed about the cost of an upgrade to CityNet, the city’s internal data network; there are continuing problems and shortcomings with CitiServ, a data centre that was supposed to consolidate dozens of city agency servers; and a shortage of users for NYCWin, a secure municipal wireless network.

The wireless network cost $500 million to build and a further $40 million a year to operate, and is underused and arguably outdated.

CityNet has experienced interruptions in service, despite a system of redundant fiber optic rings intended to enable it to withstand a breakdown. The $95 million CitiServ project is reported to have confounded agency officials, with the technology department, DoITT, struggling to migrate old systems into the new data centre.

“The technology department is officially referred to by its acronym, DoITT, but is sometimes derided as “Don’t Do It” by city workers who seek to avoid working with the department,” The New York Times said.

Of Post’s departure, Bloomberg said, “Over the past ten years, we have fundamentally transformed the operations of New York City agencies and elevated New Yorkers’ expectations of how efficient, user-friendly and transparent their government should be, and a large part of that is because of the tirelessness and talent of Carole Post. From her work at the Department of Buildings to the Mayor’s Office of Operations to DoITT, Carole has brought agencies together in common cause, finding efficiencies, defining legal strategies and creating collaborations that use taxpayers’ dollars more effectively. There’s nobody better to help a great institution like New York Law School climb to new heights, and though I’m very disappointed to see her go, I wish her well in tackling this new challenge.”

NY’s CTO Resigns, As Some Question Bloomberg’s Handling of City’s Tech Projects

New York’s emergency call IT project: just seven years behind schedule and $1bn overbudget

Standish Group: the 21 perils of using consultants

By David Bicknell

We always have a lot of time for the work of the Standish Group in the US on how and why IT projects fail.

The group’s recent Chaos newsletter makes some strong points about the perils of using consultants. (In fact, in all, it identified 21 perils!)

Standish argues that the number one consultancy misdeed is what is describes as “the X-Factor”. The X-Factor is the difference between what the consultant initially bids to win the contract, and what is ultimately delivered to the client. It is sometimes referred to as “low ball pricing.” These terms accurately reflect the standard practice of bidding on the project as defined. However, “there is conscious intent to solicit, promote, and champion requirements changes.” 

Standish Group continues: “The X-Factor will alter the ultimate deliverable from the project as initially defined and increase the cost. The X-Factor cost increase can occur through requirements analysis and validation. At the end of the process, the unselfish consultant provides recommendations for changes and/or additional requirements based upon user input and their own analysis, demonstrating that the project as originally defined and presented will not meet the business needs, which is something they knew all along. 

“The X-Factor final deliverable is not necessarily better. It might be worse. It is guaranteed to be different. Since requirements changes represent more money, the consultant will encourage changes at every opportunity. The end result of it being more billable hours for the consultant. The X-Factor and the other twenty factors message here is caveat emptor or let the buyer beware.

“On the surface, the X-Factor and the other twenty factors could be casually dismissed as justifiable and acceptable risks of doing business. In reality, they are carefully devised and skillfully practiced techniques designed to serve the primary objective of the consultant to maximize their profit.

“The addition of complexity and confusion is the common denominator. This gets manipulated into project expansion, schedule delays, requirements changes and additions, new hardware, new applications, system integration projects, and a “till death do we part” relationship. The consultant’s hooks are in so deep that the cost of terminating the relationship is unaffordable. The consultant will pretend to be a trusted and friendly advisor until the profit well runs dry.

“When a conflict occurs between the client’s interest and the consultant’s profit, the consultant will protect his profit. “Show Me the Money” was the mantra of the consulting world long before it became a signature line in a Hollywood movie. This mercenary depiction of consultants is not an individual or personal indictment. It reflects the nature of the industry. The behaviour pattern and mode of operation is a reaction to the “survival of the fittest” environment.

“Consultants are under enormous pressure to develop the business; and they face intense competition. This breeds their overly aggressive, relentless pursuit of the bottom line. The consultant is neither friend nor enemy; he’s an entrepreneur in business to make a profit.”

Admittedly, this X-Factor scenario will already be familiar to many companies in their dealings with consultants. Over the coming months, Standish says it plans to take a closer look at some of the other key factors to be aware of around using consultants.

Chaos Activity Newsletter