A supplier is selected after a thorough process. The specification is met. The contract is signed.

And yet, six or twelve months later, the original problem still exists.

The operation hasn't improved. Risk hasn't meaningfully reduced. People are quietly working around the solution rather than with it.

At that point, the conversation usually turns to delivery issues, scope creep, or budget pressure. But in my experience, most supplier failures don't start with poor execution.

They start much earlier, at selection, when organisations mistake compliance for capability.

The Comfort of Checklists

Checklists exist for good reasons.

They create consistency. They provide defensibility. They help organisations demonstrate that decisions were made "properly", especially in regulated or risk‑sensitive environments.

The problem is that checklists are very good at measuring what's easy to specify, and very poor at testing what actually matters.

A supplier can meet every line of a specification and still be the wrong fit for the real‑world operating environment. When that happens, the organisation hasn't made a reckless decision. It's made a defensible one.

Unfortunately, defensible decisions are not the same thing as good decisions.

This is how teams end up with suppliers who are technically compliant but operationally weak, and why so many projects stall after the initial optimism fades.

Features Don't Fix Problems. Outcomes Do.

One of the most common traps in supplier selection is focusing on what a supplier offers rather than what will change if they succeed.

Features are tangible. Outcomes are not.

Outcomes require uncomfortable clarity about:

• What isn't working today
• Where inefficiency or risk actually shows up
• What success would look like in operational terms

When organisations reward suppliers for features, suppliers respond with features. When they're challenged on outcomes, something different happens: vague proposals collapse very quickly.

This is the heart of solution‑based thinking, understanding the problem deeply enough that the solution becomes obvious, not performative .

The Discovery Test Most Suppliers Fail

There's a simple way to tell whether a supplier is likely to help or hinder you.

Before they present anything, ask yourself one question:

Are they genuinely trying to understand how we actually operate?

A credible partner will ask about constraints, failure points, trade‑offs, and workarounds. They'll want to know what's failed before, and why. They'll probe how decisions are made under pressure, not just how things are meant to work on paper.

A transactional vendor will skip that discomfort and move straight to slides, features, and generic case studies.

If discovery is shallow, delivery will be too. No contract language can compensate for a poor understanding of reality.

Why SLAs Don't Equal Success

Service Level Agreements matter. They set expectations and define minimum standards.

What they don't do is guarantee outcomes.

An SLA tells you what happens after something goes wrong. It doesn't tell you whether the supplier is capable of preventing the issue in the first place.

The most effective suppliers don't hide behind SLAs. They invest in governance, adaptation, and shared accountability. They treat the contract as a baseline, not a ceiling.

That's where the difference between a vendor and a partner becomes visible, and where many supplier relationships quietly fail.

The Cheapest Option Rarely Is

Headline price is easy to compare. It's also misleading.

The real cost of a supplier tends to appear later, through:

• Implementation friction
• Internal firefighting
• Workarounds and bolt‑ons
• Management time lost to poor fit

This is the total cost of ownership that never shows up in a tender spreadsheet.

Organisations that make consistently good supplier decisions stop asking, "What does this cost?" and start asking, "What will this cost us to live with?"

That single shift eliminates more bad decisions than most process improvements ever will.

Track Record Beats Reputation

Large logos and polished case studies are reassuring, but they're also easy to curate.

What matters more is behaviour:

• How does the supplier respond when the brief is wrong?
• What happens when delivery conflicts with contract wording?
• Can they show evidence of adapting to protect outcomes?

Problem‑solving history tells you far more than brand recognition ever will.

This Isn't Really About Procurement

At its core, this isn't a procurement issue. It's a leadership one.

Supplier decisions shape resilience, confidence, and risk exposure. They influence whether organisations feel in control, or permanently reactive.

Checklists, SLAs, and contracts all have their place. But none of them replace judgement, clarity, and the willingness to challenge surface‑level compliance.

The organisations that avoid expensive supplier failures aren't luckier. They're simply more disciplined about asking why before they ask how much.

And that discipline, more than any framework, is what turns buying into strategy.

Better decisions don't come from longer checklists. They come from better questions.