Mitigating Outsourcing Risks: I

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 welcome

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.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

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.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Decisions, Decisions: II

Most of us have participated in group decision-making. The process can be frustrating and painful, but it can also be thrilling. What processes do groups use to make decisions?

If Only I Had Known: I

Have you ever regretted saying something that you wouldn't have said if only you had known just one more little fact? Yeah, me too. We all have. Here are some tips for dealing with this sticky situation.

Asking Brilliant Questions

Your team is fortunate if you have even one teammate who regularly asks the questions that immediately halt discussions and save months of wasted effort. But even if you don't have someone like that, everyone can learn how to generate brilliant questions more often. Here's how.

Using the Parking Lot

In meetings, keeping a list we call the "parking lot" is a fairly standard practice. As the discussion unfolds, we "park" there any items that arise that aren't on the agenda, but which we believe could be important someday soon. Here are some tips for making your parking lot process more effective.

The Deck Chairs of the Titanic: Obvious Waste

Among the most futile and irrelevant actions ever taken in crisis is rearranging the deck chairs of the Titanic, which, of course, never actually happened. But in the workplace, we engage in activities just as futile and irrelevant, often outside our awareness. Recognition is the first step to prevention.

See also Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.