Scope of the Topic: This guide aims to highlight the key components of vendor management spanning the lifecycle of a project, including selection and evaluation criteria, contracting and legal essentials, performance reviewing, and tips for managing relationships to ensure success through effective integration of the vendor in the project.
Managing external vendors can make or break your project. I learned this the hard way when a key supplier missed deadlines on a critical software implementation, resulting in severe cascading delays on the entire project. That experience taught me that vendor management is not administrative. It is a critical strategic role that has a direct impact on the outcome of the project. In fact, the emphasis on vendor management in PMP certification training courses is because the majority of the resources for most projects are external.
70% of a project's activities are performed by external vendors, yet project managers still see vendor relationships as transactional and not strategic. This is the reason why poor vendor management results in budget overruns and schedule delays of 15-25% in any organization. The positive side to this is that systematic vendor management is extremely beneficial. If you spend time on selection, you will greatly reduce the stress on yourself from the vendor and the resulting stress on the project through effective contracting, objective performance assessments, and genuine relationship-building.
Vendor management is the process of selecting, contracting, and coordinating external suppliers throughout the course of your project. It begins when you recognize the need for external resources and ends when you accept the final deliverable. It is different from procurement, which focuses on the purchasing process. Vendor management addresses the relationship and contracts signed afterwards and is a core competency reinforced through formal PMP training.
Vendors can be considered as external team members. Other than providing specialized skills, they can also provide equipment, materials, and services which your internal team lacks, and which you have employed them. Balancing the multiple priorities of quality, cost, time, and relationship is critical in management.
The scope includes more than simple task delegation. It also involves coordinating dependencies, monitoring performance, resolving conflicts, managing payments, and ensuring that deliverables fit seamlessly with your project. Knowing the components of the project management plan helps you understand where vendor management fits in the overall project governance.
I break structures of vendor engagements into four stages:
The Selection Stage takes 2-6 weeks and depends on the level of complexity involved and how well-defined the requirements are, which should involve researching potential vendors, issuing requests for proposals, evaluating the responses to identify the best vendor, and then negotiating the final contracts. If you are specific and detail what you need, you will leave room for the expertise of the vendors to shine through. Rushing through the selection stage will create problems that will haunt you throughout the entire project.
The Onboarding Stage helps vendors get fully operational by investing time to establish proper communication channels, which helps to run detailed kickoff meetings where you share project context, goals, and any constraints, in addition to providing access to the right tools and channels. This helps to avoid poor onboarding, which costs time and causes confusion that can linger for months. Prioritizing this helps avoid the scenario, which I have witnessed multiple times, where vendors did not fully grasp the project's priorities or constraints.
The final stage I call Performance Management, which takes place throughout the entire vendor engagement. I recommend setting up weekly meetings with critical vendors to review their work and doing monthly reviews with others to keep the cadence of the engagement. This will help you to address roadblocks promptly and keep the payment cycles moving, so you can maintain timelines and avoid having to review the bigger problems later. I also recommend tracking a PM (Project Management) level KPI in project management to help in measuring the vendor's contribution.
The end of a project includes a closeout stage. It involves finalizing all payments, collecting feedback, archiving all documents, and keeping relationships professional for future opportunities. It is important to remember that many project managers do not close out correctly, but doing it properly is important for network and organizational learning.
Project managers should remember to evaluate their vendor's performance. This is best done using objective metrics. Legend Consulting and P2K Consulting cite these metrics as the industry standard:
These metrics form the basis of any evaluation and assist in future communications about accountability if there are any issues.
There is a pattern to the problem of selecting the wrong vendor. My criteria are a consequence of balancing multiple priorities, starting with technical capability. This includes a thorough review of referenced project experience. It includes the evaluation of marketing materials. Cost is always the next consideration. The cheapest vendor is often the most expensive. Budgeting in project management is a key factor that is evaluated. The last factor is cultural fit. Do not overlook the importance of alignment in work ethics and collaboration, as it is key.
Assessing risk involves detailing key concerns and strategy pivots. Outline financial risk and mitigation strategies. Understanding types of project risk will help describe vendor-related risk.
Good contracts capture agreements which are risk-defining and shield against the loss of project scope. Mandate contracts include:
Avoid ambiguity and undefined goals. Use high quality means nothing to describe thresholds. Clear scope to test and ensure no critical defects. Updated training enhances knowledge of scope agreements in a guiding and defining structure.
Service Level Agreements (SLAs) define and refine business expectations. Detail response time and define and outline consequences for non-performance.
The absence of clear and defined expectations and the calibre of anticipation between the vendor and the client. Vendors fail to deliver on defined expectations, attributed to the absence of expectations. Clear and defined scope capture and guideline objectives, sustained communication and feedback, proactive monitoring, and mutual agreement are key.
The absence of defined expectations and quality objectives increases the susceptibility to quality gaps. Establish the absence of defined quality expectation intervals to deliver a clear scope. Prior to scope acceptance, quality checkpoints should be established.
The extent of defined control on scope changes increases with the absence of control gaps. All changes should be channelled through documentation, and scope keepers define and control the objectives of the overall scope.
Dependency risk is elevated with the exclusion of defined control gaps on a single vendor. Defined control gaps outline the scope of project leadership.
The best vendors become real partners; for me, building a number of strategic partnerships is a consistent success driver compared to transactional relationships.
Partner with vendors. Share the context of a project, invite feedback, appreciate, publicly acknowledge, and pay for value delivered on time. These create the right permissive environment for goodwill, which is the best currency in times of flexibility.
Be openly candid and forthright about the challenges. If vendors do not know about a given problem, they cannot help solve it. Therefore, the problem boundary honesty paradoxically fortifies the partnership.
Retrospectives and collaborative problem-solving encourage vendors to do more. Differentiating the benefits of project management to include the value of the relationships created is useful.
Coordination is more efficient with the right tools.
Projects with management software are easier because there are shared visibility tasks. Vendors are able to see the expectations set, and they can transparently update their status.
Using a document management system is useful for organizing contracts and deliverables. There is less confusion with version control.
Increased collaboration is the result of a platform, such as Teams, which can create private, dedicated channels for rapid communication with major vendors.
Performance dashboards simplify visualization of metrics. Issues that need to be addressed are made more visible.
The outcomes of projects are greatly improved with the effective management of vendors. Systematic approaches are what determine struggling versus fully utilizing the capabilities of vendors. Clearly outline expectations and selection criteria, and take your time when choosing vendors. Clearly document expectations in contracts. Objective metrics should be used to track performance. Cultivate relationships based on trust and transparency, and address problems as early as possible.
Successful projects are beneficial to vendors as well, highlighting the benefits of successful collaboration to manage vendors. Great project managers demonstrate value to vendors as they accomplish successful projects.
Shashank Shastri is a PMP trainer with over 14 years of experience and co-founder of Oven Story. He is an inspiring product leader who is a master in product strategies and digital innovation. Shashank has guided many aspirants preparing for the PMP examination thereby assisting them to achieve their PMP certification. For leisure, he writes short stories and is currently working on a feature-film script, Migraine.
QUICK FACTS
Most projects successfully incorporate 3-7 vendors, striking a good balance between competition and oversight complexity. It's more important to identify the best vendors than to achieve a certain number.