Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Jim Ditmore

Why IT Outsourcing Often Fails

Cost Savings?

(Page 2 of 2)

Another frequent reason for outsourcing is to achieve cost savings. While most small and midsized companies don't have the scale to achieve cost parity with a large outsourcer, nearly all large companies and many midsized ones do have that scale.

Nearly every outsourcing deal that I have reversed in the past 20 years yielded savings of at least 30% and often much more. Cost savings can be accomplished by an IT outsourcer for a large company for a broad set of services only if the current shop is mediocre. If your shop is well run, your all-in costs will be similar to those of the best outsourcing vendors. If you're world class, you can beat the outsourcer by 20% to 40%. A recent example: General Motors' new CIO, Randy Mott, is looking to reverse the company's dependence on IT outsourcing and improve time to market and quality, all while keeping costs in check.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Realize as well that any cost difference an IT outsourcer can deliver typically degrades over time. Consider that the goals of the outsourcer are to increase revenue and profit margin, so it invariably will find ways to charge you more, usually for changes to services, while minimizing the work it's doing. While the usual response is that the customer can put terms into the contract to avoid this situation, I have yet to see terms which ensure that the outsourcer does the "right" thing throughout the life of the contract.

One dysfunctional, $55-million-a-year outsourcing contract I reversed a few years back was for desktop provisioning and field support for a major bank. During a surprise review of the relationship, we found warehouses full of both obsolete equipment that should have been disposed of and new equipment that should have been deployed. Why? Because the outsourcer was paid to maintain all equipment, whether in use in our offices or in a warehouse, and it had full control of the logistics function (here, the critical intellectual property). So the outsourcing vendor had ordered up its own revenue, in effect. Furthermore, the service had degraded over the years as the vendor hollowed out its initial workforce and replaced it with less qualified people.

The solution? We immediately insourced the logistics function and established quality goals. Then we split the field support geography and conducted a competitive bid to select two vendors for that work. Every six months we evaluated each vendor's quality, timeliness, and cost. We gave more territory to the higher-performing vendor and took away territory from the lower-performing one, which was on notice for possible replacement. We maintained a small team of field support experts to keep training and capabilities up to par, update service routines, and resolve problems.

The result was far better quality and service--at a 40% lower cost. These results are typical with similar actions across a wide range of services, organizations, and locales.

When I was at Bank One more than a decade ago, working under CEO Jamie Dimon and COO Austin Adams, they supported our unwinding of the largest IT outsourcing deal ever consummated at the time. Three years into the contract, it had become a millstone around Bank One's neck. Costs were going up every year and quality eroded to the point where system availability and customer complaints were the worst in the industry.

In 2001 we cut the deal short--it was scheduled to run another four years. During the next 18 months, after hiring 2,200 infrastructure staff and revamping the processes and infrastructure, we reduced defects (and downtime) to 1/20th the levels in 2001 while reducing our ongoing expenses by more than $220 million per year. This effort aided the bank's turnaround and allowed for the merger with JP Morgan a few years later.

As for having in-house staff do critical work, Dimon said it best: "Who do you want doing your key work? Patriots or mercenaries?"

In Proper Moderation

Like any tool or management approach, outsourcing is quite valuable when used properly and in the right circumstances. As an executive leader, you can't focus on all company priorities at once, nor would you have the staff. And in some areas, such as field support, outsourcing provides natural economies of scale for many companies.

When outsourcing, ensure that your company retains critical IP and control. Or use outsourcing to augment your capacity, or to leverage best-in-class specialized services.

Since effective management of large outsourcing deals is nearly impossible, do small deals. Handle the management like any significant in-house function, establishing SLAs, gathering operational metrics, reviewing performance with management every three to six months, and addressing problems. Stipulate consequences for bad performance and rewards for good performance. Use contractors, including cloud providers, for peak workloads. With these best practices and a selective hand, your IT shop and company can benefit from outsourcing and avoid the failures.

What experiences have you had with IT outsourcing? Do you see companies getting better at managing and using these services? Let us know in the comments section below.

New outsourcing opportunities for insurance companies are emerging around cloud and Web-based initiatives, mobility, real-time interactive customer service, and data management. What is the new thinking in insurance about outsourcing and what are the new opportunities--and risks--in the current hyperconnected global financial services environment? Download our Optimizing The New Outsourcing Model report. (Free registration required.)

« Previous Page | 1 2  


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.