Imagine this: You are a plant manager at a mid-sized manufacturing firm. You've just finished a three-day executive retreat where the buzzword of the week was "Lean-Agile." You've hired a team of consultants to implement Scrum alongside 100 sticky notes on a board that vaguely resembles a value stream falling gently like the autumn leaves.
Three months later, nothing has changed. In fact, throughput is down. The "sprints" feel like forced marches. The data you need to make decisions still takes two weeks to reach your desk. Your team is frustrated, and the program is quietly abandoned. But hey, that value stream map is now a Visio file, so you can show it to the next round of consultants.
If this sounds familiar, you aren't alone. In fact, you are in the majority. Continuous Improvement programs have a failure rate that would be unacceptable in any other business function. But the reason they fail isn't "lack of management buy-in." It's likely your age of methodology doesn't match the maturity of your information.
The Crisis of Failure in Modern CI
For nearly a century, we have been obsessed with improving production efficiency. From Taylor's scientific management of 1911, where stopwatches were used in time studies, to the automated pipelines of DevOps today, the methodology landscape is crowded. Yet, despite this wealth of knowledge, practitioners are struggling.
Two Concepts That Explain Everything
To understand why CI fails, we must first define two concepts that are rarely discussed in the boardroom but dominate the factory floor: the Iteration Cycle and Information Latency.
1. The Iteration Cycle
Edwards Deming defined CI as the repeated application of the Plan-Do-Study-Act (PDCA) cycle. The Iteration Cycle is the actual block of time it takes for information to travel from the hands-on activity, the physical change in a product, to a change agent who can modify the process. This is the very nature of scientific thinking: trying things and finding out.
2. Information Latency
Information latency is the delay between the occurrence of an event and the availability of that data for decision-making. This is closely tied to Technical Maturity. In a "Dark Factory" where everything is connected via IoT sensors and robotics, latency is near zero. In a traditional job shop where data is recorded on clipboards and entered into Excel once a week, latency is high. The latency is directly related to the technical maturity of the organization. This is evidenced by how CI methodology is formed with the Continuum of Continuous Improvement.
The Core Thesis: The success or failure of a CI program depends on the frequency and length of the iteration cycle, and that cycle is dictated by your firm's information latency. If you pick a methodology designed for low latency, like Scrum, but your firm has high latency, no MES and manual reporting, the program will fail.
The Evolution of Improvement: Era by Era
Era 1: The Birth of Standardization
The First Industrial Revolution changed the world through Standardization and Specialization. Adam Smith's Wealth of Nations (1776) famously described the pin factory, where breaking a task into 18 distinct operations increased productivity by orders of magnitude. Feedback loops could take months or years.
Era 2: The Giants of Quality
This is the era of the "Guru." After WWII, Deming and Juran introduced Statistical Process Control. Six Sigma followed, designed for iteration cycles of 3 to 6 months. The Socio-Technical Exception: Toyota achieved short cycles, hours to days, not through technology, but through visual management: Kanban, Andon, Gemba walks. They beat the technology curve with culture.
Era 3: Software Infiltrates the Shop Floor
Agile and Scrum (2001) moved the iteration cycle to two-week sprints. Many manufacturing firms fail when they try to run two-week sprints in environments where the physical process or information latency requires much longer cycles.
Era 4: Industrial DevOps and Digital Twins
Industry 4.0 uses Digital Twins and Industrial DevOps. In high-tech environments like additive manufacturing, the iteration cycle drops to minutes or hours.
The Future: Hyper-automation
In "Dark Factories," the iteration cycle becomes near zero. AI agents monitor, recommend, and act on physical changes autonomously.
The Diagnostic Framework
There are few practitioners who utilize all that is available in the world of operational excellence. DPS-Lean favors the use of Theory of Constraints, Lean, Six Sigma, and Agile in order to start general and go specific at every engagement. The certification courses likewise teach with these frameworks in mind, ensuring the framework matches the information latency of the firm being analyzed.
The goal is to compress the time between "Problem Occurs" and "Improvement Implemented." Stop chasing the trend. Whether you use a stopwatch from 1911 or a Digital Twin from 2024, information must flow.