When we outsource internal processes, we create risk. It's no surprise that the risk created varies with the kind of services outsourced. For instance, outsourcing cubicle maintenance creates risks that differ from those created by outsourcing IT, software testing, or product development. When the risks of outsourcing create threats to the enterprise, we mitigate them — if we fully appreciate the risks.
Since some risks associated with outsourcing are inherent to outsourcing, many decision makers haven't encountered them before. Some of these risks are intuitively clear, or have been widely discussed. For example, outsourcing a customer relationship software maintenance task entails some risk of exposure of proprietary information.
But there are other outsourcing risks that are a little less obvious. In the descriptions below, "customer" refers to the organization that decided to outsource some activity, and "vendor" refers to the organization that carries out the outsourced activity.
Part II explores risks associated with the evolution of the processes that are outsourced. In this Part I, I describe risks related to the migration of knowledge to the customers' competitors.
- Knowledge of the outsourcing process
- Knowledge of and experience with the process of outsourcing itself is a customer asset. An example of valuable knowledge: contractual artifacts for managing outsourcing risk. As the customer engages with a vendor, it inevitably transfers that knowledge to the vendor, and from there, the knowledge can migrate to competitors of either party.
- Customers can mitigate this risk by taking care not to reveal intentions during the initial negotiation. Vendors who understand this customer concern can gain trust and loyalty by promising to treat — and then actually treating — contractual terms as if they were the intellectual property of the customer. Often, in effect, they are.
- Improving competitors' processes
- Outsourcing elements Outsourcing elements of internal
processes inevitably transfers
internal knowledge to the vendorof internal processes inevitably transfers internal knowledge to the vendor. When the customer outsources, the vendor necessarily acquires knowledge that previously had been internal to the customer. For instance, the customer might have developed an automated tool for transferring data from one commercial customer relationship management system to another — a tool that isn't available commercially. That knowledge might then propagate to arrangements between the vendor and other customers. Nor is such propagation limited to that one vendor, because its employees carry that knowledge with them when they move to other vendors.
- Vendors who accept business only from selected customers who do not compete with each other provide some mitigation of this risk. Customers can mitigate this risk by favoring vendors who don't serve competitors.
The significance of any risk related to outsourcing depends upon the importance of the outsourced process in differentiating the customers' offerings from the offerings of competitors. The more significant a differentiator the outsourced process is, the greater the risk incurred by outsourcing it. Next in this series Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
More articles on Personal, Team, and Organizational Effectiveness:
- Snapshots of Squirming Subjects
- Today we use data as a management tool. We store, recall, and process data about our operations to help
us manage resources and processes. But this kind of management data is often scattered, out of date,
or just plain incorrect, and taking a snapshot doesn't work. There is a better way.
- Help for Asking for Help
- When we ask for help, from peers or from those with organizational power, we have some choices. How
we go about it can determine whether we get the help we need, in time for the help to help.
- Coping and Hard Lessons
- Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated
mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required
to avoid them is just plain difficult. Here are some examples of hard lessons.
- Virtual Clutter: II
- Thorough de-cluttering at work involves more than organizing equipment and those piles of documents
that tend to accumulate so mysteriously. We must also address the countless nonphysical entities that
make work life so complicated — the virtual clutter.
- Red Flags: II
- When we find clear evidence of serious problems in a project or other collaboration, we sometimes realize
that we had overlooked several "red flags" that had foretold trouble. In this Part II of our
review of red flags, we consider communication patterns that are useful indicators of future problems.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming October 5: Downscoping Under Pressure: I
- When projects overrun their budgets and/or schedules, we sometimes "downscope" to save time and money. The tactic can succeed — and fail. Three common anti-patterns involve politics, the sunk cost effect, and cognitive biases that distort estimates. Available here and by RSS on October 5.
- And on October 12: Downscoping Under Pressure: II
- We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope. Available here and by RSS on October 12.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info