Partner with internal teams, such as Procurement, Finance, IT, Legal, and business operations.
Partner with your procurement team to define an evaluation process that:
The evaluation process may vary based on organization and procurement policies.
Define the minimum requirements a vendor needs to meet to submit a proposal.
Specify these requirements clearly and concisely.
The evaluation process consists of a series of assessments, each representing a decision gate to narrow the options to the most viable vendor(s).
A visual metaphor to communicate the evaluation process is the Cone of Uncertainty.
Your minimum requirements aren't specified sufficiently if more than ten vendors respond to your RFP.
Create the proper framework upfront and use it consistently throughout the evaluation process:
Every interaction with a vendor is an opportunity to evaluate and quantify fit:
Select the right people to score, contribute, and evaluate the vendors and their solutions.
Confirm they have a good knowledge of the solution space.
Complete the required due diligence at each evaluation stage.
Engage in research and peer networking to understand your operating ecosystem.
Score to the extent possible.
Emphasize quantitative scoring in your evaluation processes. Scoring as much as possible results in better selection decisions and minimizes biases influencing decision-making.
Initiate preliminary negotiations (RFP approach) soon after your recommendation to leadership is accepted.
Team members bring their unique experiences, relationships, and perspectives to the project. Diversity in thinking and perspective is good. However, team members must surface material biases to leadership.
Examples of biases include:
Leadership should assess and decide when bias may harm the vendor solution decision process and make appropriate team member changes.
Previous employment or work history with a particular vendor is an example of a bias that may be beneficial. Deeper insight into a vendor may uncover critical pros and cons that the evaluation team should know. Consider assigning the team member with the vendor history as a contributor, not a scorer.