I have run supplier development programmes in three companies. Two were failures. One transformed my supplier base and saved millions. The difference was not the budget, the tools, or the suppliers. The difference was the approach. And the approach that worked was the opposite of what most companies do.

Why most supplier development fails

Most supplier development programmes fail for a simple reason: they are designed to serve the buyer, not the supplier. The buyer identifies a gap in supplier performance, develops an improvement plan, sends it to the supplier, and monitors compliance. The supplier receives a list of demands, responds with the minimum effort required to maintain the contract, and resents the intrusion. Six months later, nothing has changed. The buyer blames the supplier's lack of commitment. The supplier blames the buyer's unrealistic expectations. The programme is quietly abandoned.

I ran this exact programme at my first company. We hired a consultant, developed a supplier excellence framework, launched it with great fanfare, and achieved nothing. The suppliers who were already good stayed good. The suppliers who were struggling stayed struggling. The consultant was paid handsomely. The only tangible output was a binder of frameworks that sat on a shelf.

You cannot develop a supplier by telling them what to fix. You can only develop a supplier by helping them see what to fix and giving them the tools to do it.

The programme that worked

At WITTE Automotive, I inherited a supply base that was causing chronic problems. Three suppliers accounted for 70 percent of our supplier-related quality issues. The traditional approach would have been to issue corrective actions, escalate threats, and eventually replace them. Instead, I tried something different.

I called each of the three suppliers and asked one question: "What do you need from us to improve?"

Not what we needed from them. What they needed from us. The question caught them off guard. Suppliers are accustomed to receiving demands, not being asked for input. But once they understood the question was genuine, the answers were illuminating.

Supplier A said: "Your engineering changes arrive with two weeks' notice and our tooling lead time is six weeks. We either delay your shipment or run with old tooling and rework. We cannot win." Solution: we gave them eight weeks of visibility on engineering changes and locked the change control process. Their quality improved immediately.

Supplier B said: "Your forecast changes so frequently that we run emergency batches every week. Emergency batches mean no process control, no capability studies, no SPC. We know our quality suffers, but we cannot push back on your schedule." Solution: we stabilised the forecast and agreed on a frozen horizon. Within three months, their process capability went from Cpk 0.9 to Cpk 1.4.

Supplier C said: "We have never seen how our part functions in your assembly. We design to a drawing, but we do not understand the function. When we have a process deviation, we do not know if it matters." Solution: we invited their engineering team to our plant for two days. They watched the assembly, talked to our operators, and saw the downstream impact of their variability. They went back and redesigned their inspection plan based on functional understanding, not dimensional compliance.

The six-month results

After six months:

Supplier A's PPM dropped from 850 to 120. Their on-time delivery went from 89 percent to 97 percent. They became one of our most reliable suppliers.

Supplier B's scrap rate dropped by 60 percent. They invested in new measurement equipment — their own decision, their own money — because they finally had the schedule stability to justify the investment.

Supplier C stopped arguing about specification interpretation. Their nonconformance rate dropped by 75 percent. And they started sending their engineers to our plant annually — at their expense — because they saw the value of understanding the application.

Total investment from our side: zero capital, two days of engineering time per supplier, and a commitment to share information we had been hoarding. Total return: roughly €1.2 million in reduced sorting, rework, line downtime, and expedited freight.

The principles

The programme that worked was built on four principles that the failed programmes lacked:

Listen before you act. The supplier knows things you do not about their process. They also know things you do not about how your behaviour contributes to their problems. Ask. Listen. Then act.

Fix your own house first. In two of three cases, the root cause of the supplier quality problem was our own behaviour — late engineering changes, unstable forecasts, missing functional context. Before demanding supplier improvement, audit your own contribution to their difficulty.

Share information generously. Forecasts, engineering roadmaps, field failure data, application context. The more the supplier understands about your business, the better they can serve it. Information asymmetry is the enemy of supplier development.

Measure results, not activities. Do not track how many meetings you had or how many reports you generated. Track PPM, on-time delivery, cost of poor quality, escape rate. If the numbers are not improving, the programme is not working, regardless of how busy everyone is.

Supplier development is not a programme you run at suppliers. It is a partnership you build with them. The companies that understand this difference have supply bases that improve year over year. The companies that do not are forever replacing suppliers and wondering why the new ones are no better than the old ones.