Kaizen is the practice of continuous, incremental improvement — every person improving their own work every day, from a standard. The records below state what kaizen is, where it came from, the method it runs on, the vehicles Toyota uses to carry it, and how improvements spread — each traced to a Toyota-grounded source.
Kaizen is daily improvement by every person, not a multi-day event
Kaizen at Toyota is the daily discipline of working from a standard, finding problems, and establishing a better standard — carried out by every person, from shop-floor workers to executives. The 3-to-5-day "kaizen event" or "kaizen blitz" common in Western practice has no real equivalent in Toyota's traditional approach. Toyota runs focused improvement activities, but the backbone of kaizen is continuous daily improvement, not an episodic workshop.
Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen is an ordinary Japanese word, not a Toyota coinage
改善 is an everyday Japanese word meaning "change for the better," used in any context. 改 (kai) means change, reform, or renew — correcting what is wrong; 善 (zen) means good or virtue. Toyota did not invent the word. What Toyota built was an organizational system around it, making improvement the responsibility of every employee rather than a management program imposed from above.
Japanese usage (改善); Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen at Toyota has several roots, not a single origin
Kaizen draws on multiple sources: Training Within Industry (TWI), whose Job Methods module taught supervisors to improve their own work (Toyota began TWI in 1951); the JUSE quality movement, which produced QC circles (first registered with JUSE in 1962); Toyota's Creative Idea Suggestion System (1951); and Taiichi Ohno embedding kaizen into the structure of the production system itself. The TWI/Job Methods influence in particular is frequently overlooked but was foundational.
Toyota 75-Year History; Isao Kato & Art Smalley, Toyota Kaizen Methods (2011) — artoflean.com/reference/kaizen
Kaizen begins from standardized work
Kaizen cannot function without a stable starting point. Every kaizen begins from a documented current standard and produces a new, better standard. The cycle is: standardize → follow the standard → find problems → improve → set a new standard → repeat. Improving a process that is not standardized gives no baseline and no way to tell whether a change helped; the result is random oscillation, and gains regress within weeks. Standards without kaizen stagnate; kaizen without standards is unanchored.
Taiichi Ohno, Toyota Production System (1978); Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen's purpose is eliminating waste and developing people — cost reduction is a byproduct
At Toyota the focus of kaizen is eliminating waste, developing people, and building capability. Lower cost follows as a result; it is not the objective. When cost reduction is made the primary driver, workers correctly read kaizen as a threat to their jobs and participation collapses. Framing kaizen as a cost-cutting program is the most common Western distortion of the practice.
Taiichi Ohno, Toyota Production System (1978); Art Smalley, Art of Lean — artoflean.com/reference/kaizen
In kaizen, management's role is to develop people's problem-solving capability
At Toyota, management's primary role in kaizen is not to improve processes directly but to develop the problem-solving capability of the people who do the work. A manager who fixes problems without building the team's ability to find and fix problems themselves is not doing the job. The aim is for the people closest to the work to be the ones improving it — which is why the suggestion system, QC circles, and jishuken are all, at bottom, vehicles for developing people.
Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen is part of daily work, not an activity separate from it
If improvement is treated as something done during special events, apart from the "real job," a kaizen culture never forms. At Toyota, kaizen is the job: working to the standard and improving the standard are inseparable. The expectation is that every person improves their own work every day.
Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen depends on the ability to see abnormalities
Kaizen depends first on being able to see when something deviates from the standard. This is why visual management, andon, and standardized work are prerequisites: they make deviations obvious. Without the means to see problems, there is nothing concrete to improve, and kaizen collapses into unfocused idea-gathering.
Taiichi Ohno, Toyota Production System (1978); Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Kaizen is inseparable from respect for people (人間性尊重)
Kaizen at Toyota cannot be separated from the principle of respect for people (人間性尊重). Its purpose is to develop every person's problem-solving capability, not to extract more output from workers. When that principle is missing, kaizen degenerates into a tool of management control rather than a means of developing people, and participation falls away.
Art Smalley, Art of Lean; Toyota's Respect for People pillar — artoflean.com/reference/kaizen
Kaizen runs on PDCA — and the discipline is not stopping at containment
Kaizen is structured improvement on the PDCA cycle: grasp the situation at the genba, find and verify the root cause, implement a countermeasure, check the result against the target, and standardize if it worked. The most common failure is stopping at containment — patch the defect, restart the line, move on — so the problem recurs. Kaizen demands investigation of why the problem occurs and countermeasures that prevent recurrence, not patches.
Practical Problem Solving (PDCA) — artoflean.com/reference/practical-problem-solving
Toyota distinguishes the kind of problem, not just the solution
Toyota's problem-solving tradition separates occurrence-type problems (発生型, hasseigata — a deviation from a standard or normal condition) from setting-type problems (設定型, setteigata — a self-imposed higher target than the current level). Kaizen is not only restoring a standard after something goes wrong; it is also deliberately setting a more demanding target and closing the gap. The disciplined root-cause analysis is the same; the starting point differs.
Practical Problem Solving; Four Types of Problems — artoflean.com/reference/practical-problem-solving
Toyota teaches kaizen as a six-step skill, not an attitude
Kaizen at Toyota is taught as a learnable craft through a structured skills course: discover the waste, analyze the current method, generate improvement ideas, develop a plan, implement, and confirm the result. This is the method behind Toyota Kaizen Methods (subtitled "Six Steps to Improvement"). Treating kaizen as merely a mindset or a slogan misses that Toyota trains it as a specific, repeatable procedure.
Isao Kato & Art Smalley, Toyota Kaizen Methods: Six Steps to Improvement (2011) — artoflean.com/learning/kaizen
Hansei — honest self-reflection — is what keeps kaizen from stalling
Hansei (反省) is deliberate, uncomfortable self-reflection: what went wrong, what you failed to see, what you must change. Toyota practices it even after success, in formal hansei-kai, and it lives in the Check and Act stages of PDCA. Fujio Cho reportedly said hansei without a feeling of regret is not real hansei. Complacency is the enemy of improvement; hansei is the discipline that prevents "we did a good job" from ending the cycle.
Hansei — artoflean.com/reference/hansei
An improvement is not finished until the standard is updated
A kaizen is incomplete when the local problem is merely fixed. The countermeasure must be captured in updated standardized work or the relevant process standard; otherwise the gain exists only in one person's memory and the old method returns when they are absent. Standardizing the improvement is what makes it permanent and what makes it transferable.
Practical Problem Solving; Yokoten — artoflean.com/reference/practical-problem-solving
The Creative Idea Suggestion System is judged by ideas implemented, not ideas submitted
What matters in a suggestion system is how many ideas are actually adopted and put in place, not how many are submitted. Toyota launched its individual Creative Idea Suggestion System in 1951, after Eiji Toyoda saw a suggestion plan at Ford; in 1953 it took the motto "Good Thinking, Good Products" (良い品 良い考). By 1973, on the order of 43,000 employees submitted more than 250,000 suggestions in a single year, well over half adopted; by its 30th anniversary in 1981 the annual count reached 1.4 million. Rapid response sustains it — small ideas are approved on the spot by the group leader. (Figures are historical, through the early 1980s; current reporting is not confirmed.)
Toyota 75-Year History (1951/1953/1973); Nemoto Masao, 1982 lecture (1.4 million / 1981, verbatim) — artoflean.com/reference/suggestion-system
QC circles are voluntary worker groups, launched by JUSE in 1962
A QC circle is a small group of frontline workers (typically 5-10 from one area) who voluntarily choose their own themes and solve quality and productivity problems using the seven QC tools. JUSE formally launched the QC circle movement in April 1962. Toyota embraced QC circles within its Total Quality Control system and won the Deming Application Prize in 1965. They remain active at Toyota today.
QC Circle — artoflean.com/reference/qc-circle
QC circles die when participation is made mandatory or themes are assigned from above
The power of QC circles is voluntary engagement and self-chosen themes. When management mandates participation or assigns the problems, the circle becomes a directed work group and the ownership that drives genuine problem-solving is lost. Many Western QC-circle programs failed in the 1970s-80s precisely because they were imposed top-down, skipped the QC-tools training, or lacked management follow-through on implementing solutions.
QC Circle — artoflean.com/reference/qc-circle
Jishuken is a hands-on management/engineer study group, distinct from QC circles
Jishuken (自主研, from 自主研究, "voluntary self-study") is a study-group activity in which managers and engineers go to the shop floor to improve real production processes under an experienced sensei — learning TPS by doing it, not in a classroom. It is distinct from QC circles: jishuken is for managers and engineers and is sensei-guided; QC circles are voluntary frontline-worker groups. The sensei teaches by questioning and challenging, not lecturing.
Jishuken — artoflean.com/reference/jishuken
Jishuken originated in Toyota's Jishu Kenkyukai, founded October 1976
The formal jishuken activity — the Jishu Kenkyukai (自主研究会, "Voluntary Study Group") — was founded in October 1976 by Toyota's Production Research Division (the group later known as OMCD). The first session was held November 16, 1976 at Nippon Denso's Anjo plant, with 17 people from 17 cooperating supplier companies. Taiichi Ohno was not a member; he supported it as an advisor (顧問). By 1997 the supplier-facing activity had grown to 44 companies in 6 groups.
Jishuken; Toyota 50-Year History — artoflean.com/reference/jishuken
The Western "5-day kaizen event" descends from jishuken — via consultants who did not develop kaizen
The five-day kaizen-workshop format practiced in North America since the late 1980s is loosely based on what individuals such as Yoshiki Iwata (Toyoda Gosei) and Chihiro Nakao (Taiho Kogyo) took from Toyota's jishuken events; they founded the consultancy Shingijutsu and packaged the format for overseas companies. Critically, although they helped establish improvement activity at their own supplier companies, none of them played any role in developing the kaizen methodology or the production system inside Toyota Motor Corporation. The event is a downstream adaptation, not the source.
Jishuken — artoflean.com/reference/jishuken
Jishuken is learning by doing — neither OJT nor classroom
The Jishu Kenkyukai was an unprecedented form of education: it took real problems from a host company's shop floor but abstracted the improvements into transferable general principles — a "pseudo-genba" (擬似現場) approach. Members from other companies worked on the host's problem, which simultaneously developed the participants' capability and delivered real results at the host site. Changes were physical and immediate, implemented during the activity, not recommendations for later.
Jishuken — artoflean.com/reference/jishuken
Yokoten is horizontal deployment — sharing improvements sideways across the organization
Yokoten (横展, from 横展開, "horizontal deployment") is the practice of spreading an improvement from where it was discovered to every other area facing the same condition. At Toyota it is an expectation, not a suggestion: solving a problem only in the place it was found is considered incomplete work. It takes three forms — copy (apply the proven solution directly), adapt (transfer the principle to different conditions), and learn (transfer the problem-solving method itself).
Yokoten — artoflean.com/reference/yokoten
The real mechanism of yokoten is Toyota's standards system, not the A3 alone
Outside observers usually cite the A3 report as Toyota's yokoten vehicle, and it plays a role. But per Art Smalley, who worked inside Toyota's manufacturing operations in Japan, the deeper mechanism is Toyota's extensive system of formal standards — standardized work, Toyota Manufacturing Standards (TMS), Toyota Manufacturing Regulations (TMR), and domain standards. An improvement that is shared but not codified into the relevant official standard is only a suggestion; once the standard is updated, it becomes the new baseline everyone follows.
Yokoten — artoflean.com/reference/yokoten
Yokoten is a push system done in person, not a best-practice database
Yokoten fails when treated as a knowledge-management database or lessons-learned repository — people do not search a database when they have a problem. It is a push system: the team that developed the improvement goes to the other areas, observes their conditions, and helps adapt the solution, verifying it works in each location. This makes yokoten inseparable from genchi genbutsu, and it is the responsibility of the team that solved the problem, not a separate department.
Yokoten — artoflean.com/reference/yokoten
Toyota practices hansei after success, not only after failure
Toyota holds hansei-kai (reflection meetings) at the end of projects and launches even when they succeed, focusing on the gaps — what should have been anticipated, what decisions were suboptimal. John Shook has described how presenting an A3 at Toyota was a demonstration of your thinking: good results with no articulated learning made for a weak A3. The learning matters as much as the outcome, which is why reflection is institutionalized rather than left to whoever has time.
Hansei — artoflean.com/reference/hansei
Suggestion-system rewards run from a few hundred to several hundred thousand yen
Rewards in Toyota's Creative Idea Suggestion System range from a few hundred yen for a routine submission to several hundred thousand yen for an outstanding one. The amount matters less than the signal — that the employee's thinking is genuinely valued.
Toyota 75-Year History — artoflean.com/reference/suggestion-system
A Toyota suggestion is a single sheet, written during the workday
Submission is deliberately light: one A4 sheet — current situation, before, after, result — handwriting allowed, done during work, with the bar kept low on purpose ("no idea too small"). Every proposal is read and commented on by a supervisor. What keeps it alive is mendomi — the supervisor's attentive follow-up on each one.
Toyota 75-Year History; OJT Solutions — artoflean.com/reference/suggestion-system
At Toyota, suggestions are about your own work — and adopted on the spot
Two features set Toyota's system apart (per Nemoto Masao, 1982): suggestions center on one's own and one's group's work — at Ford, many were about other people's work — and adoption is immediate, with a squad, group, or section leader who has the authority simply deciding, so "by the time of review it's mostly already done." Nemoto noted it might better be called a reward system than a suggestion system.
Nemoto Masao, 1982 lecture "The Role of the Manager" — artoflean.com/reference/suggestion-system
Prompt recognition is what keeps suggestions coming
Suggestions made this month are mostly reviewed and recognized the next. Nemoto's point: a person who got no reaction to his last suggestion won't bother making the next. Rapid acknowledgment, not the size of the reward, sustains participation.
Nemoto Masao, 1982 lecture — artoflean.com/reference/suggestion-system
How a QC circle is actually structured
A QC circle is 5-10 workers from one area with an elected leader, meeting weekly or biweekly for 30-60 minutes and working a theme through the seven QC tools: pick a theme, analyze the current situation with check sheets and Pareto/Ishikawa diagrams, find the root cause, develop and test a countermeasure, verify, standardize, and present. A company-level promotion structure — a steering committee, often chaired by the plant manager — is what keeps a voluntary activity from quietly withering.
QC Circle — artoflean.com/reference/qc-circle
QC circles came from a JUSE journal, extending quality tools to the floor
JUSE launched the QC circle movement in April 1962 through its journal Genba to QC (later renamed QC Circle). Japanese firms had used statistical quality control since the early 1950s, but it was confined to engineers and managers; the circle movement deliberately put those tools in the hands of the frontline workers closest to the problems.
QC Circle — artoflean.com/reference/qc-circle
QC-circle results are shared up and across — recognition and yokoten at once
At Toyota, circle presentations are a real event: groups present to management, and the best circles compete company-wide and even between companies. The presentation does two jobs — recognition that sustains motivation, and yokoten, the horizontal sharing of a proven improvement to other areas.
QC Circle — artoflean.com/reference/qc-circle
Who ran the jishuken: Ohno advised it, he didn't lead it
Toyota's Production Research Division (later OMCD) ran the Jishu Kenkyukai. Taiichi Ohno supported it as an advisor (顧問) and spoke to participants, but never personally led the supplier workshops; Kikuo Suzumura and Fujio Cho were among Toyota's support personnel, and Nampachi Hayashi was a key contributor in the later period. The point is often garbled outside Toyota — Ohno's role was advisory, not hands-on.
Jishuken — artoflean.com/reference/jishuken
How a jishuken session ran: monthly, rotating hosts, four parts
The Jishu Kenkyukai met about once a month, companies taking turns hosting; the host's own shop-floor problem became the theme. Each cycle had four parts: establish the theme, improve it with a cross-company team inside a set time, trial the countermeasures and present results to all members, and receive critical evaluation from Toyota's Production Research Division. If results fell short, follow-up sessions continued on the same theme.
Jishuken — artoflean.com/reference/jishuken
Hansei (反省): learned in childhood, and stronger than "reflection"
Hansei combines 反 (turn back) and 省 (examine oneself) — to look back at your own actions and examine them critically. Japanese children learn it from elementary-school age: when something goes wrong, the expected response is to reflect, acknowledge the shortcoming, and commit to doing better. "Reflection" is too mild a translation; hansei carries genuine regret and personal responsibility.
Hansei — artoflean.com/reference/hansei
Hansei is the hardest Toyota practice to transfer
The mechanics can be copied — hold reflection meetings, add a "lessons learned" section. The spirit cannot be installed by a process: the genuine personal discomfort, the willingness to confront your own inadequacy, the cultural assumption that this is simply how adults behave. In Japan, acknowledging your shortcomings is a virtue; deflecting blame loses respect.
Hansei — artoflean.com/reference/hansei
Ohno built kaizen into the structure of TPS, not into a program
Beyond the suggestion system and the circles, Ohno embedded kaizen into the design of the production system itself: reducing the number of kanban, shortening changeovers, and solving the problems that andon surfaces are all kaizen driven by how the system is built — not by special events laid on top of it.
Taiichi Ohno, Toyota Production System (1978) — artoflean.com/reference/kaizen
Isao Kato — Toyota's TWI trainer behind the standardized-work and kaizen courses
Much of Toyota's internal kaizen and standardized-work training traces to Isao Kato, the company's TWI expert, who codified the methods into formal courses. The lineage runs through TWI Job Methods: Toyota began TWI in 1951, and JM's structured "question every detail, eliminate first" approach fed directly into how Toyota teaches improvement.
Isao Kato & Art Smalley, Toyota Kaizen Methods (2011) — artoflean.com/reference/kaizen
Kaizen operates on several levels at once — daily kaizen is the backbone
Toyota runs kaizen on multiple levels simultaneously: daily kaizen (small improvements as part of normal work), QC circles (voluntary small-group problem-solving), the individual suggestion system, and project-level improvement for larger cross-functional or capital changes. Daily kaizen is the most common and the hardest for outsiders to copy, because it requires a culture where frontline workers are expected and enabled to improve their own work continuously.
Art Smalley, Art of Lean — artoflean.com/reference/kaizen
Three kinds of problems — including the visionary kind that defined the Prius
Toyota distinguishes occurrence-type problems (発生型 — a deviation from a standard), setting-type (設定型 — a self-imposed higher target), and a third, vision- or goal-oriented type: pursuing a future ideal that does not yet exist, where even the target must first be defined. Large development challenges like the Prius are of this third kind. Kaizen spans all three; the disciplined analysis is the same, only the starting point differs.
Practical Problem Solving; Four Types of Problems — artoflean.com/reference/practical-problem-solving
PPS, TBP, and A3 are the method, the name, and the format
Practical Problem Solving (PPS) was Toyota's earlier name for its structured eight-step PDCA method; Toyota Business Practice (TBP) was adopted around 2005 as the company-wide standard name (PPS persisted in Europe and some operations). A3 is the format — a single 11×17 sheet — that documents the thinking. Same logic, three labels people often confuse.
Practical Problem Solving — artoflean.com/reference/practical-problem-solving
Kaizen needs a team leader free to respond in seconds
Structured improvement requires a team leader available to respond within seconds when a problem occurs — which in turn requires adequate staffing ratios and a clear understanding that the team leader's primary job is responding to and solving problems, not administrative work. Where that role is starved, problems get patched and buried instead of investigated.
Practical Problem Solving — artoflean.com/reference/practical-problem-solving
Why Toyota invests so heavily in standards: it is what makes improvement stick
An improvement shared in person is necessary but not sufficient. Until it is written into the official standard — standardized work, a manufacturing standard, an engineering standard — it stays a suggestion that fades when the person who made it leaves. Codify it into the standard and it becomes the new baseline everyone follows. That is why Toyota is, at its core, a heavily standardized knowledge company.
Yokoten — artoflean.com/reference/yokoten
Kaizen is mandatory because cost reduction is the only profit lever a plant controls
Profit = (price − cost) × units sold, so a manufacturer has three levers: raise the price, sell more units, or lower the cost. In a competitive market a supplier can do almost nothing about the first two — customers set the price and demand cost-downs, and volume is pull-driven by the customer's schedule. That leaves cost reduction as the one lever the plant can actually pull, which is why kaizen is a daily necessity, not an optional program.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Cost-Plus vs. Cost-Reduction: under cost-reduction logic, waste elimination IS the profit
Two assumptions can govern how a plant pursues profit. Cost-Plus fixes the margin and adjusts the price (price = cost + profit) — an inefficient plant simply charges more. Cost-Reduction fixes the price (the market sets it) and treats every element of cost as improvable (profit = price − cost). At Toyota the price option is closed, so finding and removing waste from the process is the mechanism of profit itself — every waste eliminated is added back to margin.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
The real cost target is the method, not labor — labor is under 10% of product cost
Direct labor is typically less than 10% of the total cost of a finished product, so cutting labor 20% improves total cost only ~2%. Roughly 70% of manufacturing cost is locked in by product design before the production plan is written. What remains in the leader's reach is the cost embedded in how the work is performed — the motions, waits, inventory, defects, and conveyance built into the method. That is where kaizen focuses.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Two ways to raise output — quantity-based adds cost, quality-based removes it
Asked how to increase production, most people reach for quantity-based answers: more workers, more machines, more overtime. Each raises output but raises cost at roughly the same rate. The quality-based alternative gets more from the same people, machines, and hours by changing the method — remove the waste and one person on one machine in one hour who made 100 parts can make the required quantity with effort to spare. TPS takes the quality-based path; quantity-based thinking never questions the method.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Kaizen is one spoke of the leader's role, not a separate assignment
A Toyota team leader carries production, quality, cost, safety, people development, equipment, and policy at once — and kaizen is one spoke among them, sitting in the same circle, not off to the side. Improving the way work is done is how a leader meets all the other responsibilities simultaneously. Where the role is narrowly defined as "just hit the numbers," kaizen atrophies; the breadth of Toyota's definition is what makes continuous improvement a daily necessity.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Kaizen and problem solving share one logic but differ in their trigger
Both follow the scientific method (observe, hypothesize, test, confirm) expressed as PDCA, so the discipline is the same. The difference is the starting point: problem solving begins from a deviation — a standard exists and something has gone wrong — while kaizen often begins before any standard is violated, from a leader's eye for waste or a challenge to improve cost, safety, or lead time even when today's performance is acceptable.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
The six-step kaizen cycle spirals — it never closes
The steps are: discover the improvement potential, analyze the current situation, generate original ideas, develop the plan, implement, and evaluate the new method. Step 6 loops back to Step 1 — confirming that a new method works raises the standard, and that raised standard becomes the baseline the next cycle scrutinizes. Kaizen without standardization gives temporary results; standardization without the next cycle gives stagnation. The procedure is built so neither has a natural stopping point.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Step counts vary (6, 8, 12) but all map to the same four PDCA phases
Different organizations teach six, eight, or twelve steps. The variation is real but superficial: kaizen on a work method, on a flow, and on equipment each need slightly different sub-steps, so the count expands or compresses with scope. Every version, mapped onto Plan-Do-Check-Act, carries the same logic. The count is a clue to what an organization finds hard — a TPM-heavy plant teaches twelve, a standardized-work plant teaches six — not evidence that one is more rigorous.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Most kaizen work happens in the Plan phase
In every step-count version, the Plan phase absorbs the most steps — discover the potential, analyze the current state, generate and select ideas — because that is where the analytical work lives. Do is always just one or two steps. Practitioners who plateau early have the Plan-phase concepts but never built the analytical depth the middle of the cycle requires.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Analyze from facts at the actual workplace — skipping analysis is the most common failure
Step 2 builds an accurate picture of how the work is actually done, from facts observed at the actual place with the actual object at the actual time — not from memory, assumption, or what the standard document says. The strong pull is to jump from "we have a waste" straight to "here is my idea," especially when the leader already has a solution in mind. But an idea chosen without real analysis usually fixes the visible symptom and leaves the root condition untouched.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Generate every candidate idea before judging any of them
Step 3 produces as many ideas as possible before evaluating a single one. Judging ideas while generating them is the most common way to kill the best answer early. Breadth is the resource the planning step then sorts and tests — narrow the field too soon and the strongest option may never surface.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Prefer work-method kaizen over equipment solutions — find the no-capital improvement first
When developing the plan, give priority to changing the work method over buying equipment. The improvement that requires no capital is the one worth finding first: it is faster, reversible, and forces a real understanding of the process rather than spending the problem away. Equipment solutions take capital that takes years to recover and often leave the underlying method unexamined.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Implementation means involving the people who do the work, not just notifying them
Executing a kaizen requires bringing in all affected team members and departments — explaining why the change is being made, asking for their input, and arranging any retraining — not merely announcing it. The best improvement plan fails if the people doing the work do not understand it or were not part of building it.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Any motion splits into value-added work, incidental work, and waste — and value-added is the smallest share
Every motion in manufacturing decomposes into three parts: value-added work that advances the product, incidental (accompanying) work that is necessary to execute the task but adds no value, and waste that adds cost and nothing else. Observed carefully, the genuinely value-added share is typically small — often under ten percent of the total — with incidental work and waste making up the large majority. Kaizen works from the waste end first, growing the value-added share.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
True efficiency vs. apparent efficiency — demand is the anchor
Apparent efficiency raises output without regard to demand — producing more parts with the same workforce. True efficiency produces the customer-required quantity with fewer labor-hours, materials, or defects, which shows up as lower cost. Making 120 when only 100 are needed is not a gain; it is overproduction. The test of any proposed improvement is whether cost actually falls — if it does not, the efficiency was only apparent.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen
Toyota tracks kaizen skill on a formal ability map — the Kaizen-Man Ability Map (改善マン能力マップ)
Toyota maps kaizen capability on a formal competency instrument organized into four domains — TPS Basic Thinking, Just-in-Time, Improvement of Productivity, and Jidoka. A mature version runs to roughly 384 individually-assessed skills, each scored on a six-level scale (don't know, understand, have experience, can do alone, can teach, can direct) and re-scored every half-year against a target. It reframes kaizen from a handful of tools into a measured, years-long development path — and shows how little of the craft most practitioners have actually seen.
Art Smalley, Art of Lean — artoflean.com/learning/kaizen