Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How Toyota Standardized Innovation Without Killing It
Transcript
- Lucas: When we talk about innovation, we usually picture a lone genius in a garage, or a skunkworks team with no rules. But Toyota — arguably the most operationally excellent company on earth — takes the opposite approach. They standardized innovation itself. Luna: Standardized innovation sounds like an oxymoron. How do you systematize something that's supposed to be unpredictable? Lucas: That's exactly the tension. And Toyota's answer is a set of tools and rituals that channel creativity into a repeatable process. Let's start with the A3 problem-solving report. Luna: A single sheet of paper, right? Fits on one side of an A3-sized page. Lucas: Exactly. The A3 template forces you to state the problem, the current condition, the root cause analysis, the proposed countermeasure, and a check plan — all within that one page. No PowerPoint decks, no appendices. It's a discipline. Luna: And this is used for every improvement project, from a factory floor tweak to a supply chain overhaul? Lucas: Correct. The A3 is the basic unit of communication. Toyota runs roughly a million A3s per year across its global operations. Each one represents a specific problem that someone owns. Luna: A million. That means there are a million experiments happening simultaneously, all standardized under one format. Lucas: Right. And the key is that A3s aren't just documents — they're living tools. They're reviewed in 'obeya' rooms, which are physical war rooms where cross-functional teams gather around the visual displays. Luna: Obeya translates to 'big room' in Japanese. I've seen photos — walls covered with charts, timelines, and A3s pinned up. Lucas: Exactly. The obeya creates a cadence of review. Every week, the team stands in front of the boards and walks through each A3. What's the status? What blocked progress? Do we need to pivot? This is where standardization meets accountability. Luna: So the process is standardized, but the solutions are emergent. That's interesting. Lucas: And there's a crucial rule that keeps the system from becoming bureaucratic: every improvement must be reversible within 24 hours. If a change doesn't work, you undo it immediately. No sunk costs, no pride. Luna: That's a very different approach from most companies, where an initiative gets launched and then they double down to justify it. Lucas: Let me give you a concrete example. In 2019, at Toyota's Georgetown, Kentucky plant, a line worker named Maria noticed that the robotic weld guns on the chassis line were consuming more copper electrodes than necessary. Luna: She filed an A3? Lucas: She did. Her A3 identified that the electrode dressing interval — that's the automated cleaning that happens between welds — was set to a universal frequency. But different body panels require different weld depths. So she proposed variable dressing intervals based on the panel type. Luna: And they let her test it? Lucas: Within a week, her team ran a small experiment on one shift. The result: electrode life increased by 30 percent, and the change was reversible — they could go back to the old setting in minutes if it caused defects. It didn't. The plant implemented it across all shifts, saving an estimated two point three million dollars annually. Luna: From a line worker's observation, using a standard template, with a reversible experiment. That's the system working exactly as designed. Lucas: Now contrast that with what happens at many companies when a frontline employee spots an issue. They tell their supervisor, who tells their manager, who eventually requests a project. By the time a decision comes down, the problem has changed, or the solution has been watered down. Luna: I think that's the real innovation in Toyota's model — not the A3 or the obeya themselves, but the permission structure. It empowers the person closest to the problem to experiment, fail small, and scale what works. Lucas: Yeah. And when a new CEO takes over and has a grand vision, that's actually another area where Toyota's approach is really interesting. They don't scrap the system. Luna: You know, it's funny — talking about these small experiments and the infrastructure that supports them, it reminds me of why shows like this exist. A couple of dollars a month from listeners is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Lucas: It does make a real difference. Helps us keep the episodes ad-free and focused on the kind of operational depth we're talking about right now. So thank you to anyone who chips in. Luna: Alright, back to Toyota. You mentioned that when a new CEO comes in, they don't tear down the system. Can you elaborate? Lucas: Sure. In 2023, Toyota had a leadership change — Koji Sato took over from Akio Toyoda. In many companies, that would trigger a restructuring, a new strategic framework, a new set of acronyms. At Toyota, Sato's main initiative was essentially 'more of the same, but faster.' He didn't change the innovation process; he accelerated its cadence. Luna: Because the system itself is the competitive advantage. It's not dependent on a single leader's intuition. Lucas: Exactly. Compare that to what happened at a major US retailer I'll leave unnamed. In 2018, they hired a new head of innovation who launched a centralized 'innovation lab' separate from operations. It had its own budget, its own building, its own culture. The lab produced dozens of prototypes. Almost none made it to stores. Luna: Because there was no bridge to the actual operations team. Lucas: The lab was trying to solve problems that the operations team didn't recognize as problems. And when the operations team had real problems, they didn't go to the lab — they went to their own supply chain group. The lab was shut down after two years with little to show. Luna: Toyota would never have made that mistake. Their innovation happens inside operations, not separate from it. Lucas: Right. And that's why the A3 process is so powerful. It's not a suggestion box — it's a workflow that connects the idea to the resource allocation. Every A3 has a cost-benefit analysis, and when it's approved, the money comes from the department's own budget. No separate innovation fund. Luna: So the people funding the experiment are the same people who will benefit from it — or suffer if it fails. That aligns incentives. Lucas: It does. And it keeps the number of experiments manageable. Toyota doesn't try to do a million A3s all at once. They have a natural throttle because each department can only sustain the experiments that its own capacity allows. Luna: We should also mention that Toyota's approach isn't just for manufacturing. They've applied it to software development, HR, even dealer networks. Lucas: Absolutely. There's a well-known case from Toyota Financial Services where a team used A3s to reduce loan processing time from 14 days to 3. The same tools, the same cadence, different domain. Luna: So what's the lesson for a small business owner or a manager listening? They probably don't have the resources to roll out Toyota's entire system. Lucas: Start with the reversible experiment rule. For any change you make, ask: can I undo this within 24 hours? If the answer is no, you need to break the change down into smaller pieces. That alone prevents a lot of bad decisions. Luna: And the A3? Could a two-person shop use that? Lucas: Absolutely. An A3 is just a structured conversation. Two people can sit down with a piece of paper and ask: what's the problem, what's the root cause, what are we going to try, how will we know if it worked? That's a powerful discipline at any scale. Luna: It's almost like the scientific method for business operations. Lucas: That's exactly what it is. Hypothesis, experiment, measurement, iteration. Toyota just made it a habit. Luna: So the next time I hear someone say 'innovation can't be managed,' I'll point them to Toyota's million-A3-a-year system. Lucas: And remind them that the most innovative company in the world standardized everything except the solution.