Latest / The CEO Diary with Fexingo: Leadership Lessons, Executive Decisions, and Corner Office Stories / How Toyota Mastered The Art Of Wasting Time
Transcript
- Lucas: If you walk onto the floor of a modern Toyota assembly plant in Kentucky today, the most striking thing isn't the speed of the robots or the precision of the welding arms. It's the silence. Or rather, the controlled quiet. There is no frantic energy, no shouting to keep up with a relentless pace. Instead, there is a palpable sense of pause. That pause is not an accident, and it is certainly not inefficiency. It is the core engine of their entire business model. Luna: It feels almost rebellious in today's context where hustle culture equates motion with value. How do they justify stopping the line if a single bolt doesn't feel right? Lucas: They call it the Andon Cord. Any worker, from the newest hire to the veteran technician, has the authority and the obligation to pull a cord that halts the entire assembly line immediately. It sounds terrifying to a traditional manager who sees every second of downtime as lost revenue. But for Toyota, pulling that cord is actually a signal of high performance. It means the worker spotted a defect before it became a cascade of failures downstream. They aren't wasting time; they are investing in prevention. Luna: So the metric isn't how fast you move, but how quickly you can identify when you shouldn't be moving. Lucas: Exactly. Most companies optimize for throughput. Toyota optimizes for flow. Throughput is about volume, pushing units out the door. Flow is about the smooth, uninterrupted journey of a single unit through the process. When you prioritize throughput, you create bottlenecks. You build inventory piles. You hide problems under mountains of unfinished goods. When you prioritize flow, you expose those problems immediately because the system grinds to a halt the moment a glitch appears. It forces resolution in real-time rather than deferring it. Luna: That requires a level of trust in frontline workers that I rarely see in tech or finance sectors. Do employees actually trust that pulling the cord won't get them fired? Lucas: That was the hardest part of the cultural transformation. Historically, supervisors would punish anyone who stopped the line. Toyota flipped that script entirely. If you stop the line and fix the problem, you are praised. If you ignore a defect and try to keep moving, you are reprimanded. It takes years to embed that mindset. It’s not just a rulebook change; it’s a rewiring of human instinct. People are naturally afraid of looking incompetent or slowing down their peers. Overcoming that social friction is where most implementations fail. Luna: It’s interesting because in my own experience, the fear of being seen as slow usually overrides the desire to be perfect. We’d rather ship a buggy product than admit we’re stuck. Lucas: Right. And that’s the trap. We confuse busyness with progress. In a knowledge work environment, like our podcasting or writing tasks, we don’t have physical assembly lines, but we have digital ones. A draft document, a code repository, a marketing campaign. When something feels wrong, do we hit pause? Or do we just push it out and patch it later? Toyota teaches us that the cost of fixing a mistake after it’s shipped is exponentially higher than the cost of pausing while it’s still in development. Luna: But how do you measure the ROI of that pause? If I take two days to refine a report instead of rushing it out in four hours, how does my boss see the value in that delay? Lucas: You have to make the invisible visible. At Toyota, they track 'cycle time' versus 'lead time.' Cycle time is the actual work done on the product. Lead time is the total time from start to finish. In a chaotic environment, lead time is huge because of waiting, rework, and errors. By stopping to fix things properly, cycle time might stay the same, but lead time shrinks because there’s no rework loop. The metric that matters is not speed of initiation, but speed of completion without error. It’s a subtle distinction, but it changes everything about how you schedule your week. Luna: So instead of saying 'I’m working hard,' you say 'I’m reducing waste.' That’s a powerful reframing for performance reviews. Lucas: Precisely. And it applies to meetings too. The biggest form of muda, or waste, in corporate America is probably unnecessary meetings. Toyota minimizes meetings by encouraging brief, stand-up huddles focused solely on blockers. No agenda slides, no presentations. Just: what did I do yesterday, what am I doing today, and what is blocking me? If someone is blocked, the line stops metaphorically, and resources are reallocated immediately. It’s agile long before agile was a buzzword. Luna: I love that. Most of my calendar is full of hour-long blocks where nothing gets resolved until the end. This sounds much more surgical. Lucas: It is surgical. But it requires discipline. You can’t just stop the line forever. Once the issue is identified, you have to solve it permanently. Toyota uses a method called 'Five Whys'. You ask why the problem happened, then why that cause happened, again and again, until you hit the root cause. Often, it’s not a technical failure but a process gap. For example, a machine breaks. Why? Lack of maintenance. Why? The schedule wasn’t followed. Why? The operator didn’t know the schedule. Why? It wasn’t communicated. Root cause: poor communication protocol. Fix the communication, not just the machine. Luna: That seems so simple in theory, yet so hard to enforce. Who owns the accountability for digging that deep? Lucas: It’s shared ownership. The leader’s job isn’t to provide the answer, but to facilitate the questioning. If a manager answers the first or second 'why', the investigation stops too early. The leader must resist the urge to fix it themselves. They have to sit in the discomfort of not knowing, letting the team dig until they find the truth. It’s a leadership test. Are you there to look smart, or are you there to ensure the problem never happens again? Luna: I think a lot of middle managers struggle with that because they’re pressured to show immediate results. Taking time to dig feels like losing ground. Lucas: That’s the short-termism that kills long-term competitiveness. Toyota operates on decades, not quarters. They understand that a superficial fix now creates a debt service payment later. It’s like credit card interest on your operational processes. You pay a little now, or you pay a lot later. The question for any executive is: which debt are you willing to carry? Luna: This brings me to the idea of 'wasted time' again. Is there such a thing as productive idleness? Lucas: Absolutely. Toyota encourages 'genchi genbutsu', which translates to 'go and see'. Engineers and managers are expected to leave their desks and go to the shop floor. They spend time just observing, watching the flow, feeling the rhythm. It sounds like wasting time sitting around, but it’s where the best ideas come from. You can’t manage a process from a spreadsheet. You have to see the human element, the friction, the awkward movements. That observation time is essential data gathering. Luna: So, staring at the wall isn’t laziness, it’s research. Lucas: It’s immersive research. And it builds empathy. When you understand the physical reality of the work, your policies become more humane and effective. You stop asking people to do things that are physically impossible or ergonomically disastrous. It’s a practical benefit that also improves morale. People feel respected when leadership takes the time to understand their actual conditions. Luna: I wonder if remote work makes this harder. How do you 'go and see' when everyone is on Zoom? Lucas: It does make it harder, which is why remote teams need to be even more intentional about visibility. You need digital equivalents of the Andon Cord. Maybe it’s a status channel that signals blockages instantly. Maybe it’s regular video walkthroughs of your workflow, not just reports. You have to create spaces where the 'pause' is normalized. If your Slack is always pinging, the line never stops, and problems fester. Silence is a feature, not a bug. Luna: That’s a bold claim. Silence as a feature. Most people panic if their notifications dip below a certain threshold. Lucas: Panic is the enemy of quality. Think about the last time you made a critical decision. Did you do it while checking three different emails simultaneously? Or did you put the phone away, close the laptop, and just think? The latter yields better outcomes. Toyota knows that deep work requires protected time. They schedule 'reflection periods' into the day. It’s not optional. It’s part of the job description. Luna: I’d like to hear more about how they handle the pressure of global competition. Isn’t it easy to slip back into old habits when sales targets are missed? Lucas: Very easy. And it happens. During the financial crisis, demand dropped, and many companies cut costs by laying off staff and increasing workload for survivors. Toyota did the opposite. They retained their workforce and invested in training. They used the idle time to upskill. When demand returned, they were ready. Competitors who had chopped their teams were scrambling to hire and train. Toyota’s commitment to people paid off because they viewed humans as assets, not expenses. It’s a long-game strategy that requires immense confidence. Luna: So the lesson is: protect the pause, empower the worker, and dig for the root cause. It’s simple, but it’s radical. Lucas: It is radical. And it’s why Toyota remains a benchmark decades later. Other companies copy the tools—the kanban boards, the five whys—but they miss the soul. The soul is the belief that every person on the line has a brain, and that brain is worth listening to. If you strip away the hierarchy and let the best idea win, regardless of title, you unlock a level of innovation that pure efficiency metrics can never capture. Luna: It reminds me that leadership isn’t about controlling the tempo, but curating the conditions for the best music to play. Lucas: Beautifully put. The conductor doesn’t make the sound; they remove the obstacles so the orchestra can play. Our job as managers is to be the obstacle removers, not the note players. Let the experts do their work, step in only when the line stops, and help them find the root cause. Then, step back and let the flow continue. Luna: Before we go deeper into the mechanics of that, I want to pause for a moment. If these conversations have moved your work forward in some small way, consider supporting the show directly. It keeps these deep dives ad-free and helps us bring you more stories like this. You can support us at buy me a coffee dot com slash fexingo. Thank you for keeping this independent voice alive. Lucas: Yeah, and we really appreciate it. It allows us to take the time to research these cases thoroughly, rather than rushing for clicks. Back to the topic, though. Let’s talk about the actual implementation of the Five Whys. How do you prevent it from becoming a blame game? Luna: Oh, right. Because if I ask 'why did this fail?' five times, someone might feel like they’re being interrogated. Lucas: Exactly. The key is framing. You are investigating the process, not the person. The language should be 'what in the process allowed this error to occur?' not 'why did you make this mistake?'. It shifts the focus from individual culpability to systemic vulnerability. When people feel safe, they tell the truth. When they feel threatened, they hide it. And hidden problems are the most expensive kind. Luna: So psychological safety is actually a prerequisite for lean manufacturing. Lucas: It’s the foundation. Without it, the Andon Cord stays untouched. Workers will let the defect pass because they’re afraid of the reaction. So you build the safety first, then you build the systems. Culture eats strategy for breakfast, as they say. But in this case, culture enables the strategy to function. Luna: It’s fascinating how a manufacturing philosophy translates so cleanly to knowledge work. What’s one thing you’ll try to implement next week based on this? Lucas: I’m going to start using the Andon Cord concept in our editorial meetings. If someone spots a logical gap in a story outline, they get to stop the meeting right there. We don’t move on until we’ve solved it. It’ll slow down the initial planning, but it’ll save us weeks of rewriting later. It’s a bet on quality over speed. Luna: I’m going to try scheduling ten minutes of pure observation during my team check-ins. Just watching how they interact, not talking, just seeing. It might feel weird at first, but I think it’ll reveal some hidden dynamics. Lucas: Do it. And don’t apologize for taking the time. Frame it as due diligence. You’re gathering data on your own team’s ecosystem. It’s smart management, not wasted time. Luna: Smart management. I like the sound of that. It’s less about doing more, and more about seeing clearly. Lucas: Exactly. In a world obsessed with velocity, clarity is the ultimate competitive advantage. Take a breath, pull the cord if you need to, and find the root cause. The rest will follow.