Small Business Resources, Business Advice and Forms from AllBusiness.com

Business Exchange

More reliability, less potholes

By:Robert Mueller
Publication: Purchasing
Date: Thursday, November 18 2004

Outsourcing IT is nothing new. But in recent years it has changed shape several times to reflect new, and arguably better-planned, organizational objectives. And best practices for creating contracts are now evolving that promise to move outsourcing from a road often pockmarked with potholes and lawsuit-bound to a more reliable relationship for both provider and customer.

And although the practice is still leading-edge, contracting for outsourcing joins other service spends in the portfolios of procurement departments. "It's part of a logical evolution," says Bob Talbott, vice president, supply management for Fireman's Fund Insurance in Novato, Calif. "To get out of the typical churning-and-burning purchasing transaction mode, as a discipline we had to [prove] that we have other skills—business analysis, financial analysis, process reengineering, the ability to facilitate cross-functional teams, the ability to make sure the supplier base aligns with company strategy—[because] those skills, which a lot of procurement groups honed through service contracts, are directly transferable to IT outsourcing contracts."

Worldwide, outsourcing was a $293.4 billion industry last year, according to a study by Gartner. The Stamford, Conn. market research company estimates outsourcing will grow to $429.2 billion by 2008, a 7.9% compounded annual growth rate. Although that's way down from the late 1990s, when growth was pushing 20%, it's high enough to make it one of the brighter spots in the entire IT industry, according to Robert Brown, principal analyst for Gartner and one of the authors of the study.

Outsourcing watchers divide the market into two segments, information technology outsourcing (ITO) and business process outsourcing (BPO). ITO consists of outsourced IT activities, usually ongoing, longer-term ones, as opposed to project work like software development and new system implementation. BPO includes outsourced business functions and usually carries with it associated IT activities—customer relationship management (CRM) systems with customer service functions, for example.

Both ITO and BPO have been around for decades Although BPO is growing faster, ITO is still the larger of the two segments.

ITO is, by most accounts, the more mature, but companies have routinely outsourced their payrolls for almost half a century. What's new in both segments is a growing variety of services and greater demand for those services from outsourcing customers. ITO has grown to include anything from the help desk to complete IT departments, and BPO now includes entire customer service departments, HR (Human Resources) operations and even procurement. Offshore BPO, especially when it's a customer-facing process like customer service, has become a political hot button.

"The first wave of outsourcing was strictly IT," says Brown. "We started to see IT outsourcing gain traction in the 1980s and into the early 1990s as very big-ticket, holistic swapouts of IT departments, where the entire department was thrown over the fence to the service providers."

By the second half of the 1990s, Brown continues, more specialization began creeping into ITO. Outsourcers began focusing on desktop management, networks, help desk services, security, server hosting and so on. Today, "you've got two tracks of IT outsourcing. On one hand, you still have companies pursuing big, strategic megadeals. On the other, you have more selective outtasking." The latest ITO trend is toward what Gartner calls utility services-outsourcing, but on a pay-as-you-go basis. Though a hot topic among analysts and service providers, utility services are still immature and many potential customers are hanging back.

The history of BPO is almost the inverse of ITOs. "If you started off in IT outsourcing with big, holistic deals, in BPO you often started out with very selective deals," he says. "Payroll outsourcing, for example, has been happening for years, though companies may not even have thought of that as business process outsourcing. By the late 1990s, there were companies that elected to do very holistic outsourcing of entire processes. HR and finance and accounting have been the typical areas where we've seen those big, strategic deals."

More recently, Brown adds, companies have begun outsourcing select subprocesses—benefits administration and payroll, for example—instead of the whole HR function. More specialized BPO services are also evolving to meet the needs of specific industries: check clearing services and credit card processing for financial institutions, for example.

"The entry point for business process outsourcing is an entirely different buying center than for IT outsourcing," Brown says. "IT outsourcing is still very much the domain of the CIO (Chief Information Officer), where BPO is absolutely a CFO-led (Chief Financial Officer), and in some cases a CEO-led (Chief Executive Officer), undertaking, depending on the magnitude of the contract in question. There's a lot of input from business unit managers. Worst case, the CIO is the last to know."

Outsourcing remains popular because when it works, it saves money. "Companies today are being driven to deliver more services, more functionality and more value for less money," says James Champy, business author and chairman of Perot Systems' consulting practice in Boston. "It's all part of a broad and pretty dramatic improvement in productivity that's going on in multiple industries." Outsourcing is usually just a way to keep costs in check.

A few years ago, Champy recalls, a lot of outsourcing was driven by companies' need to find IT competency they were lacking. The outsourcing providers delivered expertise as well as savings. And before that, companies went to providers to cash in their IT investments and improve their balance sheets. "The deals that were around 10 years ago were deals that had companies selling their IT operations to outsourcers, and some of that still goes on. When they did that, they took an asset that showed little or no value on their balance sheets, sold it for $100 million, and suddenly you had more on the assets side of your balance sheet."

But savings today is more likely to involve concentrating assets and effort on core competencies, and outsourcing noncore activities to specialists. "Take payroll outsourcing, classic BPO," says Bob Rosetta, chief sourcing officer for JP Morgan Chase in New York. "Is payroll a core competency of my business? No. Are there people out there to whom it is core? Yes." Outsourcers have the tools and the expertise to do the job better and cheaper, he notes.

"You have to ask, 'How consistent is the outsourced service with the primary purpose of your corporation?'" adds Sean Chou, chief technology officer of Fieldglass, a Chicago company that makes a software product called InSite that helps users create and monitor outsourcing contracts. "If it's something you feel has nothing to do with your strategic direction and has nothing to do with your primary product, then it's an area you don't really want to build up expertise in." Nor is it usually an area where it makes sense to invest heavily in equipment and staff. "You tend to build out all this stuff to handle peak capacity, when in fact, 80% of the time you're nowhere near that peak capacity."

Historically, outsourcing has been prone to failure. "A lot of these deals are golf course deals," says Dave Whitinger, director of consulting for International Computer Negotiations, a consulting firm that helps organizations work out successful deals with outsourcers. Whitinger is also program director for Caucus, an organization that aims to improve procurement of outsourcing services. "The suppliers are smart enough to dial in a deal with the senior executives, and then it kind of comes down from the mountain. There is no disciplined process. Those are the kind of contracts that are really one sided and they're the ones that wind up in court."

Another reason deals go bad is that business conditions change and contracts with outsourcers aren't flexible enough to take that into account, according to Whitinger. "If you went out and did an honest survey of clients who have outsourced work and technology, you would find a surprising amount of discontent. A lot of that comes from the fact that the service providers are doing a superb job of running the operations, but they're not able to respond to business changes that clients often have because the deals are rigidly structured. There's very little room to add the value that the client ultimately wants."

Rosetta agrees: "If you look at some deals that are multiyear—say five, seven, 10 years—they're very difficult deals to craft. You need a contract that's extremely flexible to change with business conditions." A lot of outsourcing deals fail because they're put together poorly in the first place, he continues. "If the client didn't really understand what he wanted, then clearly he's going to have a disconnect with his supplier. The more mature your sourcing process, the better your odds of doing a good deal that's going to last."

"One of the biggest pitfalls is that you get what you contracted for, but it's not what you need," says Talbott. "That happens because of a lack of clear business strategy. If the sourcing department isn't in lockstep with the overall company strategy, then you could end up with a wonderful contract, but it's not what the business needs." A similar danger, he continues, is lack of confidence in where your business is headed. "A lot of these deals are done with projections on demand or the business environment, and the outsource provider makes its investments based on that. You've got to be very careful because that's a relationship destroyer if you aren't open, honest, and do the due diligence to make sure you know what you're talking about."

Another potential problem, Talbott suggests, is control. "It's important to set a level that you feel comfortable with. Too much, and you end up micromanaging your outsourcer. The outsourcer becomes a group of contract employees, rather than a true outsource provider, and much of its value disappears. Too little control could put you in a situation where you don't know what's happening with a key business process."

Perhaps because outsourcing contracts have had their share of problems, more of them are coming under the purview of procurement departments. Whitinger reckons procurement is involved in about half of all companies, though the extent of that involvement varies greatly. "In some organizations, it's just approving the purchasing order. But in the organizations that follow best practice, there's a dedicated purchasing team with folks that understand how to do technology deals."

Rosetta sees a divide between larger and smaller firms. "I think the groups that are more mature and have a large level of spend have sourcing or procurement organizations. Their operating models are varied, but in the larger organizations, there probably is some formal sourcing process that they use to get these deals done." In fact, he says, outsourcing deals aren't a whole lot different than any other service buy, though an extra measure of diligence is often necessary when contracting for ITO and BPO because many providers are new to the business.

Purchasing must be involved in setting up ITO and BPO deals, says Chou. "They have to shepherd the process the way they always have in terms of just selecting the provider. They are definitely going to be the experts when it comes to conducting a fair and impartial evaluation of suppliers. They're unquestionably going to have better expertise in that area than anyone else in the organization.

"Purchasing as an organizational construct has really emerged in the last few years. Its power and effectiveness has been growing steadily, and it's shown how effective having a purchasing organization can be—first with goods and then with contract labor and now with more and more services. I see purchasing organizations growing in power and influence as they complete one successful project after another. They've been able to prove that they are generating returns on investment because they're dealing with hard dollars."

Best practices for ITO and BPO purchasing

Best practices for contracting with ITO and BPO providers exist, but they're still evolving and aren't yet widespread. "Some of the bigger firms have disciplined procurement processes in place, but some of them don't," says Dave Whitinger, director of consulting for International Computer Negotiations Inc. Nevertheless, there are practices that consultants and procurement executives agree are important to success.

  • The most important thing, says Robert Brown, principal outsourcing analyst for Gartner, Stamford, Conn., is to "understand your motivations for outsourcing in the first place. What strategic objective are you trying to achieve through outsourcing? A lot of companies go into the process of outsourcing as if it's merely an exercise in cost reduction. They very quickly realize that there are other aspects to outsourcing that can be achieved by focusing on the strategic, core mission of the business."

  • Acquiring ITO and BPO services is always a group effort. At JP Morgan Chase, there's a standing strategic sourcing group that includes teams trained to work with the company's CIO and infrastructure organizations in IT, and with internal client groups to structure process outsourcing deals. Legal, finance, risk management and others are included, as the nature of deal dictates. "We put together cross-functional teams and we lead the projects that way," says chief sourcing officer, Bob Rosetta.

  • Bob Talbott, vice president, supply management, Fireman's Fund Insurance, also stresses the team approach. "There has to be a cross-functional team," he says. "I want my group to be the subject matter experts on the process of outsourcing. I want the [internal] client to be the subject matter expert on the area that's being outsourced. Both of those things have got to be there, and they've got to be complementary."

  • Flexibility must be built into ITO and BPO deals, so they can accommodate changing business conditions. "The most important thing is to craft the initial contract with the idea that it will change," says Talbott. "I was taught as a junior buyer to make a contract as bulletproof as possible. If you go into an outsourcing agreement like that, you may have covered your risk, but you've also limited any flexibility to react to business change down the road. The bottom line is this: It's about balance."

  • Flexibility, however, does not mean abandoning performance benchmarks and service level agreements. One reason outsourcing deals fall apart is that they're hard to track, says Sean Chou, chief technology officer, Fieldglass. "Your contract is meaningless if it's not going to be enforced and adhered to." Brown recommends performance benchmarking before contracting to establish a baseline for the outsource provider.

  • Less quantifiable is what Chou calls fit-comfort issues like the supplier's corporate culture and management style. "An ITO supplier is square in the middle of our business, so the fit is very important," says Talbott. "You've got both upstream and downstream issues with that outsourcer. If we're talking about a logistics provider that handles our shipping and outbound function, then fit isn't nearly as important as performance metrics."

Offshore outsourcing: It's controversial and growing

Sending ITO and BPO offshore, especially to India, is a hot topic on television news shows and in political debates. Those who oppose the practice say American jobs, at a time of high unemployment, are being shipped overseas. Those who support it point to lower costs that eventually sift down to consumers. They note that in any case, outsourcing work to foreign producers—in such diverse industries as garment manufacturing and electronics assembly—is a horse that's been out of the barn a long time. Who's right?

The entire IT services industry in India, and that includes ITO, BPO and project work, amounted to only 1.4% of worldwide IT services revenue in 2003, according to Gartner That works out to a little under $8 billion. IBM's IT services revenues from Europe, the Middle East and Africa alone last year amounted to $14.6 billion. Of the 10 leading IT services suppliers, only two are foreign companies, and both of those are Japanese. But U.S. services firms are using offshore outsourcing themselves, and the extent of that practice is hard to pin down. "We wouldn't consider doing a large, U.S.-based IT development project without somehow having an offshore capability," says James Champy, business author and chairman of Perot Systems' consulting practice in Boston.

Although offshore outsourcing is still a small percentage of the total outsourcing spend, it's growing rapidly. According to Gartner, Indian IT services grew 29% between 2002 and 2004, compared with 4% growth among U.S. suppliers. "The economic case for moving certain forms of work offshore is too strong, and the quality and competency with which that work is done offshore is too good to ignore," Champy says.

The most controversial forms of offshore outsourcing happen in the BPO arena in front-office applications like call centers, where a customer dials a toll-free number and gets a customer service rep in New Delhi or Mumbai. Most of those scenarios are still experimental, says Sean Chou, chief technology officer, Fieldglass. "For every story you see where it works, there's another where it failed and the customer has taken the process back inhouse. I think it's an inevitable trend, though. As the expertise and sophistication of offshore outsourcing providers increases, they will compete in those areas, as they have in technology. And that's not necessarily a bad thing."

The number of jobs lost to offshore ITO and BPO isn't very large, says Champy. Of more concern long-term is a possible drain on domestic IT talent as potential computer science majors see programming jobs moving out of the country and direct their educations to more promising areas.

"This is only anecdotal," Champy says, "but I see students hesitating to go into computer sciences programs, particularly in colleges and universities that had produced lots of analysts, so-called systems engineers and programmers. People are saying, 'Why should I go into this field? It's all going to go to India.' I think there's some chance that our talent pool in this country will start to dry up. Even as prices go up elsewhere, you won't see a resurgence of programming and coding in this country."

In addition, make sure to read these articles: