Who's accountable for IT failure? (part one)

Who's accountable for IT failure? (part one)

Summary: IT failures are a management crisis of serious proportions that have been largely ignored. Here's what senior executives need to know - and do - right now.

SHARE:
TOPICS: CXO, Legal, Software
13

This two-part series presents a structure for understanding why IT projects fail, in a way that goes far beyond project management alone. Part one elaborates the problem while part two discusses the need for greater accountability on the part of senior management.

BE SURE TO READ PART TWO OF THIS SERIES.

=========================

It's a sobering statistic: nearly 70 percent of IT projects fail in some important way, putting the economic impact worldwide at three billion dollars, which corresponds to 4.7 percent of global GDP. And it's a universal problem: setbacks span the public and private sectors, occur in all industries, and often result in substantial economic and productivity losses.

Read Also: Annual cost of IT failure: $6.2 trillion Worldwide cost of IT failure: $6.2 trillion Critique: $6.2 trillion global IT failure stats Worldwide cost of IT failure (revisited): $3 trillion

Just look at these CRM failure statisticsfor the years 2001-2009 - the numbers tell a story of significant problems related to IT project delivery:

  • 2001 Gartner Group: 50%
  • 2002 Butler Group: 70%
  • 2002 Selling Power, CSO Forum: 69.3%
  • 2005 AMR Research: 18%
  • 2006 AMR Research: 31%
  • 2007 AMR Research: 29%
  • 2007 Economist Intelligence Unit: 56%
  • 2009 Forrester Research: 47%

In virtually every case of failure, management fails to anticipate serious problems. Even in cases where challenges are likely, IT failure is too often considered business-as-usual, with executives throwing their figurative hands in the air, in surrender to chance or bad luck.

IT failures happen when managers exercise insufficient judgment, possess too little experience, hire the wrong people, ignore warning signs and, crucially, fail to involve affected employees in a way that eases the path to success.

WHY IT PROJECTS FAIL

Although tempting to blame project managers for failure, we must point attention to senior executives for allowing the conditions for failure to exist in the first place. The underlying reasons fall into three categories:

  1. Unrealistic and mismatched expectations
  2. Conflicts of interest among customers, vendors and integrators
  3. Corporate organization structure that conspires toward failure

Unrealistic and mismatched expectations.Too many executives expect technology magically to solve business problems, an almost delusional misconception that leads to unhealthy risk. Dr. Paul Kedrosky, a well-known investor and economics writer, explains why: "Software is super malleable and appears to create infinite productivity," he says, "which creates a nearly perfect trap for senior executives."

Health-care business services provider, MedSynergies, fell into this trap when it purchased software from Lawson Software. The ill-fated relationship ended in a lawsuit when MedSynergies sued Lawson and hosting provider, Velocity Technologies, claiming the companies:

[C]onspired to lure plaintiffs into onerous, long-term software, hosting and services contracts and then simply failed to perform," the complaint said. "When their software did not work, defendants piled up the services, charging hundreds of thousands of dollars in 'consulting fees' to fix the problems they themselves created."

Although there are two sides to every story, it's clear the parties had sharp differences of opinion regarding software capabilities and implementation process.

In another case of mismatched expectations, farming organization Woolf Enterprises sued ERP supplier Ross Systems over a failed implementation. Woolf's lawsuit states that Ross made:

[P]re-sale promises...that its software would fit Woolf's needs without major tweaks, save for a "grower accounting module..." Moreover, while Ross promised it would develop the grower accounting module at no charge to Woolf, it never had any intention of doing so, according to the complaint.

Forensic financial analyst and blogger Francine McKennaadds, "We let business off the hook because IT is complicated." In both the previous examples, the lawsuits are rooted in business, rather than technology, disputes. However, when technology is involved, many executives relinquish accountability they might otherwise retain.

Read Also: IT failure and collaboration: Ten big symptoms Design thinking: A new approach to fight complexity and failure Amplifying 'weak signals' for IT success Three simple truths of failure

A recent failure involving ERP vendor, Epicor, demonstrates this critical point. In a lawsuit filed earlier this month, Group Manufacturing Services claims that Epicor misrepresented the functionality and ease of implementation of its software. Epicor's response states that the customer chose to implement the software itself to save money, and "adopted a go it alone mentality, despite Group's lack of experience." To an outside observer, it appears that Group over-estimated its own ability to manage the implementation and tried to pass blame to Epicor.

Of course we cannot ignore technology as a complicating factor on business-oriented IT projects. Beverage distributor, Major Brands, describes this situation in another lawsuit against Epicor. After years of cost overruns and delay, Major Brands scrapped its ERP project, for which it paid about $1.2 million (including software and related implementation services). The big culprit, according to the lawsuit: the software was so slow as to be "absolutely useless."

Although technology itself plays a role in some IT failures, far more often the problem is connected with the customer's inability to cope with organizational change, conflicts with vendors, lack of training and other management issues.

Conflicts of interest among customers, vendors and integrators. Implementing enterprise software typically involves multiple groups, each with its own set of interests, goals, and measures of success. For example, when IBM faced lawsuitsin the Philippines over a failed government project involving the company's DB2 database product, tensions rose among the customer, IBM, and the system integrator. All three parties pointed fingers at each other in a series of public accusations.

Similarly, when California's Marin County sued Deloitte Consulting and SAP for fraud, it became clear how conflicting goals and agendas among customer, software vendor, and system integrator could drive failure rather than success on business transformation projects. The Marin County case is a glaring example of a concept we can call the IT Devil's Triangle.

Read Also: Exploring the Devil's Triangle Five tips from inside the Devil's Triangle 'Pain chains' and the IT Devil's Triangle The IT 'Devil's Triangle' [podcast] The ERP devil's triangle Software pricing and the Devil's Triangle Roche CIO discusses IT, consultants, and the Devil's Triangle [podcast]

I wrote the following about the Devil's Triangle principle:

Three parties participate in virtually every major software deployment: the customer, system integrator or consultant, and the software vendor. Since each of these groups has its own definition of success, conflicts of interest rather than efficient and coordinated effort afflict many projects.

The Devil's Triangle explains how economic pressures can drive software vendors and system integrators to act in ways that do not serve customer interests. It also offers insight into the ways some enterprise software customers damage their own projects.

Many IT projects succeed or fail based on how the three groups manage built-in tensions among themselves. The likelihood of success increases when each group aligns goals and expectations in a spirit of cooperation and mutual benefit. Conversely, implementations fail when greed, inexperience, or arrogance emerge as prominent motivations among participants or stakeholders.

Corporate organization structure that conspires toward failure. Since most CIOs don't have the board-level status of other business leaders, they lack the ability to marshal crucial resources that could dramatically improve the likelihood of IT project success. Executive Director of the Center for CIO Leadership, Harvey Koeppel, believes that many companies treat IT as a second-class citizen: "Instead of integrating IT into broader business activities, many organizations position IT as a technology black box."

In my experience talking with a variety of organizations, it is clear that executive attitudes toward the CIO vary substantially. While some organizations treat the CIO as a strategic senior executive, many companies relegate IT to substandard status and prestige.

The extent to which the CIO participates as a peer with other executives in decision-making and external communications is a clear differentiating factor in companies reporting success with IT projects. SAP's Oliver Bussmann, is an example of a CIO who is fully integrated at a strategic management level in the company. In addition to running a global IT shop, Bussmann serves as one of the company's top external voices.

I asked him to explain why this is important:

Today, IT is much more than just a cost center. As CIO, you must remain ahead of new trends, know what is coming, and work out how you can implement without disruption.

The consumerization of IT is the driver for many business decisions today, so the CIO must be a business front-runner and leader, rather than a follower. SAP Global IT is one of SAP's best customers and I share those experiences on our blog. In addition, I have built up many customer relationships via social media channels, which have become an essential business communications tool.

To the extent that IT is disconnected from lines of business, the conditions for failure become intensified. For many organizations, the challenge lies in putting ideals of communication and collaboration into practice. As with all culture change efforts, bringing together IT and the business requires a shared commitment extending over a lengthy period - there is no quick fix.

Also Read: Recognizing the top 25 'social' CIOs Why CIOs fail - A short primer on success CIO view: Ten principles for effective collaboration CIO view: Business requirements and the elegant art of 'no'

When discussing this issue with the former federal CIO of the United States, Vivek Kundra, who is now Executive Vice President of Emerging Markets at salesforce.com, he responded:

Even if every IT project in the public and private sectors were successful, end users would still be unhappy with the result. In general, these projects are not designed for today's social era and do not deliver direct value to end-users. There is a huge disconnect between what technology builders create and the value that end-users demand.

It is no coincidence that both these leaders raised the issue of communication when discussing how to overcome structural impediments to IT success. The innovative CIO of Seton Hill University, Phil Komarny, agrees:

To reduce failures, we must break down the walls between IT and business constituencies, to make everyone a stakeholder and align interests around the table. By engaging in a more social and collaborative dialog with line of business peers, the CIO can bring greater transparency to the entire IT process.

====================

Part two of this essay discusses the critical topics of risk and accountability. It also describes the impact of these failures on shareholder value and company reputation, and offers advice to management.

Topics: CXO, Legal, Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

13 comments
Log in or register to join the discussion
  • Note also that this conversation could be extended into, wait for it, wait

    Small box (PC/Mac/etc) software which has been a perpetual nightmare to use.

    For these there are also plenty of show-stopping bugs in such as Word (and there are plenty of other vendors that fit this profile) that have been around for as long as the product.

    It's bloody surprising that the world of software works at all, let alone well.
    ego.sum.stig
  • Technical Support Engagement

    Regarding a subset of this article...I am in technical support and work closely with ERP deployments to ensure that the transition to support teams at the end of stabilization goes smoothly. This means aligning expectations with the project team and the business while protecting the production environment and preparing support personnel for the deployment. I am having a hard time finding out how other industries and/or businesses perform this same task. Can anyone point me to a website, article, blog, etc.?
    RoniV
  • I've seen my share of disasters

    I've seen a good many disasters in my career and they all came down to management willfully ignoring users' needs - both in-house and customers. The successful projects were always based on a painstaking search for quality and user satisfaction. User satisfaction doesn't mean just listening to users - it may entail introducing completely new procedures and processes, but the user experience must be always taken into account, besides the expected business results. Every level of management must take responsibility, from corporate strategy to supervisor, at the appropriate level. I believe that ignoring users' needs and expectations is a bad case of [i]hubris[/i] and history - both ancient and recent - teaches us where [i]hubris[/i] leads.
    mainvision
    • Part of it is cultural

      If techies are looked down on as people not smart enough to have gone to business school, then management is asking for trouble. But then again, if the techies don't interact with the people expected to use the system enough to determine what they actually need, then the odds of a successful system are low.
      John L. Ries
  • Real Impact of Project Failures

    "putting the economic impact worldwide at three billion dollars, which . . ." also means that an equal oir larger sum of money is allocated and paid out to others to fix the failures. Using (current) government accounting methodology, this means that failure grows the economy by re-circulating money from one segment to another.

    ( Oh, how I wish there actually was a 'snark' font available. )
    WCarlS
  • Alignment and governance

    From my experience, there are a number of reasons. But looking at successful projects gives some hints. Strong ownership at the highest levels in the company. Strong governance model with a multiple-tiered approach to governance. Real focus on partnering with aligned and transparent objectives. Strong and disciplined programme management. Regular achievable milestones. Quantified business benefits.a focus on celebrating success!
    ebbeckt@...
  • Global GDP

    Is 63 Trillion Dollars. I.e. 3 Billion is .0047%

    Not such a big problem after all
    chris.wilson@...
    • Thank you

      ... for pointing that out and saving me the trouble.
      12312332123
  • Well, obviously it can't be the IT wease... um, I mean, staff

    All they do is write the specs, hire the vendors, spend the money. No, it must be those pesky end users that IT never gets around to asking about their needs. They're only end users, after all. The project isn't about THEM, for heaven's sake.
    Vesicant
    • That has nothing to do with IT

      The majority of IT is there to support users and that is what we do. The problems being described come from the top down. IT Managers/CIO's rarely know anything about the technology and expertise they supervise and project managers know EVEN LESS than that. Yet they are the ones that drive IT decisions. Millions are spent, yes, but these expenditures are approved by the board/executives. The end results are rarely in line with what was promised, but as long as the corporate world puts its trust in managers and methodologies that they can see in a flow chart (and draw on with crayons), instead of common sense and technical experience these failures will continue. Again, it is a managment problem, NOT an IT problem.
      12312332123
    • Not IT

      From the projects I have been involved with, the specs come from on high, i.e. the various business departments. They are also heavily involved in selecting the overall solution and the vendors. Maybe the CIO is involved along with the possiblity of an IT department manager or two. What the rest of the IT department gets is a dictate from above that this vendor will be coming in to implement their solution for the stated business needs and we are to do everything possible to make it happen. And if anything goes wrong, we are the ones who will be blamed.
      ultimitloozer
  • Technology does NOT solve problems, but may help implement solutions

    1. Solve the business problem.
    2. Evaluate technology that could HELP implement the solution.

    Too many organisation try to do these in the opposite order.
    Patanjali
    • Agreed.

      Agreed. +1
      CobraA1