Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How Toyota Turned Scrap Into A Competitive Moat
Transcript
- Lucas: Let's talk about the one cost line item that managers love to ignore because it feels too small to matter: scrap. Not the big stuff like a broken machine or a supply chain rupture, but the tiny, daily accumulation of parts that fail inspection before they ever leave the factory. Luna: Right, because if you're looking at a ten percent margin, losing two percent on scrap feels negligible until you realize it's actually eating half your net profit. Lucas: Exactly. And this brings us to a specific lesson from Toyota, one that goes deeper than the usual 'lean manufacturing' platitudes we hear every day. They didn't just try to reduce scrap; they monetized it by making the cost of failure so transparent that it changed how engineers designed parts in the first place. Luna: So instead of hiding the loss in a general overhead bucket, they put a direct price tag on every single bad unit? Lucas: Precisely. In the late nineteen nineties, when I was tracking their operations closely, Toyota introduced a practice where the cost of scrap wasn't just absorbed by the plant budget. It was traced back to the specific supplier and the specific engineering decision that caused it. This forced a shift from blame to root cause analysis. Luna: That sounds incredibly friction-heavy for a supplier relationship though. Did they face pushback? Lucas: They did, initially. But the twist is that Toyota shared the savings. If a supplier could prove they reduced scrap rates below a certain threshold, Toyota would adjust the long-term contract terms to reflect lower material costs, effectively sharing the efficiency gain. It turned a punitive measure into a partnership incentive. Luna: I see. So the real leverage wasn't punishing the error, it was aligning the financial reward for fixing it. Lucas: Spot on. Most companies treat quality control as a police force, catching bad products after they're made. Toyota treated it as an insurance policy against future design flaws. The concrete detail here is that they tracked the 'cost of poor quality' as a percentage of revenue, keeping it under two percent for decades while competitors hovered around four to five percent. Luna: Two percent sounds small, but in volume manufacturing, that's a massive absolute number. Lucas: It is. For a company moving millions of units annually, that two percent gap represents hundreds of millions in pure operating income. The question for us listeners is whether your business has a similar hidden leak that you're ignoring because it's buried in administrative costs. Luna: Most service businesses don't have physical scrap, but they definitely have rework. How does that translate? Lucas: Rework is the service sector's equivalent of scrap. Think about a software bug that requires three different teams to fix, or a consulting report that gets sent back for revisions because it missed the client's actual brief. That time is wasted material, except it's human capital. Luna: And human capital is way more expensive than metal shavings. Lucas: Significantly. The lesson from Toyota isn't about factories; it's about visibility. You can't manage what you don't measure. If you aren't tracking the cost of your own errors in real time, you're flying blind. Luna: So the first step is just admitting that your internal mistakes are costing you money directly, not just indirectly. Lucas: Yes. And then attaching a dollar value to those mistakes. When a project manager sees that a delay cost the team fifteen thousand dollars in idle wages, they start prioritizing differently. It changes behavior instantly. Luna: That feels like a hard pill to swallow for leadership who prefer optimistic forecasts. Lucas: Optimism is fine for sales pitches, but terrible for operational planning. Toyota's approach was brutally honest. They celebrated the discovery of a defect, not the concealment of it. That cultural shift is harder than any technical process change. Luna: Because if you punish the messenger, nobody reports the problem until it's too late. Lucas: Exactly. You want early warnings, not late apologies. The best operations teams are the ones that make it safe to say, 'I broke this,' quickly enough to fix it before it compounds. Luna: It reminds me of how airlines handle safety reports. Pilots can file anonymous incident reports without fear of losing their licenses. Lucas: Right, same principle. Transparency builds trust, and trust allows for faster correction. In business, opacity creates risk. Every hidden error is a bomb waiting to go off during peak season. Luna: So for our listeners running smaller teams, how do you start tracking this without getting bogged down in bureaucracy? Lucas: Start with one metric. Pick the most frequent type of error your team makes—whether it's coding bugs, shipping mistakes, or billing errors—and track it weekly. Just one number. See if it goes up or down over a month. Luna: Keep it simple. Don't try to measure everything at once. Lucas: Correct. Complexity kills adoption. If you ask your team to fill out twenty forms to report an error, they won't do it. If you ask them to send a quick Slack message or update a dashboard cell, they will. The tool must be invisible; the insight must be clear. Luna: And then use that data to tweak the process, not to fire people. Lucas: Absolutely. If you use error data to punish individuals, you'll get false data. If you use it to improve the system, you'll get accurate data and better profits. It's a choice between short-term ego and long-term efficiency. Luna: I think a lot of leaders struggle with that distinction because they feel personally attacked by bad numbers. Lucas: They do. But remember, the number isn't attacking you. It's informing you. Your job isn't to be perfect; your job is to build a machine that corrects itself. That's the Toyota way. Luna: Building a self-correcting machine rather than relying on heroic individual effort. Lucas: Yes. Heroes burn out. Systems scale. If your business collapses when your star employee takes a vacation, your system is broken. If it runs smoothly, you've solved the scrap problem at the structural level. Luna: That's a powerful reframe. Profit isn't just about selling more; it's about leaking less. Lucas: Precisely. The biggest margin expanders are often the boring ones. The quiet fixes that stop the bleeding. Once you see that, you can't unsee it. Luna: And it starts with just asking, 'what are we losing today?' Lucas: That's the only question that matters. Everything else is just noise. Luna: If these conversations have moved your work forward in some small way, consider supporting the show directly. Lucas: Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It keeps the research ad-free and helps us keep digging into these operational details. Luna: We appreciate every bit of support that lets us stay independent and focused on the facts. Lucas: Back to the topic though, because there's one last nuance about Toyota's approach that really sticks with me. Luna: Which is? Lucas: The speed of the feedback loop. They didn't wait for end of month reports to analyze scrap. They wanted to know within hours. That immediacy allowed them to stop the line, fix the issue, and restart, minimizing the total damage. Luna: Speed as a quality tool. I hadn't thought about it that way before. Lucas: It is. Delay is the enemy of correction. The faster you learn from a mistake, the cheaper the lesson. Luna: So the goal isn't perfection, it's rapid iteration. Lucas: Exactly. Perfection is a myth. Speed is a strategy. Build the fastest learning cycle you can, and let the profits follow.