Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How Toyota Cut Line Stops 70 Percent With One Andon Tweak
Transcript
- Lucas: Toyota’s Tahara plant in Japan is often called the most efficient car factory on earth. It's where Lexus vehicles are built, and it's also the birthplace of a famous operational tool: the Andon cord. Luna: Right, the cord that any worker can pull to stop the entire assembly line. I've heard it's a cornerstone of lean manufacturing. Lucas: Exactly. The idea is that if a worker sees a defect—say a misaligned part or a missing bolt—they pull the cord, the line stops, and the problem gets fixed immediately. But for years, Tahara had a problem: workers were pulling the cord too often for trivial issues, and line stops were eating into production targets. Luna: So the solution wasn't to pull the cord less—it was to change how the system responded when it was pulled. Lucas: Bingo. Toyota realized the issue wasn't the frequency of pulls; it was the response time. When a worker pulled the cord, a team leader would walk over, assess the issue, and either fix it quickly or let the line stop. But the walk time alone could take 30 seconds, and if the leader was busy, the line sat idle for minutes. Luna: Thirty seconds doesn't sound like much, but in a plant that produces a car every minute, that's half a car's worth of lost production per stop. Lucas: Right. So Toyota made one change: they reprogrammed the Andon board to show not just the location of the pull, but the exact time elapsed since the pull. And they set a target—team leaders had to respond within 15 seconds. If they didn't, the line would automatically stop. Luna: Wait, so before, the line only stopped if the leader decided it should. Now, it stops automatically if the leader is too slow? That flips the incentive. Lucas: Completely. Suddenly, team leaders had a strong motivation to be at the pull point within 15 seconds. They started positioning themselves closer to the line, anticipating frequent pull zones. They even began communicating with workers via headsets to pre-empt issues. Luna: And the result? A 70 percent reduction in line stops? That's huge. Lucas: Yes. Line stop time dropped by 70 percent. But here's the counterintuitive part: the number of pulls actually went up. Workers felt more comfortable pulling the cord because they knew the system would handle it quickly. Quality improved, and overall production efficiency rose. Luna: So the fix wasn't about punishing workers for pulling—it was about making the system responsive. That's a lesson that applies way beyond car factories. Lucas: It's the difference between a panic button and a signal. The Andon cord was originally designed as a signal, but over time, the culture turned it into something workers hesitated to use because stopping the line felt like failure. The tweak restored its original purpose. Luna: I've seen a similar principle in software teams. When a bug gets reported, the best teams don't just log it—they have a rapid response protocol. If the on-call engineer doesn't acknowledge within five minutes, the escalation kicks in automatically. Lucas: Exactly. It's the same idea: the escalation is automatic, not discretionary. That removes the fear of overreacting. And in hospitals, rapid response teams for deteriorating patients work on a similar timer. If vital signs cross a threshold, the team must assemble within a set time, or an alert goes to the unit director. Luna: So the common thread is: design the system so that the right response happens fast, without requiring a hero to decide whether to act. Lucas: Yes. Toyota's tweak cost almost nothing—just software changes and some training. But it required a shift in mindset. The team leaders had to trust that responding quickly wouldn't undermine their authority, and workers had to trust that pulling the cord wouldn't get them blamed. Luna: And that cultural shift is often the hardest part. How did Toyota get buy-in? Lucas: They started with a pilot on one line. They let team leaders see the data: average response time, number of stops, and defect rates. Within two weeks, the pilot line had 40 percent fewer stops. The team leaders themselves became advocates because they saw they could handle more issues without breaking flow. Luna: So the data sold itself. That's a great example of leading with evidence, not mandates. Lucas: And once the system was rolled out, they kept measuring. They found that the optimal response time was actually 12 seconds, not 15. So they tightened the target. Continuous improvement, right? That's kaizen. Luna: I love that they didn't stop at 70 percent. They kept iterating. Lucas: That's the Toyota mindset. The Andon tweak is a small story, but it illustrates a huge principle: when you change the structure of a feedback loop, you change behavior. And behavior change is what drives operational results. Luna: It also shows that the best operational fixes often come from the people doing the work. Did the idea come from a team leader or a manager? Lucas: Actually, it came from a group of production engineers who were analyzing stop data. They noticed that long response times were correlated with longer line stops even for minor issues. So they proposed the automated escalation as a way to force fast response. But they tested it with workers first. Luna: So bottom-up input with top-down support. That's a formula that works in a lot of contexts. Lucas: And it's worth noting that this wasn't a massive investment. Toyota didn't buy new robots or redesign the line. They just changed the rules of an existing system. That's the kind of low-cost, high-impact change that any operation can look for. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, that's what keeps the episodes coming without interruption. And we really appreciate it. Luna: Alright, back to the Andon cord. So what happened after Tahara? Did Toyota apply this to other plants? Lucas: They did. Within a year, the automated Andon response was standard across all Toyota plants in Japan, and later worldwide. Each plant customized the time targets based on their line speed and part complexity, but the principle remained: fast, automatic escalation. Luna: And I assume other manufacturers have adopted it too? Lucas: Yes, many have. But the key is not to copy the tool; it's to copy the logic. What is your version of the Andon cord? In a hospital, it might be the rapid response team. In a call center, it might be an escalation button for difficult customers. The question is: how quickly does the right person respond, and is that response automatic or discretionary? Luna: So the lesson for any operator: find the signal that's being ignored or feared, and make the system respond faster and more reliably. Lucas: Exactly. One small tweak can turn a bottleneck into a flow enabler. And the beauty is that the data to identify that tweak is often already there—you just have to look for patterns in response times. Luna: Thanks, Lucas. That was a great deep dive into a tiny change with a massive impact. Lucas: Thanks, Luna. And to our listeners, maybe take a look at your own team's escalation processes. You might find a 15-second target that could change everything.