Latest / The Buyer's Side with Fexingo: Procurement, Sourcing, and B2B Purchasing Decisions / How One Buyer Used a Supplier Scorecard to Cut Quality Costs by 30 Percent
Transcript
- Lucas: Last year I sat in on a quarterly review at a mid-sized automotive parts manufacturer. The procurement director pulled up a slide that showed their quality-related costs—scrap, rework, warranty claims—had dropped 30 percent over 18 months. I asked what changed, and he said, 'We finally started scoring our suppliers properly.' Luna: That's a big number. So they just started measuring and the costs fell? Lucas: Not exactly. They'd been measuring for years. The problem was they measured everything—twenty-six different metrics—and none of them were weighted. So a supplier who delivered on time but had high defect rates could still get an 'A' because on-time delivery was given the same importance as defect rate. Luna: So the scorecard itself was misleading. It didn't actually tell the buying team which suppliers were truly performing. Lucas: Right. And that's a common trap. The team I'm talking about redesigned their scorecard around three core metrics: defect rate, on-time delivery, and corrective action response time. They assigned weights: 50 percent to defect rate, 30 percent to on-time delivery, and 20 percent to corrective action response time. Luna: Why those three? And why 50 percent on defects? Lucas: Because their internal data showed that 70 percent of their quality costs were driven by defects. On-time delivery mattered, but a late part you could expedite. A defective part could shut down a production line, trigger a recall, or lead to warranty claims. So they made defect rate the dominant factor. Luna: That makes sense—align the scorecard weight with the actual cost impact. Did they share the new scorecard with suppliers? Lucas: They did. And that transparency was key. Every supplier got a quarterly scorecard that showed exactly where they stood on each metric, plus a composite score. Below a 70 out of 100, they went on a 90-day probation. If they didn't improve within two consecutive probation periods, they were disqualified from new business. Luna: So suppliers knew the rules and the consequences. That must have changed behavior pretty quickly. Lucas: Yeah. In the first quarter, about 15 percent of their supplier base fell into probation. Most of those improved within the 90 days. A handful didn't, and they were phased out. But here's the interesting part—the overall defect rate dropped not just because underperformers were cut, but because even the good suppliers paid closer attention to the weighted metrics. Luna: You're saying the scorecard itself became a communication tool. It told suppliers, 'We care most about defects,' so they invested more in quality control. Lucas: Exactly. And that's the real value of a well-designed scorecard. It's not just an evaluation tool—it's a strategic alignment mechanism. When suppliers understand what's weighted heavily, they allocate their resources accordingly. Some even started sending weekly defect reports proactively, just to stay ahead of the quarterly review. Luna: That's a great example of how procurement can drive change without demanding price cuts. You're improving quality, which reduces total cost of ownership. Lucas: And that's exactly the kind of high-leverage procurement work that often gets overlooked. If today's conversation gave you some ideas for your own supplier performance management, you know, these episodes stay ad-free because of listener support. It's a small way to keep the conversation going—buy me a coffee dot com slash fexingo. Luna: Yeah, we hear from listeners who say they've used specific frameworks from this show with their own teams. That feedback is what keeps us going. Lucas: Alright, back to the scorecard. The second challenge this team faced was getting internal buy-in. The plant managers were used to informal relationships with suppliers—they'd call a rep they liked and get a rush order. The scorecard threatened those relationships. Luna: How did they handle that pushback? Lucas: They started by sharing the data. They showed each plant manager the actual cost of defects from their top five suppliers over the previous year. In one case, a single supplier had caused $400,000 in rework costs at one plant. The manager had no idea because the costs were buried in the plant-level P&L. Luna: So visibility was the first step. Once they saw the numbers, they couldn't argue with the need for change. Lucas: Right. Then they involved the plant managers in the scorecard design. They asked, 'What metrics matter most to your daily operations?' The managers pushed for including corrective action response time because a slow response from a supplier meant their own team had to hold inventory longer. Luna: So the final scorecard wasn't just procurement's tool—it was a cross-functional tool. That makes enforcement easier. Lucas: Exactly. And once the scorecard was live, they held quarterly joint reviews with procurement, quality, and plant operations all in the room. When a supplier scored low, it wasn't just procurement delivering bad news—it was the plant manager saying, 'This directly affects my line.' Luna: That's powerful. Now, you mentioned data cleanliness earlier. How big of a hurdle was that? Lucas: It was the biggest hurdle, honestly. The defect data lived in the quality management system. The on-time delivery data lived in the ERP. The corrective action data lived in spreadsheets and emails. They had to build a simple integration to pull all three into a single dashboard. Luna: So they had to clean up their data before they could trust the scorecard. That must have taken time. Lucas: About three months of dedicated work. They assigned one data analyst to reconcile definitions—for example, what counts as 'on time'? Is it the promised date, the requested date, or a one-day window? They standardized all that before they even calculated the first score. Luna: And I imagine the first few scorecards had some surprises—suppliers they thought were great but actually weren't. Lucas: That happened. One supplier had a long-standing relationship with the plant manager and was considered a 'preferred supplier.' But the data showed a defect rate of 8 percent, which was twice the average. That supplier went straight to probation. The relationship became tense, but the data was hard to argue with. Luna: What happened to that supplier in the end? Lucas: They improved. Within two quarters, their defect rate dropped to 3 percent. They invested in better inspection equipment and retrained their line workers. The scorecard gave them a clear target and a reason to act. Luna: So the scorecard actually strengthened the relationship in the long run because it removed ambiguity. Lucas: Exactly. And that's the final piece I want to highlight—the scorecard isn't a weapon. It's a shared language. When both sides agree on the metrics and the weights, the conversation shifts from 'You're not performing' to 'Let's look at the data and figure out where to improve together.' Luna: That approach probably sets the stage for more strategic partnerships, too. Once you have a reliable scorecard, you can start talking about joint cost-reduction projects or innovation. Lucas: Right. And that's the trajectory this company is on now. They're planning to add a sustainability metric to the scorecard next year, weighted at 10 percent. They'll adjust the other weights accordingly. The framework is flexible as long as the data is clean and the weights reflect the true cost drivers. Luna: So one takeaway: start with the cost data, pick three to five weighted metrics, and involve the internal stakeholders early. That seems like a repeatable formula. Lucas: Yeah. It's not flashy, but it works. And as we've seen, it can deliver a 30 percent reduction in quality costs within 18 months. That's real money that drops straight to the bottom line. Luna: Alright, thanks Lucas. That was a practical one. I'm sure some listeners are already thinking about which metrics they'd weight differently. Lucas: I hope so. That's the point. Thanks, Luna.