Note: You are experiencing only the raw content of this site, without the intended layout and design. Either your browser has ignored the Cascading Style Sheet (CSS) files for this site, or you are using an outdated browser which does not support Web Standards. Learn more.

Home « Blogs

EDS' Next Big Thing Blog: Read and Respond to What the EDS Fellows Say About Technology

Read and respond to what the EDS Fellows have to say about the future of technology on EDS' Next Big Thing Blog on eds.com.

Outsourcing and innovation

by Charlie Bess

I was in a meeting recently when Tom Hill (another EDS fellow who posts entries to this blog) was talking with some folks about the Technology Adoption Curve that Geoffery Moore introduced in his series of books (Crossing the Chasm…). It got me thinking about the conflict between outsourcing and the need to inject innovation and thought leadership.

It seems that when some organizations outsource a function, it’s because they don’t want to know the details and want to trust someone else to operate the task. They view the work as being in the main stream and not of real strategic advantage (at least not the way they were doing it).

The problem appears when the outsourcer, who takes over the work, wants to improve the environment using new techniques (since it is in their area of expertise, you’d think they should know some better ways). This new approach is a change and viewed as risky by the outsourcing organization.

They don’t want to understand it, and yet don’t want to accept the advice of someone who is knowledgeable about what needs to be done in this area. Obviously, this is a recipe for stagnation and frustration and possibly dissatisfaction with the outsourcing arrangement.

This change by the outsourcer may even enable the outsourcing organization to reach a new level of business value generation (yet more change). That’s why organizational change management may be as important to an outsourcer as their ability to execute. Having a functional governance process is also critical, since the business value generated by the change should be discussed openly in this sort of enterprise level setting - especially when it involves techniques that are by their very nature enterprise wide (e.g., SOA, or business rules deployment).

The challenge for the technical services companies in the second half of this decade will be to be viewed as a value delivery partners and not (just) as people who can execute and hide the details. Response to this issue has been on the rise in Business Process Outsourcing, where the entire business function is outsourced, not just a silo within the process. A counter balance would be Software as a Service where the capabilities are provided but the organizational issues remain to be addressed internally, instead of outsourced.

Published Monday, January 23, 2006 2:13 PM

Subscribe to this post's comments using RSS

Comments

# Posted by vinnie mrichandani Monday, January 23, 2006 4:46 PM

Charlie, what's frustrating to me is how little the services industry is talking about how IT is evolving and innovating. It is a bigger, more global industry than many verticals it services - yet does not like to talk about its own supply chain, how customer service is improving, what technologies and best practices it is implementing.

Indian vendors talk about their GDM and CMM initaitives - that is innovation, but they have been saying it for a while. The industry needs fresher ideas because their is so much waste as I wrote in my post Frederick Taylor and Technology services at

http://dealarchitect.typepad.com/deal_architect/2006/01/frederick_taylo.html

# Posted by Richard Veryard Thursday, January 26, 2006 4:35 PM

A key implication of this asymmetric interaction between supply-side risk and consume-side risk is that complex high-tech outsourcing requires collaborative governance. We are starting to see a number of complex systems engineering programmes exploring new ways of managing procurement. See the asymmetric design blog at http://www.asymmetricdesign.com/

By the way, you should really credit Everett Rogers for the Technology Adoption Curve. Moore's contribution was that there was a critical discontinuity in the curve, which he called the Chasm.

cheers, Richard

Post a New Comment

: required  
required  
optional
required  
Please only click Submit once.

Subscribe to EDS RSS Feeds

I would like to receive the EDS Newsletter