A thought stayed with me recently: we rarely abandon our values deliberately. We simply lose sight of them. Haste is especially good at making that happen. A deadline is approaching, the team is stretched, and a provider arrives with a polished roadmap for moving forward. Their perspective may be thoughtful and their offering may be excellent. But under pressure, their definition of what matters can quietly become yours. I help teams pause long enough to make their own values visible, collectively, before asking providers how they would deliver against them. It does not slow the decision. It makes the decision belong to the team again.
I have seen large decisions and tactics from every side of the table. I have represented providers at major consulting firms, worked as an account partner at a software company, and advised buyers building new capabilities. Good providers are supposed to bring a point of view. They study the market, recognize patterns, and invest in the problems they believe customers will pay them to solve. A confident roadmap is not evidence of bad intent. It is evidence that the provider has done its job. The buyer still has to do theirs.
That work begins before the first presentation. What does the organization value? What does the team value? What matters to senior leaders, IT, legal, regional teams, and the people who will live with the decision after the contract is signed? The answers will not always agree. That is the point.
One group may value speed while another worries about control. A global leader may want consistency while a regional team needs flexibility. Legal may see exposure where the business sees opportunity. None of them is wrong. The work is to make those differences visible and decide, together, what the selection must protect.
That is the part of the process I enjoy most. I help teams turn many valid perspectives into one shared definition of what matters. Only then do the familiar mechanics become useful. A weighted scorecard can hold providers accountable to criteria the team chose. It can also reveal when the numbers and the team's judgment disagree. That disagreement is not a failure of the process. It is where the most important conversation begins.
A spreadsheet cannot tell you which delivery team you trust to show up when something breaks. Subjective judgment is not noise to eliminate. It is part of the decision, and it should be made visible rather than hidden. The discipline is in getting the order right. Establish the values. Define the capability. Invite the perspectives. Evaluate the fit. Then let the providers compete to support your roadmap, instead of allowing the best presentation to write it for you.
Takeaway
Haste rarely presents itself as compromise. It feels like momentum. Take the meeting. Use the provider's framework. Start the demonstration. Borrow the evaluation criteria. A provider recently offered to write a client's capital request. Helpful on the surface, but it would have let the proposed solution begin writing its own business case. Each shortcut feels reasonable. Together, they can leave a team comparing solutions before agreeing on what it is trying to protect. Values, in this context, are not words on a wall. They are the choices a team wants its decision to honor when attractive options pull in different directions. Speed or control? Consistency or local flexibility? Immediate relief or a capability that will last? Provider perspectives are useful. Peer experience is useful. Understanding why a company invests in certain parts of its roadmap is useful. The problem begins when those inputs stop informing your values and start replacing them. A good competitive process makes the team's values explicit, reconciles the differences among stakeholders, and turns what matters into criteria providers can respond to. The result is more than a defensible selection. It is a decision that still feels right after the sales cycle ends.