Vendor Mismanagement

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 mismanagedthen, 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.  Top    Next Issue

Projects 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

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.

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:

Project Improvisation Fundamentals

Project plans are useful — to a point. Every plan I've ever seen eventually has problems when it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's Part I of a set of tips for mastering project improvisation.

Why Scope Expands: I

Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?

How to Get Out of Firefighting Mode: II

We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

Seven Planning Pitfalls: I

Whether in war or in projects, plans rarely work out as, umm well, as planned. In part, this is due to our limited ability to foretell the future, or to know what we don't know. But some of the problem arises from the way we think. And if we understand this we can make better plans.

Lessons Not Learned: I

The planning fallacy is a cognitive bias that causes us to underestimate the cost and effort involved in projects large and small. Mitigating its effects requires understanding how we go wrong when we plan projects by referencing our own past experience.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming September 4: Beating the Layoffs: I

If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily before the layoffs can carry significant advantages. Here are some that relate to self-esteem, financial anxiety, and future employment. Available here and by RSS on September 4.

And on September 11: Beating the Layoffs: II

If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily can carry advantages. Here are some advantages that relate to collegial relationships, future interviews, health, and severance packages. Available here and by RSS on September 11.

Coaching services

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