For years, I’ve heard Kaizen translated into two words: continuous improvement.
It’s not exactly wrong. But after working as a Kaizen Leader at Toyota, I learned that those two words leave out one of the most important parts: improvement isn’t just about making the process better. It’s about developing people who know how to make it better.
If you want to see where your own processes may need attention, start with my free Process Optimization Audit Checklist.
Because Kaizen doesn’t mean changing everything all the time. And it doesn’t mean what many companies have come to think it means.
Kaizen Doesn’t Mean What Most Companies Think It Means
There is a Japanese word that has become almost impossible to separate from Toyota: Kaizen.
Ask most business leaders what it means and you’ll probably hear the same answer: continuous improvement. That’s how it’s described in books, consulting frameworks, training programs, and countless conversations about the Toyota Production System.
And it’s not entirely wrong.
But after living and working in Asia and eventually becoming a Kaizen Leader at Toyota, I came to understand that those two words leave out something important. Kaizen (改善) literally means something closer to “change for the better.” Toyota itself often uses “continuous improvement” when explaining Kaizen in English, but it has also described this as a broad translation rather than the literal meaning.
That might sound like semantics, but the distinction matters. When Kaizen became synonymous with continuous improvement, many companies began treating it as an activity: an improvement workshop, a project, a suggestion program, or the responsibility of a team tasked with making processes more efficient.
What I experienced at Toyota was different. Kaizen wasn’t simply something you did to the work. It was part of how people learned to think about the work.
Toyota Didn’t Invent Kaizen
This is another misconception. Toyota did not invent the word Kaizen, just as it didn’t invent every idea that eventually became associated with the Toyota Production System. The Japanese term existed independently of Toyota.
Toyota developed its own approach to improvement over decades, incorporating ideas from inside and outside Japan into a management system that became globally influential. Statistical quality control was introduced at Toyota in 1949, its Creative Idea Suggestion System followed in 1951, and quality-control activities continued developing over the following decades.
Kaizen became deeply connected to Toyota’s philosophy of involving people throughout the organization in improving the work. The history of Toyota’s suggestion system gives us a useful window into what that actually looked like.
In 1951, Toyota employees submitted just 789 improvement suggestions. By 1972, they submitted 168,000 suggestions in a single year, 76% of which were adopted, according to Toyota’s history of its Creative Idea Suggestion System.
More than 70 years after the program began, the practice was still active. In 2023, Toyota reported approximately 810,000 employee suggestions, equivalent to about 14.4 suggestions per plant technical employee, according to Toyota Times.
The point isn’t the number, and it certainly isn’t that every company should try to collect hundreds of thousands of employee ideas. The more interesting question is what kind of organization produces that many people who are actively thinking about how their work could be better.
That’s where Kaizen becomes much more interesting.
The Improvement Isn’t the Most Important Part
Companies often approach improvement in a predictable way. Leadership identifies a problem. A project team analyzes it. Someone designs a solution. Management approves it, and employees are trained on the new process.
The process may genuinely improve. But there is another question worth asking: Did the organization become better at improving?
Those aren’t necessarily the same thing.
Imagine Sales and Operations repeatedly struggling with incomplete information during customer onboarding. Leadership could solve the immediate problem by adding another required field, creating another checklist, introducing another approval, or writing another SOP. Any of those might help.
But consider what happens if the people doing the work learn how to see where information breaks down, understand why it’s happening, test a countermeasure, study the result, and incorporate what they learned into the process. The process improves, but so does the organization’s ability to solve the next problem.
That was one of the biggest differences I saw at Toyota. The goal wasn’t simply to create better processes. It was to develop people capable of creating better processes.
Constant Change Isn’t Kaizen
This distinction matters because companies today are changing constantly. They introduce new software, restructure teams, redesign workflows, build dashboards, set new priorities, and launch new initiatives. With so much activity, it can feel like continuous improvement because something is always changing.
But change and improvement are not the same thing.
A company can change a process and make it worse. It can implement technology that creates more work. It can add an approval that prevents one mistake but slows down hundreds of transactions. It can restructure a department without changing the broken workflow moving through it.
Kaizen requires more discipline than simply asking, “How can we make this better?” You have to understand the current condition, identify the problem, investigate what’s creating it, test a countermeasure, and learn from what happens next.
This is also why standardization and Kaizen aren’t opposites. I’ve heard people argue that standardization prevents innovation, but without understanding the current way the work happens, what exactly are you improving from?
A standard gives you a baseline. Kaizen gives you a disciplined way to challenge it. When you discover a better way, that becomes the new baseline until you learn something else.
Kaizen Changes the Leader’s Job
There is another implication that doesn’t get discussed enough. If leaders are always the people identifying problems and designing solutions, the company can improve while simultaneously becoming more dependent on leadership.
That’s not a scalable system.
A leader practicing Kaizen doesn’t need to have every improvement idea. The leader needs to create the conditions where other people can recognize problems, understand them, test appropriate changes, and learn from the results.
That requires more than telling people they’re empowered. Employees need access to the right information. They need clear expectations and standards. They need enough authority to improve the work they understand. And they need leaders who don’t immediately take that authority back when something goes wrong.
Without those conditions, improvement keeps moving upward. Employees identify problems, managers solve them, and executives approve the solution. Eventually, the organization has a small number of people responsible for thinking and a much larger number responsible for executing.
That’s almost the opposite of what Kaizen is trying to create.
Maybe We’ve Been Measuring the Wrong Thing
When companies talk about continuous improvement, they often measure the improvements themselves. How much time did we save? How much waste did we remove? How much did quality improve? How many improvement projects did we complete?
Those outcomes matter, but there is another measure leaders should pay attention to: Is the organization becoming more capable of improving without waiting for leadership to initiate every change?
Can the people closest to the work recognize when something isn’t performing as expected? Can they investigate why? Can they distinguish the actual problem from the symptom? Can they test a countermeasure rather than immediately adding another permanent layer to the process? Can they determine whether the change actually made the work better? And can the organization capture what it learned and make that knowledge part of how the work gets done?
If not, doing more continuous improvement projects may not create a continuous improvement culture. It may simply create more projects.
That’s why I’ve become careful about reducing Kaizen to two English words.
Continuous improvement describes an outcome we want. Kaizen asks something deeper of an organization. It asks us to develop people who can see problems, give them a method for understanding those problems, create the conditions for them to improve the work, and then learn from what happens.
The most important thing I learned about Kaizen at Toyota wasn’t that everything should constantly change. It was that improvement shouldn’t depend on a small group of people whose job is to improve everything for everyone else.
The process should get better, but the people improving it should get better, too.
That’s the part of Kaizen I think we lose when we simply call it “continuous improvement.”
Want to Work With Us?
Improvement shouldn’t depend on a few people at the top.
The Ops Edge Academy™ is a 12-week implementation and certification program that helps operations leaders build the systems and problem-solving discipline to improve how work gets done, using PDCA, process mapping, and real operational challenges from their business.
Enrollment for the January 2027 cohort is now open.
