Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 22, Issue 6;   February 16, 2022: Vendor Mismanagement

Vendor Mismanagement


When we outsource knowledge work to vendors, we expect to achieve the desired result with less risk and uncertainty than if we did the work ourselves. But mission creep, mission retrenchment and employee capture can lead to less welcome results.
A scientifically accurate atomic model of the external structure of the SARS-CoV-2

A scientifically accurate atomic model of the external structure of the SARS-CoV-2 virus. Each "ball" is an atom. The spikes are the tools the virus uses to penetrate cells in the host.

In the context of outsourcing, vendors also seek to penetrate the organizations they serve. Sometimes they manage to "leverage" one mission into several more, working with multiple business units of the payer organization. In some ways, the vendor behaves like a virus, establishing a relationship with the payer that cannot be terminated. Image (cc) by SA 4.0 by Alexey Solodovnikov courtesy WikiPedia

In past decades, a growing share of knowledge work has been performed not by employees of the owner organization, but by vendors and contractors. The differences between vendors and contractors can be somewhat murky. Roughly speaking, a vendor is a business that provides the owner client a result. By contrast, a contractor is a business or an individual that provides the owner client the people needed to produce the result. Vendors provide results; contractors provide services that the payer uses to achieve those results.

For example, consider the task of optimizing snow clearance efforts for a small city. Optimizing plow routes is a necessary step. Because using the needed software and hardware does require some sophistication and special knowledge, the city might hire a contractor to work with city employees to produce optimized routes. Alternatively, the city might hire a vendor to deliver the optimized routes. In simple terms, the vendor is more likely than the contractor to produce the end result without even visiting city offices.

Because both vendors and contractors must be managed, both can be mismanaged. And because the differences between them are significant, differences in patterns of mismanagement are also significant. This post examines three patterns of vendor mismanagement. In what follows, I use the term payer to refer to the organization acquiring the result from the vendor; the term vendor monitor to refer to the payer employee responsible for supervising the vendor and verifying receipt of the result; and vendor rep to refer to the representative of the vendor empowered to speak for the vendor.

Three common forms of vendor mismanagement are mission creep, mission retrenchment, and payer employee capture.

Mission creep
Some vendors have an inherent conflict of interest. They benefit from using the existing agreement with the payer to secure additional business. When the vendor allows this "meta mission" to distort performance of the existing mission, the payer can be harmed.
Often, the vendor monitor is less expert in the subject matter of the mission than is the vendor. And under pressure to complete this task and others, the vendor monitor can be tempted to accept the advice and offerings of the vendor rep without seeking independent unbiased evaluation. Moreover, because of administrative controls within the payer organization, the vendor monitor often finds that creating a new mission for the vendor already under contract is more expeditious than seeking a new vendor for the new mission.
Too often, Because both vendors and
contractors must be managed,
both can be mismanaged
then, an existing vendor is hired to provide a result that would be better achieved by another vendor.
Track the ratio of two numbers. The numerator is the value of new vendor agreements or extensions created for existing vendors. The denominator is the total value of agreements or extensions. Pay special attention to the agreements that involve vendors delivering results that are beyond their usual areas of expertise.
Mission retrenchment
Mission retrenchment is the practice of "downscoping" an existing agreement. A common often unspoken reason for retrenchment is the inability of the vendor to achieve the agreed-upon result in full. The root causes might lie anywhere — within the vendor organization, within the payer organization, or both, or neither.
With respect to vendor mismanagement, the most significant of these are causes that lie within the vendor organization, but which aren't acknowledged as such. A failure mode that can cause significant harm to the payer involves collusion between the vendor rep and vendor monitor. Such collusion need not be malicious. They might have formed a friendship that precludes either of them recognizing both the vendor's failure and the vendor monitor's failure to acknowledge the vendor's failure.
One form of mission retrenchment can be less evident than others. It involves schedule slippage and/or budget creep. By extending the schedule or increasing the budget, the vendor gains additional time or resources to achieve the previously agreed-upon result. Both vendor and payer hope that the additional time and resources are adequate. They can be, if the cause of the shortcoming was miscalculation of schedule or resource requirement. But if the cause lies elsewhere, the extensions won't help much.
Monitor incidents of mission retrenchment. Determining root causes is an essential first step for identifying both substandard vendor performance and unrealistic payer expectations.
Payer employee capture
Perhaps the process most harmful to payer objectives is payer employee capture — expecially when the employee captured is the vendor monitor. Capture occurs when the payer employee begins to feel greater loyalty to the vendor than to the payer. The captured employee then takes steps to transfer credit to the vendor while transferring risk to the payer.
For example, if someone in the payer organization requests an estimated delivery date for some component of the expected result, a captured vendor monitor might recognize that providing such an estimate might commit the vendor to meeting that date, even though it was only an estimate. The captured vendor monitor might then seek to avoid providing such an estimate by choosing not to pass the estimate request to the vendor. Instead the vendor monitor might respond to the request with delays and excuses until the requestor ceases making such requests.
In extreme cases, the vendor rep and the vendor monitor form an alliance to protect the vendor's activities from the effects of the payer organization's process controls.
The indicators of employee capture are plain, but they can develop so slowly that they escape notice until a serious problem develops. Regular status reporting might be helpful; periodic detailed review might be necessary. If capture is detected, reassignment or termination of the vendor monitor might be necessary.

Working with the same vendor over a long period of time, and over numerous efforts, does provide both comfort and efficiency. But the price of that comfort and efficiency can be elevated risk of mission creep, mission retrenchment, and most important, payer employee capture. Go to top Top  Next issue: Disproof of Concept  Next Issue

How to Spot a Troubled Project Before the Trouble StartsProjects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

Your comments are welcome

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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 Project Management:

Finger PuzzlesFinger Puzzles and "Common Sense"
Working on complex projects, we often face a choice between "just do it" and "wait, let's think this through first." Choosing to just do it can seem to be the shortest path to the goal, but it rarely is. It's an example of a Finger Puzzle.
Chocolate chip cookiesNine Project Management Fallacies: III
Some of what we "know" about managing projects just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.
An unfinished building, known as SzkieletorThe Planning Fallacy and Self-Interest
A well-known cognitive bias, the planning fallacy, accounts for many unrealistic estimates of project cost and schedule. Overruns are common. But another cognitive bias, and organizational politics, combine with the planning fallacy to make a bad situation even worse.
John Frank Stevens, who conceived the design and method of construction of the Panama CanalPower Distance and Risk
Managing or responding to project risks is much easier when team culture encourages people to report problems and to question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk.
Auklet flock, Shumagins, March 2006Seven More Planning Pitfalls: I
Planners and members of planning teams are susceptible to patterns of thinking that lead to unworkable plans. But planning teams also suffer vulnerabilities. Two of these are Group Polarization and Trips to Abilene.

See also Project Management and Ethics at Work for more related articles.

Forthcoming issues of Point Lookout

Three gears in a configuration that's inherently locked upComing April 24: Antipatterns for Time-Constrained Communication: 1
Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
A dangerous curve in an icy roadAnd on May 1: Antipatterns for Time-Constrained Communication: 2
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:

Reprinting this article

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

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.