Key Takeaways
Audit operations through flow, synchronization, and leveling, not finance alone
Two views of performance. Masaaki Imai argues that companies need to assess both financial results and the work system that produces them. Financial statements are widely audited, but they do not show whether work moves smoothly, whether processes meet customer demand together, or whether production swings create waste. He proposes FSL, meaning flow, synchronization, and leveling, as a way to examine those operating conditions. Imai estimates that only 1 percent of companies have adopted this approach, a judgment rather than a verified global statistic.
Make the work visible. FSL reviews are intended to show executives where operations stall and where improvement is needed, alongside the figures shareholders already receive. Imai’s larger claim is that customer satisfaction and durable financial performance depend on the operating system, not merely on its reported outcomes.
What's compelling is the distinction between outcomes and the machinery that generates them. In complex systems, lagging measures such as profit can conceal fragile processes until a failure becomes expensive. Operational indicators can make emerging problems discussable before they appear in quarterly results. Yet a new audit is not automatically a cure: measures can be gamed, and a smooth-looking process may still produce something customers do not value. FSL is most useful when treated as evidence for inquiry, not a score that replaces judgment. The key governance question is whether directors ask what the numbers reveal about actual work.
Let customer orders pull work instead of letting forecasts push it
Start with actual demand. A push system schedules each process from forecasts, so departments make what their plans prescribe, whether or not the next process needs it. A pull system starts with customer orders and signals upstream processes to replenish what has been used. Kanban, a card or other signal passed between processes, communicates what to make or move. It connects information to material rather than relying on a cascade of separate instructions.
KOA changed its signal. The Japanese electronics maker had accumulated about three months of finished goods while still missing delivery commitments. Its production was driven by forecasts, and sales branches held separate stocks. Under the KOA Production System, responsibility shifted toward the plant, production moved closer to actual orders, and products went more directly to customers. The company reduced handoffs and the delays caused by them.
Pull systems offer a practical answer to a common planning error: treating a prediction as if it were a customer. They also shorten feedback loops, because shortages and quality defects become visible sooner when large buffers no longer conceal them. This resembles demand-driven control in other fields, where a downstream signal regulates upstream activity. The approach does not make forecasting useless. Suppliers still need plans, and highly variable or long-lead-time inputs may require buffers. The useful distinction is between forecasting to prepare capacity and forecasting as permission to produce inventory without a real need.
Trace disruptions through the whole flow, not isolated departments
Follow the work end to end. Flow means that materials, information, and tasks progress through connected processes without unnecessary waiting, detours, or piles of work-in-process. Taiichi Ohno developed Toyota’s approach under constraint: after Japan’s surrender, Toyota’s president challenged the company to catch up with US automakers, despite a smaller market and limited resources. Ohno questioned whether productivity had to mean faster machines. He reorganized work so one operator could tend multiple machines and, later, different processes, with tasks arranged to keep work moving.
A local fix can shift the problem. Design, production, sales, suppliers, and delivery all affect the customer’s experience. If each department optimizes its own output, products can pile up between stages. Imai therefore treats a stalled flow as a visible clue to investigate the process, rather than as a reason to demand more speed from one team.
This systems view connects naturally to bottleneck analysis: improving one station does little if the constraint simply relocates downstream. It also explains why departments can report strong local performance while the customer waits. Flow makes dependencies observable, which is valuable in factories and in service work such as claims processing or software delivery. Still, continuous movement should not become a fetish. Some processes need deliberate review, safety checks, or recovery time. The right question is not whether anything ever pauses, but whether the pause protects value or merely reflects poor coordination.
Level the work before volume swings become inventories and overtime
Smooth the sequence. Synchronization means coordinating the timing and requirements of connected processes. Leveling, or heijunka, means distributing product types, volume, and timing more evenly instead of letting peaks and troughs dictate chaotic work. It does not erase changing demand. It helps an operation absorb that variation with smaller batches and a steadier pace.
Yokomori learned by rearranging the work. The Japanese stairway maker had piles of heavy parts, and operators spent much of their time moving them around. Consultant Kenji Takahashi urged the company to coordinate factory production with the order in which stairs would be assembled in buildings. After adopting more level, connected production, Yokomori reduced the monthly cost of moving materials from several million yen to about one million over two years. It also combined operations that had previously been separated, reducing handling and waiting.
Leveling addresses a basic queueing problem: uneven arrivals create waiting, congestion, and idle periods even when average capacity seems adequate. In operations research, Little’s Law describes the relationship between work-in-process, throughput, and lead time; reducing piles can shorten lead times, but only if the process remains capable of meeting demand. Yokomori’s sequence-based changes show why scheduling and physical layout belong in the same conversation. The limitation is that smoothing cannot make unpredictable demand disappear. Companies need to distinguish manageable variation from genuine shocks, then design flexibility for the latter.
Use standards to expose problems and give workers room to improve
Make the best-known method visible. Standard work is a documented way to perform a task safely and consistently. It is not meant to freeze work forever: a standard gives teams a baseline for noticing abnormal conditions and testing improvements. Imai pairs it with 5S, a workplace practice of removing unnecessary items, arranging what remains, cleaning, maintaining order, and building the discipline to sustain it. Jidoka means designing equipment to stop when work is complete or something abnormal occurs, so defects do not silently travel onward.
Mitsutoshi Sato saw the effect on a Toyota line. By observing machine cycles and operator movement, the team improved the work sequence and equipment conditions. The line’s staffing fell from nine operators to five as its daily capacity rose from a stated 680 pieces to 819. The point is not that fewer workers are always better, but that visible work can reveal capacity hidden by poor design.
Standards are often mistaken for bureaucracy, but here they function as shared experimental controls: without a baseline, teams cannot reliably tell whether a change helped. This connects to scientific practice, where repeatable procedures make variation interpretable. The human element matters just as much. If standards are imposed without worker knowledge, they can become tools of surveillance or intensification rather than learning. Imai’s examples are strongest when operators help identify problems and shape changes. Productivity gains should also be assessed alongside safety, workload, and the quality of the work itself.
Make customer trust an executive operating priority
Governance shapes behavior. Imai argues that leaders often face pressure to protect short-term shareholder expectations, while the work required for customer satisfaction takes sustained attention. He contrasts BP’s response to the 2010 Deepwater Horizon disaster, which initially sought to limit blame and minimize the damage, with Johnson & Johnson’s response after poisoned Tylenol capsules killed consumers in 1982. J&J halted production and advertising, recalled products nationwide, and introduced tamper-resistant packaging.
Turn priorities into operating choices. Imai’s point is not that financial results do not matter. Rather, leaders should pursue them by building operations that reliably serve customers. That requires senior executives to visit the workplace, review conditions directly, and sustain improvement beyond a short campaign. He proposes regular FSL reviews that report operational findings to the CEO, making the quality of work a leadership concern rather than a project delegated to middle managers.
The crisis comparison illustrates how organizational purpose can guide decisions under pressure, when no spreadsheet fully captures public trust or harm. It also shows why customer orientation is not simply a branding statement: it must shape recall decisions, safety systems, and daily production. One dramatic case cannot prove that customer-first governance always maximizes shareholder returns, and the book acknowledges the limits of examples like these. Still, the broader principle is persuasive: durable commercial legitimacy depends on treating customers as people affected by the system, not merely as figures in a forecast.
Treat inventory as a warning light, not a badge of productivity
Buffers can hide causes. Traditional operations often treat large batches and full warehouses as evidence of efficiency. Imai instead sees excess stock as a sign that production may be disconnected from demand, while inventory itself consumes space, money, handling, and time. Taiichi Ohno’s view was that producing more than needed can conceal surplus capacity, defects, and process delays.
The stakes can exceed cost. At Union Carbide’s Bhopal plant, reduced demand for pesticides did not stop production, and unused methyl isocyanate accumulated in storage. A 1984 leak killed thousands and exposed many more people. Imai uses the disaster to show that unnecessary stock can create hazards, not just accounting burdens. He also describes Toyota’s suppliers near its plants performing better during the 1970s oil crises than more distant suppliers less connected to its operating methods.
Inventory reduction can improve cash use and expose operational weaknesses, but the lesson should not be simplified into “zero stock is always safe.” Inventory is also a buffer against supply interruptions, disasters, and long transport times. Resilience engineering asks which failures a buffer protects against and what happens when it is removed. The Bhopal example is especially powerful because the stored material was not merely idle capital; it represented a serious hazard. A sound policy distinguishes avoidable accumulation from deliberate protection, and reviews both the cost of holding stock and the cost of being without it.
Study how users behave, not only what buyers say they want
The user may reveal the real product. Sakae Komiyama developed rotating mirrors partly as a decorative product, but a supermarket buyer later told him they had helped stop shoplifting. That discovery redirected the small company’s attention toward safety and visibility. A bookstore guard then explained where mirrors would improve her view of hidden areas, helping Komy place products around actual work rather than abstract assumptions.
Use insight to improve service. One retailer later reframed the mirrors as tools for noticing customers who needed help, not just watching suspicious visitors. Staff could spot long lines or someone searching for an item. The retailer reported that losses fell by half. Komy’s story illustrates Imai’s broader customer orientation: the people who purchase, install, and use a product may have different needs, and daily observation can reveal uses its maker did not anticipate.
This is a strong example of learning through use rather than relying only on stated preferences. In product design, people often adapt tools to solve problems designers did not foresee; observing those adaptations can expose latent demand. The retailer’s shift from surveillance to assistance also shows that the same technology can embody different organizational values. The result should be interpreted carefully: one company’s report does not establish a universal effect, and customer observation can raise privacy concerns. The useful practice is to ask users what work they are trying to accomplish, then test whether a product genuinely helps.
Analysis
Strategic Kaizen is both an operations manual and an argument about corporate power. Its central move is to relocate strategy from boardroom declarations to the movement of work: orders, materials, information, and decisions must connect across the business. The FSL proposal gives that argument a memorable diagnostic vocabulary, while the cases make it concrete. KOA exposes the absurdity of abundant stock alongside missed deliveries; Yokomori shows that a warehouse may be treating a coordination failure rather than a capacity shortage; Komy demonstrates how attention to actual users can change a product’s purpose.
The book’s strongest insight is that operational design is not a technical concern separate from governance. Forecast-driven production, isolated departments, and inventory buffers embody choices about whose needs count and which failures remain invisible. Financial measures can reward short-term output while concealing long lead times, poor quality, or customer frustration. Regular operational review could broaden accountability, particularly when senior leaders see the workplace directly rather than receiving only polished summaries.
Its limitation is the tendency to present lean operations as nearly universally superior and inventory as primarily waste. The cases support the argument, but they cannot establish that a single operating design suits every industry, supply chain, or risk environment. Low inventory can expose problems, yet it can also increase vulnerability when replenishment fails. Similarly, productivity gains need assessment against employee workload, safety, quality, and resilience, not headcount alone. FSL is most credible as a disciplined way to ask where work stalls and why, not as a universal ranking of companies.
The book also places considerable weight on CEO commitment. That emphasis is justified: improvement programs lose force when leadership treats them as temporary initiatives. But commitment must be institutionalized in incentives, training, cross-functional authority, and candid reporting, or it remains a personal preference that can disappear with a leadership change. The durable lesson is to connect customer outcomes, workplace learning, and financial stewardship through observable processes. Doing so makes operational excellence more than an efficiency campaign: it becomes a way to test whether the organization can keep its promises.
Review Summary
Strategic Kaizen explores operational excellence using Flow Synchronization and Leveling assessment. Readers appreciate its focus on continuous improvement and Toyota's success story. The book emphasizes reducing waste, improving customer satisfaction, and making small, consistent improvements. Some found the content familiar or too manufacturing-focused. It discusses the importance of long-term value creation over short-term goals and suggests reporting operational performance alongside financial results. Overall, readers found it insightful, though some desired more diverse industry examples.
People Also Read
Glossary
Flow, synchronization, and leveling (FSL)
Lean operations assessmentFSL is Imai’s framework for assessing operational performance through three connected concerns: whether work moves through processes, whether separate processes are coordinated, and whether production volume and timing are made more even. The book proposes regular reviews of these conditions as a complement to financial reporting, so leaders can see where operations are interrupted and where improvement is needed.
Kaizen
Continuous practical improvementKaizen means improvement through ongoing efforts involving people throughout an organization. In Imai’s usage, it is broader than isolated improvement events: it is a management approach that maintains current standards while continually raising them. Improvements can be small and low-cost, and depend on observation, participation, problem-solving, and follow-through.
Gemba
The place value is createdGemba is a Japanese term meaning the real place. In management, it refers to the workplace where employees perform the work that creates value for customers. The book argues that managers should visit the gemba to observe actual conditions and real items, rather than depending only on secondhand reports or conference-room discussion.
Muda
Non-value-adding activityMuda is any activity that consumes resources without adding value for which a customer would pay. Examples in production include overproduction, excess inventory, defects, unnecessary motion, processing, waiting, and transport. Imai also uses the term more broadly for anything that interrupts useful flow, and argues that managers should identify and remove it at the workplace.
Mura
Unevenness in operationsMura means irregularity or unevenness in work. In the book, uneven demand, production, or workload disrupts the flow of operations and can create idle periods, overload, and excess inventory. Leveling is presented as a way to reduce such variation by distributing production more evenly across time and processes.
Muri
Overburden or strainMuri refers to strenuous work or overburden placed on people or equipment. The book groups it with waste and operational unevenness because excessive demands can disrupt stable processes and contribute to errors, delays, and deterioration. Lean improvement seeks to design work so that resources are used effectively without requiring unnecessary strain.
Baratsuki
Operational variationBaratsuki is the Japanese term Imai uses for dispersion or variation in operations. Variation in cycle times, quality, output, or workload makes it difficult to sustain a reliable flow. Standard work, synchronized processes, and leveling are among the practices used to reduce unwanted baratsuki and make abnormalities easier to detect.
Heijunka
Production workload levelingHeijunka means leveling production by distributing different products, volumes, and timing more evenly. Instead of making large batches in response to peaks and then leaving capacity idle, a leveled system aims for a steadier sequence that matches customer demand while making effective use of people, equipment, and materials.
Kanban
Signal for replenishmentKanban is a card or other signal used to coordinate the movement or production of items between processes. When a downstream process uses something, the signal tells the preceding process what needs replenishing. In the book’s account of the Toyota Production System, kanban connects information and material in a pull system and helps limit production to actual requirements.
Jidoka
Automatic abnormality stoppingJidoka is the design of equipment to stop when a process is complete or an abnormal condition occurs. This prevents defects from moving unnoticed to the next process and allows workers to attend to other tasks rather than continuously watch a machine. The book treats jidoka as an important condition for stable flow and quality.
Standard work
Documented best-known methodStandard work describes the current best-known way to perform a task, including the work sequence and relevant operating conditions. It gives employees a consistent baseline, helps distinguish normal work from abnormality, and makes results of changes easier to evaluate. In the book, standards are meant to be maintained and improved, not treated as permanent rules.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.