Your Vendor Is Not Your Partner. They're Your Supplier With a Contract.

The account manager was genuinely good company. He remembered my daughter's name, he sent something at Christmas, and for about fourteen months we called his firm our strategic partner in every steering pack. Then the delivery went sideways, and I learned that "partner" had been doing a lot of load-bearing work in my head and none at all in the contract.

I'm not telling you to be cold with your suppliers. I'm telling you that warmth is not a control.

Watch what the word does to a meeting. Partners share problems. Partners absorb a bit of pain for each other. Partners don't send each other formal letters, because that would be, well, a bit much between partners.

Which means the moment you accept the framing, you've agreed to a set of behaviours that all run in one direction. You're the one who softens the escalation. You're the one who doesn't put the slip in writing because the relationship is good and it'll probably recover next sprint. You're the one absorbing their delay into your plan, and calling it pragmatism.

Meanwhile their account manager has a number he owes his own management every quarter, and a delivery lead he doesn't control, and a contract in a drawer that says exactly what they owe you and by when. That contract is the only thing in this arrangement that behaves consistently under pressure.

So use the relationship. Genuinely. A supplier who likes working with you will find you a better engineer, take your call at 21:00, and tell you things they aren't obliged to tell you. That's worth a lot and you should invest in it. Just don't let it stand in for the mechanism. Be warm with the people and precise with the agreement, and never let anyone talk you into thinking those two things are in tension.

The test is simple. If you'd feel awkward reading a clause out loud on the weekly call, you've let the relationship become a substitute for the contract rather than an addition to it.

Here's the bit that gets people. When the supplier is late, you are late. Nobody at your board is going to be satisfied by an explanation that correctly allocates the blame elsewhere. Correct and useless is still useless.

Which means every third-party dependency belongs on your plan, in your risk register, with someone on your side owning the mitigation. Not the vendor's name. Yours. What do we do if this slips by four weeks, who decides, and by when do we need to know?

A mid-size manufacturer, a warehouse management rollout across nine sites, an integrator doing the software configuration and a separate supplier providing the handheld hardware. We had a weekly call with the integrator. Their status was green for eleven consecutive weeks. Friendly calls, good notes, nice people.

In week twelve it went amber, and in week thirteen it went red with a nine week impact, which was somehow a surprise to everyone on our side and to nobody on theirs.

What I'd been doing was accepting status. What I should have been doing was accepting evidence. Not "is the interface configuration on track", which invites the answer that keeps the call pleasant, but "can you show me the interface running against our test data, this week". Green is an opinion. A working thing in a test environment is a fact.

The second failure was worse and entirely mine. Nine weeks of integrator delay hit a hardware order with a twelve week lead time, and we hadn't mapped that link. The handheld supplier was performing perfectly. It didn't matter. Their delivery slot got rebooked into a period we couldn't move, because nobody on our side was tracking what would happen to the second supplier if the first one slipped.

When you've got more than one third party, the dependency between them is yours to manage. They will not do it for you. They may not even know the other one exists.

Most technical leaders escalate far too late, and then far too hard, because they've spent eight weeks being reasonable and have finally run out of patience. That sequence costs you the relationship and rarely recovers the date.

Do it the other way round. Escalate early, when the ask is still small, and make the first one almost gentle. A short note after the call: "As discussed, the interface build is now tracking two weeks behind the plan. To protect the September cutover we need a firm date by Friday the 12th, or we'll need to look at re-sequencing site three. Can you confirm?"

Nobody's career is threatened by that note. It costs the account manager nothing to answer it. But it exists, it has a date in it, and it starts a paper trail that means your third note, the serious one, arrives as the expected next step rather than as an ambush.

Two things I'd insist on. Put the commercial consequence in writing before you say it out loud in anger, and say it plainly rather than by implication. And escalate on your own side at the same time. The vendor's management should never be the first people to learn there's a problem. Your sponsor should be, and they should hear it from you in the same week you learned it.

The thing to protect, when you're annoyed, is the account manager's ability to help you internally. He is going to walk into a room in his own company and argue for resources on your behalf. Give him something he can carry in: a specific request, a date, a reason his own leadership will understand. What he can't carry in is a general expression of your disappointment.

And practise one sentence until it's easy to say: "I want to be straight with you, this is now at the point where I have to raise it formally, and I'd rather you heard that from me first." I've said that a dozen times. It has never once damaged a relationship. Silence and a sudden legal letter absolutely have.

Take every third party your delivery depends on and, for each one, write down the name of the person on your side who owns the mitigation if they slip by a month. Not the person who manages the relationship. The person who owns what you do about it.

Where that name is blank, or where it's you for more than two suppliers, you've found the thing to fix this week.

Then change one question on the standing agenda. Replace "are we on track" with "what can you show us this week", and hold it there for a month. You'll know by the third call which of your suppliers has been reporting status and which has been reporting reality.