ie8 fix
madison

5 tips to reduce outsourcing risk

By | January 27, 2009, 6:22am PST

Service providers present a special challenge to organizations involved with complex IT projects. Although consultants are integral to many projects, dysfunctional service provider relationships can increase the customer’s risk of failure.

To explore this issue, I spoke at length with Alec Miloslavsky, CEO of Exigen Services, an outsourcing supplier that specializes in Agile development. I asked him why traditional relationships with system integrators sometimes cause a gap between customer goals and consultant interests:

Traditional consulting companies base their relationship model on labor arbitrage, where the services provider gains financial benefit primarily from differences in labor costs. As a result, the consulting firm neglects key issues in IT project delivery, increasing the customer’s risk.

Alec added that projects generally face three types of risk:

  • Financial risk, where project cost rises above expectations
  • Time to market risk, where the project is late
  • Delivery risk, where the project doesn’t achieve planned objectives

Pure labor arbitrage contributes to all these problems, especially in environments where there is insufficient governance to control results.

I asked Alec for five tips to help services customers get the most from their relationship with external consultants. Here is his list:

1. Outsourcing should generate a favorable return. The goal of an outsourcing investment should be achieving a specific business result — not simply buying cheaper labor. Project risks and execution should be shared responsibilities between you and your outsourcing partner. If you structure the outsourcing partnership correctly, risk reduction happens automatically - therefore reducing your costs.

2. Methodology matters. Demand that the specific methodology of outsourcing and project execution is an explicit part of your vendor’s business proposition. Project governance should be the responsibility of the vendor. Make sure that methodology and governance address the risks of project execution, as well as unique risks of distributed development.

3. Success is a joint responsibility. Success is a function of the time and effort invested into the project by the stakeholders (engineering, IT, and business users) . The absolute key to success is frequent and timely feedback by the all the stakeholders, particularly on the business side. Whenever possible, clearly identify the decision-making criteria in advance so that the team can work most effectively to meet your business goals.

4. Things will change. Within any project, change is inevitable. Make sure the business model and the methodology are nimble enough to absorb business change, and that the sign-off approving project change is held in the relevant hands. To ensure maximum project return, reassess and reconfirm priorities periodically during the project, as part of the project execution methodology.

5. Align end to end. Because outsourced projects rely on resources who are working for a different company, there is the potential for staff changes to affect your intellectual property and project control. The best way to minimize this risk is to make sure your outsourcing business model aligns you and your outsourcing vendor all the way from overall business goals down to the staff level. Specifically, verify that the HR and compensation strategy of the vendor aligns with your project goals.

My take. The relationship between services provider and customer is critical to achieving successful projects. As Alec noted, this relationship should be a two-way street with shared goals, responsibilities, and incentives on both sides.

I strongly disagree with those who push responsibility onto one side or the other of this relationship; such imbalances perpetuate negative cycles of failure.

While not a silver bullet, Alec’s excellent advice can certainly help align the interests of customers and consultants to improve project success rates.

[Photo of Alec Miloslavsky from Exigen Services.]

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

Topics

Michael Krigsman is a recognized authority on the causes and prevention of IT failures.

Disclosure

Michael Krigsman

Michael Krigsman writes and speaks about technology in a manner that most observers consider to be fair and balanced. Michael believes that writing about IT failures, which often have complex causes, creates a unique obligation to be reasonable and accurate in both reporting and analysis.

Michael maintains active personal and professional relationships with enterprise technology buyers, vendors, analyst firms (or individual analysts), consultants, and system integrators. As CEO of Asuret, Michael sells and delivers paid services to members of these same groups.

Vendors regularly reimburse Michael's out-of-pocket travel expenses to attend industry conferences and events. Conference organizers frequently waive entry fees when Michael attends industry events. Michael often speaks at industry conferences and events.

He is a member of the Enterprise Irregulars, a loose association of consultants, investors, industry representatives, analysts, and users of enterprise software.

For daily updates on Michael's activities, follow him on Twitter.

Biography

Michael Krigsman

Michael Krigsman is CEO of Asuret, Inc., a consulting company dedicated to reducing technology implementation failures. Asuret's suite of software tools improve the success rate of enterprise software deployments by quantifying and measuring governance issues that cause most project failures. Michael led the research effort underlying Asuret's model of collective intelligence and its practical application to reducing IT failures in consulting environments. He is a recognized authority on the causes and prevention of IT failures and is frequently quoted in the press on IT project and related CIO issues. He is considered an enterprise software industry "influencer" and provides advice to technology buyers, vendors, and services firms.

Previously, Michael served as CEO of Cambridge Publications, which develops tools and processes for software implementations and related business practice automation projects. Michael has been involved with hundreds of software development projects, for companies ranging from small startups to Fortune 500 organizations. Michael graduated with an M.B.A. from Boston University and a B.A. from Bard College. He is a Board member of the America's Cup Hall of Fame and the Herreshoff Marine Museum in Bristol, RI.

10
Comments

Join the conversation!

Just In

RE: 5 tips to reduce outsourcing risk
MFilak 5th Nov 2009
I agree with Alec and his take on the outsourcing relationship. Also agree that you need to know what you outsource. Where I would beg to differ is the the RFQ concept. That in and of itself begins to look at the engagement as a price run-off. Who has the lowest quote? In fact, I would argue that the base processes used for outsourcing today are rooted in the 20th century. I believe that RFIs, RFQs, RFPs should be a thing of the past. What you really want to release is a principles of outsourcing document. This document describes the scope, gives the saliant facts of the environment and the objectives of the outsourcing effort. It purposely avoids any directions that could frame a solution in advance. What the buyer should want is for the outsourcer to innovate - come up with creative solutions and creative ways to price that are outcome (note: I use the word outcome and not output) based.

Additionally, rather than the term win/win (which I also find rooted in the 20th century), the commercial models need to aligned/aligned.
0 Votes
+ -
Outsourcing is unpatriotic (nt)
croberts 27th Jan 2009
(nt)
0 Votes
+ -
How so?
dgalligan 27th Jan 2009
Plenty of outsourcing stays on US soil. It isn't limited to IT processes, either.
0 Votes
+ -
Contributr
Consulting in general
mkrigsman@... 27th Jan 2009
The issues raised in the post actually apply to consultants and system integrators as much as to outsourcers. It's an important and general set of lessons.
0 Votes
+ -
Questions for Consideration
elizab 27th Jan 2009
Which are you opposed to: outsourcing in general (i.e. even to other US domestic companies) or specifically off-shoring?

What if there were plenty of business to go around (meaning no US job was cut to create an off-shore job)? Are you still opposed to outsourcing or off-shoring?

This issue applies to all industries today, from manufacturing, legal research, programming, etc.

Should we ask ourselves the following questions:

* Whose economy(ies) are US dollars directly supporting?

* Are subsidiary dollars that flow from off-shoring equal to or greater than those off-shore US dollars?

* Who actually benefits from subsidiary dollars generated from off-shoring? US workers (white collar and blue)? Senior and executive management? Corporate type investors and raiders (VCs, private equity firms, investment bankers) ?

* Do we make ourselves "flabby" by restricting US work dollars to only domestically located US firms/sites?
0 Votes
+ -
Most important tip to reducing outsourcing risk
Spiritusindomit@... 27th Jan 2009
Outsource to US companies!
0 Votes
+ -
Contributr
You think that changes anything?
mkrigsman@... 27th Jan 2009
I know your comment is not serious, but the reality is that these issues are totally relevant to on-shore or off-shore projects.

You're alluding to political issues, while I'm address successful IT projects.
0 Votes
+ -
I can give 1 good tip for reducing the risk,
DO NOT OUT SOURCE, why put your companies valuable
assets at risk to save a few bucks, you may find out later the cost is higher (like customers who go else where because of crappy support) than you can afford
0 Votes
+ -
Interesting Perspective
elizab 28th Jan 2009
Alec Miloslavksy has an interesting point of view: that "traditional consulting companies base their relationship model on labor arbitrage?" and that doing so creates project risk."

In fact, I believe many companies outsource for that very same reason?lower cost, not that the outsource vendor has capabilities or expertise that are missing in house.

When the focus is so heavily on driving cost down, it generally means that the company who makes that choice:

* Feels that all work and relationships are essentially commodities

* Has decided that quality and predictability are not worth additional dollars, regardless of their professing to support quality

* Has probably put the same care of thought into the conceptualizing of their IT initiatives, which explains initiatives that get kicked off that sound good in theory but fail in practice; or that "lower costs for a company" but cause pain for customers; or that purport to have high ROI, but in reality take vastly longer to achieve breakeven on investment regardless of achieving any strategic benefit.

It?s difficult to craft the close partnership with a client that?s needed in order to follow his 5 recommendations.
0 Votes
+ -
Know what you out-source
meedabyte 5th Feb 2009
At least another important success factor in BPO is
"know what you're outsourcing".
Once you know, apply SLAs on it and go with RFQs.
Anyway, I agree that the concept of sharing goals,
responsibilities, and incentives on both sides (that
we usally call Win-Win approach) is crucial.
0 Votes
+ -
I agree with Alec and his take on the outsourcing relationship. Also agree that you need to know what you outsource. Where I would beg to differ is the the RFQ concept. That in and of itself begins to look at the engagement as a price run-off. Who has the lowest quote? In fact, I would argue that the base processes used for outsourcing today are rooted in the 20th century. I believe that RFIs, RFQs, RFPs should be a thing of the past. What you really want to release is a principles of outsourcing document. This document describes the scope, gives the saliant facts of the environment and the objectives of the outsourcing effort. It purposely avoids any directions that could frame a solution in advance. What the buyer should want is for the outsourcer to innovate - come up with creative solutions and creative ways to price that are outcome (note: I use the word outcome and not output) based.

Additionally, rather than the term win/win (which I also find rooted in the 20th century), the commercial models need to aligned/aligned.

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix