Managing Vendors on a Project: What Good Looks Like, What Bad Looks Like
Most project failures involving a vendor are not failures of the vendor. They are failures of vendor management — the day-to-day work of setting expectations, holding the line on scope, and catching small slips before they compound. After two years of disrupted supply and remote handoffs, that work has only gotten harder: the supplier you never met in person is now late, the contact who knew your project has moved on, and the kickoff that should have happened in a room happened on a call where everyone nodded and no one wrote anything down. The contract matters, but the contract does not run itself. The contrast below is what separates a vendor relationship that delivers from one that quietly bleeds your budget.
What good looks like
Good vendor management is unglamorous and consistent. It treats the supplier as part of the delivery team without pretending the commercial relationship does not exist.
A single named owner on your side holds the relationship — not three people who each assume someone else is watching it.
Scope, acceptance criteria, and what "done" means are written down and agreed before work starts, not negotiated after the invoice arrives.
Status is reviewed on a fixed cadence against milestones, and the vendor knows a slip must be reported early, in writing.
Issues are raised respectfully and promptly, with a paper trail, so a pattern is visible long before it becomes a crisis.
Payment is tied to verified deliverables, and someone actually checks the work before it is approved.
There is a known escalation path both sides have agreed to, used calmly rather than as a threat.
What bad looks like
Bad vendor management usually feels fine right up until it doesn't. The warning signs are quiet, which is exactly why they are dangerous.
The relationship runs on goodwill and verbal updates; nothing is documented, so accountability evaporates when people change.
Scope is fuzzy, change requests are informal, and every new ask is absorbed without anyone tracking the cost.
Status meetings become status theatre — green dashboards over a project that everyone privately knows is slipping.
Problems are smoothed over to keep the peace, then surface all at once near a deadline when options are gone.
Invoices are approved on trust because no one has time to verify the deliverable.
The first real escalation is also the first hard conversation, so it lands as an accusation instead of a process.
How to move from one to the other
Name the owner. Put one person's name against the vendor relationship and make it part of their job, not a favour they do between other tasks.
Write the definition of done. Agree acceptance criteria in writing before work starts. This single habit prevents most disputes that end up in dueling emails.
Make slips reportable, not punishable. If vendors fear blame, they hide problems. Reward early honesty so you learn about trouble while you can still act on it.
If a vendor relationship on one of your projects has drifted toward the second column, XNM's program & project delivery advisory can help you reset the cadence, the documentation, and the working relationship before the next milestone.