Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How Toyota Stopped Overproduction Waste
Transcript
- Lucas: Let’s talk about the most expensive mistake a company can make: making too much stuff. Not too little, but too much. In a world obsessed with growth metrics and market share, overproduction is the silent killer of margins, tying up capital in unsold goods and burying your team in busy work that adds zero value. Luna: It’s funny because we always think of waste as physical scrap or broken machines, but idle inventory is basically just money sitting there doing nothing while paying for storage and insurance. Lucas: Exactly. And if you are listening to this from a non-manufacturing background, you might be thinking this is a factory floor problem. But whether you are running a software agency, a retail brand, or a consulting firm, you are likely guilty of producing deliverables before they are actually needed, creating bottlenecks downstream that everyone then has to scramble to fix. Luna: Right, like when marketing sends out a campaign asset that sales isn't ready to pitch yet, so now it's just sitting in a shared drive waiting for someone to remember to use it. Lucas: That is a perfect example. The principle comes from Toyota in the mid-twentieth century, specifically their development of the Kanban system. The word Kanban translates roughly to signboard or visual card, and the core idea was simple: stop pushing work through the system based on a forecast, and start pulling it only when the next stage actually has capacity to receive it. Luna: So instead of telling the factory to build ten thousand parts because the quarterly plan says they will sell them, you wait until the assembly line physically signals it needs more? Lucas: Precisely. They used a two-bin system where a downstream worker takes parts from Bin A. Once Bin A is empty, they send a Kanban card back upstream saying I need more. The upstream process only produces what was requested. It turns production into a response mechanism rather than a prediction game. Luna: That sounds incredibly rigid though. What happens if demand spikes suddenly and you don't have enough buffer? Doesn't that risk shutting down the whole line? Lucas: That is the classic objection, and it is fair. Toyota didn't ignore buffer; they managed it differently. They kept small, controlled amounts of safety stock, but they made sure every single unit in that stock had a clear destination. The danger of traditional forecasting is that you build inventory hoping for demand that never arrives, which is dead weight. The Kanban approach accepts that you might run low, but it forces you to address the root cause immediately rather than hiding behind a warehouse full of unused product. Luna: I see. So the visibility of the empty bin triggers a faster reaction than waiting for a monthly report to show a shortage. Lucas: Spot on. It creates a real-time feedback loop. If a machine breaks or a supplier delays, the signal stops propagating upstream almost instantly. You don't keep building parts that no one needs while the bottleneck sits unresolved. In many modern tech companies, this looks like limiting work in progress on a project management board. If the testing column is full, developers stop writing new code until bugs are cleared. Luna: Yeah, because otherwise you just pile up untested features that nobody knows how to deploy, and now your sprint review is just a demo of half-finished work. Lucas: And that is wasted effort. The beauty of the Kanban mindset is that it exposes problems. In a push system, problems are hidden by inventory. If you have three weeks of spare parts, you don't notice the machine is drifting out of alignment until it finally fails catastrophically. With Kanban, the lack of replenishment signals the issue early, forcing maintenance teams to fix it before production halts completely. Luna: It basically trades the illusion of security for the reality of flow. Having extra stock feels safe, but it masks inefficiency. Lucas: It does. And in today's environment, that distinction matters more than ever. We are looking at September twenty-eighth, twenty twenty-six, and global supply chains are still recovering from years of disruption. Companies that rely on massive forward-looking forecasts are getting burned when those forecasts prove wrong. Those using pull-based systems adapt faster because they are reacting to actual consumption data. Luna: But implementing that requires a huge cultural shift. You can't just tell people to stop working unless asked. That sounds like it would frustrate employees who want to feel productive. Lucas: It does require training, and it requires redefining what productivity means. In a push culture, being busy is rewarded. In a pull culture, being efficient is rewarded. You have to teach teams that standing still while waiting for a signal is not laziness; it is respecting the flow of the entire system. It takes leadership to enforce that discipline when the natural instinct is to keep moving. Luna: I guess that's why it's called an operator's manual. It's not just a tool; it's a behavior change. Lucas: Absolutely. And let's take a quick moment to talk about how we keep this conversation going. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these episodes without ads cluttering up your feed. Luna: It really helps us dig deeper into these operational details instead of rushing through headlines. Thanks for keeping the lights on. Lucas: Back to the floor. Let's look at a specific metric that tells you if your Kanban system is actually working. It is called Throughput Time, which measures how long it takes for a request to go from start to finish. In a healthy pull system, this number should drop over time because you are eliminating waits and handoffs. Luna: So if your throughput time is going up even though you are finishing more projects, something is wrong with the flow. Lucas: Correct. It usually means you have accumulated invisible inventory somewhere in the pipeline. Maybe designers are hoarding assets, or engineers are waiting on approvals. The signal gets stuck. Identifying where the cards stop moving allows you to unblock that specific node rather than trying to speed up the whole department. Luna: That makes sense. Speeding up a bottleneck doesn't help if the rest of the line is waiting on something else entirely. Lucas: Right. You end up creating more waste by adding pressure to a constrained resource. The Kanban approach focuses on balancing the load. If one station is consistently slower, you don't push more work to it; you either improve its process or adjust the upstream pull rate to match its capacity. Luna: It’s basically matching the heartbeat of the slowest part of the system rather than trying to outrun it. Lucas: Exactly. And this applies to knowledge work too. If your QA team can only test five stories a day, your dev team should limit their commits to five. Anything beyond that just piles up in the staging environment, creating context-switching chaos for the testers and delaying feedback for the writers. Luna: I've seen that happen. Developers ship everything at Friday afternoon because they hit their daily goal, leaving QA with a mountain of work on a short deadline. Lucas: That is pure push behavior. The result is usually rushed testing, missed bugs, and hotfixes on Monday morning. By capping the work in progress, you force a smoother, steadier delivery pace that everyone can handle sustainably. Luna: Sustainability over sprints. That seems like a hard sell to executives who love seeing big weekly numbers. Lucas: It can be, but the numbers eventually speak for themselves. Lower defect rates, higher employee satisfaction because people aren't drowning in backlog, and better cash flow because you aren't investing in unfinished work. It is a different kind of performance metric, but it is often more profitable in the long run. Luna: So the key takeaway is to look for the piles. Where is the work piling up? That's where your Kanban signal should be pointing. Lucas: Yes. Find the bottleneck, respect its pace, and eliminate the waste generated by trying to beat it. It is a disciplined way to run a business that values quality and flow over frantic activity. Luna: It’s counterintuitive, but it feels like the only way to stay sane when everything is changing so fast. Lucas: It is. And as we head into the final quarter of twenty twenty-six, that stability might be the most valuable asset any operator can build. Luna: Where do you see the biggest opportunity to apply a pull system in your own workflow this week? Lucas: Probably my inbox. I treat it like a Kanban board, but I haven't limited my WIP lately, and the pile is growing. Luna: Start small. Clear three items, then stop until the next stage is ready. Lucas: I will try that. Thanks for keeping me honest. Luna: Anytime. See you next time.