Recently, I had the same discussion with two completely different clients: what does standardization actually mean? Those conversations revealed just how many different views exist around this concept. They also exposed a common pattern — standardization is sometimes misplaced, harmonization inappropriate, and actual improvement completely absent. Because organizations often lack a clear understanding of these concepts, they also lack a clear strategy and roadmap for improving their business results and processes. That makes this a good moment to share my views on standardization, harmonization, and improvement — and how they truly differ.
What is Standardization?
As possibly known, in Lean the standard is often defined as “the best known possible way, at this moment, to perform the work to deliver the targeted end result”.
Setting the Initial Standard
In practice, setting the initial standard means observing the various ways work is currently performed for a given product or process and selecting the most effective and efficient method — one that respects relevant values and principles. In some cases, this involves cherry-picking the best elements per step from different observed approaches and combining them into a single preferred method.
This first step, collectively determining the initial standard, marks the beginning of standardization, not the end.
Eliminating Deviations from Standard: the Essence of Standardization
Once you define a standard, you will inevitably observe deviations from it. Late materials, poor-quality inputs, missing information, absenteeism, machine breakdowns — all of these are demonstrable causes that prevent the process from following the known standard. In many cases, these deviations outnumber the instances that actually follow the standard. When that happens, people start treating the deviations as “normal.” This is a critical mistake: never confuse “normal” with “standard.”
Never confuse “normal” with “standard.”
I consider the elimination of all deviations with apparent and demonstrable causes to be the true essence of standardization. In quality management terms, this equates to stabilizing the process and bringing it under control. Interestingly enough, this is not the same as actually improving the process (more on this later). If, however, the number of deviations largely outnumbers the number of cases that follow the standard, standardization will definitely positively impact the overall results coming from the process. This is due to the fact that in such a situation the standard is barely visible in the results. The standard is in fact then often wrongly seen as “the exception to the rule”.
The Pitfall of Misplaced Standardization
A common trap organizations fall into is directing their energy toward accurately documenting how to handle deviations in detail. While this may be necessary from an operational or quality handbook perspective, it is a misplaced use of the word standardization. From a true standardization standpoint, deviations should not be documented — they should be eradicated.
Complaint handling provides a telling example: organizations often invest more effort in resolving complaints quickly and correctly than in eliminating the root cause of the complaints themselves. Peter F. Drucker would likely call this being efficiently ineffective: “There is nothing so useless as doing efficiently that which should not be done at all.”
What is Harmonization?
Harmonization addresses a different challenge: what happens when multiple variants of a standard exist? Understanding when harmonization is appropriate — and when it is not — is essential.
Variants Driven by External Requirements
Sometimes a process deviates from the standard because of differing external requirements. Customer A may require different things than Customer B. For example, Toyota has different packaging, labeling, and loading requirements compared to Renault. These differing customer requirements create distinct variants of the standard. Although the process name may be the same (e.g., “loading”), each variant is effectively a different standard in its own right — and each one needs to be standardized individually.
Harmonizing variants that stem from external or customer requirements can be highly inappropriate. This type of harmonization demands careful consultation between customer and supplier and must deliver a clear win-win for both parties. Imposed, top-down harmonization — sometimes even labeled as “standardization” — without awareness of legitimately required differences leads to massive organizational frustration.
Variants Driven by Internal Differences
In many cases, however, variants exist purely because of internal differences: personal preferences, unclear or ambiguous internal rules, differences between teams, sites or countries, or historical origins such as mergers and acquisitions. Merging these internally driven variants into one preferred variant is what I call harmonizing — and this is the appropriate form of harmonization.
This type of harmonization is often part of setting the initial standard. In that sense, defining the initial standard involves two activities: harmonizing the internal variants that exist for a process, and clearly identifying potential deviations caused by demonstrable external factors.
What is Improvement Actuallly?
Many organizations treat every initiative as an “improvement” initiative. But in quality management theory, standardization is not improvement — it is stabilization: reducing variation by eliminating assignable causes. True improvement is something fundamentally different.
Standardization is not improvement: it is stabilization.
From Stabilization to Improvement
Standardization produces a consistent, predictable process with repeatable and reliable results. But market demands may force you to take that stable process to the next level. Simply reducing the remaining deviations from the standard will not be enough. At that point, you need to change the standard itself — the until-then best known way to perform the work. Changing the standard itself is what quality management theory defines as improvement.
Why You Need a Standard Before You Can Improve
To genuinely improve, you first need a standardized — and therefore stabilized — process. Only then do you have a reliable basis to improve upon. And only after you standardize the new method can you evaluate whether it delivers the results you aimed for. A non-standardized process produces no reliable or repeatable results and therefore cannot serve as a basis for comparison.
Organizations Need a Clear Improvement Strategy
Without a fundamental understanding of standardization, harmonization, and improvement, organizations cannot build a clear-cut strategy and roadmap for continual improvement. (And from the above, it should be clear why continual improvement is a more accurate term than continuous improvement.)
Too often, what organizations call their “improvement program” turns out to be a hodgepodge of correct but also misplaced standardization, appropriate and inappropriate harmonization, and baseless improvement efforts. The result is a scattershot approach — many seemingly incoherent and unproductive activities running in parallel.
Without theory, no effective practice. Without thinking, no effective doing. There are seemingly more reasons why the Toyota Production System is sometimes referred to as the Thinking Production System.
