Foundations for smart standards
Standardization is a constant challenge in many organizations. Although creating standards is a relatively simple step, the real difficulty lies in ensuring that they are followed consistently, day after day, in different contexts and under pressure. The big problem is not having standardization, but rather getting it to become part of the routine without turning into useless bureaucracy – something that exists only on paper but is not actually applied.
This challenge applies to a wide range of sectors, from hospitals to factories, from software teams to service operations. The gap between what is established as the standard and what is actually carried out largely explains the hidden costs in quality, safety and productivity. The root cause of this problem lies in the way we approach standardization and the kind of effort needed to implement it effectively.
As James Womack observes in an article published in Planet Lean, ideas that do not require deliberate practice spread quickly; those that demand changes in beliefs, routines and systems advance slowly — as is the case with process standardization. The solution is to make the right thing easier to do, as well as visible and understandable in the gemba. The “placebo” is treating it as an abstract concept.
Womack also highlights that, without the support of a robust management system, improvement gains can be unsustainable. He emphasizes that true transformation requires profound changes in the way managers operate, moving from a command-and-control stance to an approach of coaching and removing obstacles. Therefore, effective standardization goes beyond simply implementing tools; it requires a cultural and structural change that allows processes to be sustained and to evolve continuously. (Planet Lean).
History illustrates this issue in various fields. In medicine, Joseph Lister (1827-1912) pioneered antisepsis in 1867, establishing simple routines, such as preparing hands and instruments, which drastically reduced surgical infections. However, this adoption was slow, depending on recurring collective practice to become part of a true “operational culture”.
Surprisingly, the same challenges faced by Lister and his followers continue to affect us today. Currently, the World Health Organization (WHO) estimates that between 7 and 15 infections occur for every 100 hospitalized patients, with high mortality rates. This happens even though there are proven strategies to reduce these infections, such as “multimodal” hygiene, which involves more rigorous prevention practices (https://tinyurl.com/mkxht7vb). Similarly, in the United States, the Centers for Disease Control and Prevention (CDC) notes uneven progress in the adoption of these practices, highlighting that local adherence is a critical factor for success (https://tinyurl.com/32mp56f8).
However, this paradox goes far beyond health care. In manufacturing, machine setups follow standards to minimize interruptions in the production flow, but they often fail if the work environment does not facilitate quick access to tools or if training does not take into account individual differences between operators. In this context, the secret to success lies in creating conditions that make these standards intuitive and visible, such as clear operating rhythms and organized inventories, ensuring that standardization integrates naturally into daily work instead of becoming an additional barrier.
In software development, processes such as code reviews are essential quality standards. However, adherence to these practices can decline if tools do not automate checks or if feedback is slow. Companies such as Google use “prompt engineering” in tools such as GitHub Copilot to make the correct process more automatic (as in unit tests), increasing productivity by up to 20%, according to internal reports and surveys by Stack Overflow. Without these tools, bugs that are “invisible” in the short term can generate high costs in the long term.
In services such as call centers or retail customer service, interactions with customers follow scripts to ensure consistency in relationships. However, without continuous reinforcement through visual reminders or hands-on training, this can become just a bureaucratic formality, with no real impact on the customer experience.
Zappos, for example, standardizes so-called "wow moments" to promote employee autonomy, but reinforces this practice with metrics at the point of execution, which resulted in a 15% reduction in churn (customer cancellation rate), according to Harvard Business Review (https://hbr.org). Likewise, in Amazon's logistics, picking standards are crucial to avoid errors, but this effectiveness depends on ergonomic layouts and automation through scans, ensuring consistent adherence to processes.
When discussing standardization, it is important to understand the critical difference between work standards and standardized work. Work standards are simple instructions that guide the execution of tasks, while standardized work is a complete system, involving a clear rhythm, a defined sequence and continuous training in the gemba. This approach underpins effective strategies, such as the WHO's multimodal strategy (https://tinyurl.com/fnnt2tys), which seeks to ensure adherence and effectiveness through continuous monitoring and feedback practices.
In practice, standardized work fails when its benefits are not visible, when there is friction, generic instructions, threats to identity or late feedback. To overcome these challenges, it is necessary to apply good “lean engineering”, with well-structured work design, teaching based on techniques such as Training Within Industry (TWI), which involves breaking down tasks, demonstration and practice, as well as solid governance to ensure the system's effectiveness over time.
This path is well known, but it requires discipline to be followed effectively. Below, we present four key points for achieving this goal:
Define the “essence”: identify what is essential to ensure quality and safety, and focus on what must be standardized for those who perform the tasks. For example, in a food factory, ensuring that those who do the work follow hygiene and temperature control procedures is essential and must be standardized.
Design the “how”: create the environment and the tools that favor natural adherence to processes, eliminating unnecessary friction. For example, implementing automation to validate data entries automatically, positioning hygiene dispensers intuitively in health care settings, or optimizing factory layouts to ensure that tools and materials flow logically, minimizing the temptation to take shortcuts.
Prioritize learning: teach in a structured way, breaking tasks down into clear steps, highlighting the key points and the reasoning behind each action. Demonstrate in practice how each step should be performed, allowing supervised repetitions until execution becomes natural and fluid, following approaches such as TWI.
Lead the lean way: finally, lead at the pace of daily work, establishing brief routines in the workplace to identify and remove barriers in real time, reinforcing positive behaviors with immediate feedback and using visual checks, such as metrics boards or reminders at the point of execution, to maintain visibility and collective accountability.
When implemented consistently, standardization goes beyond individual action, becoming a collective behavior and taking root in the organization's culture. For example, quick setups in manufacturing not only raise operational efficiency, reducing downtime and waste, but also foster a continuous improvement mindset among teams. Similarly, smooth code reviews in software development minimize accumulated technical debt, promoting more robust and collaborative code throughout product life cycles.
Although the case of hand hygiene in health care serves as a classic example of invisible prevention, the same principles apply universally, whether in the precise preparation of machines to avoid mechanical failures, in rigorous code reviews to catch errors early, or in standardized interactions with customers in services that build trust and consistency in the user experience.
At the heart of this issue, sustainable adherence to standards depends much more on intelligent design than on isolated persuasion efforts, because it is the redesign of the work environment that makes the desired behavior the path of least resistance. “Slow” ideas, such as those of a preventive and transformative nature, gain real traction only when the workflow is restructured to make the right thing intuitive and the wrong thing unlikely, eliminating subtle barriers that sabotage daily execution.
The practical invitation is straightforward: select a critical process in the operation, identify the essential elements, redesign the point of execution for smoothness, teach with depth and method, and establish regular and visible checks. In this way, you will not only convert theoretical knowledge into tangible practice, but also cultivate an organizational resilience that can perpetuate excellence over time.
Effective standardization goes beyond simply having established processes; it is about integrating them so that they become part of the organization's daily life. True transformation comes when standards become part of the culture, sustained by a robust management system and a continuous approach to learning, feedback and improvement. By adopting a consistent and focused standardization strategy, organizations not only ensure efficiency and quality, but also promote an agile and collaborative work environment, capable of adapting and evolving continuously.
