Several terrific articles that have appeared recently emphasize the importance and complexity of a key lean practice: standard (or standardized) work, which we’ll call SW. So we decided to bundle them into a broader roundup of key pieces about this key practice.
“Standardized work at Toyota is a framework for kaizen improvements,” says Taichi Ohno in chapter one of The Birth of Lean. Standards matter because they “make abnormalities immediately obvious so that corrective action can be taken.” As Art Byrne explains in a recent Ask Art piece, standards are a baseline for continuous improvement that represent the best known way of working; they are always about growing your people because “establishing standard work and then improving on it is a major part of creating a learning environment where every employee is contributing their ideas and learning new ways every day.”
Without standard work you simply cannot have kaizen, says John Shook in the first of three seminal columns. They are two sides of the same coin, he explains, elaborating that SW without kaizen kills motivation, causes problems to repeat, and stunts initiative; while kaizen without SW leads to chaotic change, lack of PDCA or root cause analysis, and confusion about tangible progress.
Like many key lean fundamentals, standard work exists at the junction of theory and practice, social and technical, tool and principle. Says Shook:
His second piece in this series shares an instructive personal story about working at Toyota that emphasizes the importance of team leader leadership in creating standard work. In this piece Shook also points out the value of extensive practice as a form of developing mastery through the evolution of standard work. And the third contains a great outline of what SW is, reminding us that SW owes a huge debt to the Training Within Industry program.
Like most core lean practices, SW calls for mastery that develops through rigorous, disciplined attention to detail. So it’s key to understand the basic elements of actually creating and using standard work. To get started there are many good resources, such as this Gemba Coach by Ballè noting the core elements (cycle time, work sequence, standard inventory) that are formally needed for SW. This popular Planet Lean article shares a wealth of advice on implementing SW, as does this insightful article from Rene Aernoudts.
Beyond learning the lyrics one must always hear the music that animates SW; as many gemba veterans note, the key to making standards work is a mindful approach to applying them, as noted in this insightful Michael Balle column. “Standards only work to avoid errors and work efficiently if people own them—believe in them, master them—in short, trust them,” he writes, explaining that “standard work’s main purpose is to understand the work much better.” “The relationship between supervisor and worker is key to establishing standard work,” Balle also argues, saying that discovering how to create SW leads to better teams led by better leaders.
It’s important to note what SW is most emphatically NOT, which is a restrictive top-down barrier to learning and improvement. Rather, it is the foundation for what author Takahiro Fujimoto calls an evolutionary learning system. In The Evolution of a Manufacturing System at Toyota, he says:
Unfortunately, SW is all too frequently the culprit when companies apply lean in precisely the wrong way. As Mark Graban’s excellent Lean Post points out, standardization is a countermeasure, never the goal. He and many others have have seen far too many companies that mindlessly “standardize” everything in the name of lean, in the process completely bureaucratizing a powerful practice and muddying the true intent of this method. Little wonder that so many scorn such practices as Taylorism. Yet as Fujimoto notes, empowering workers to take ownership in owning rigorous and specified work procedures is quite the opposite: “We should think of them not as a rejection of Taylorism but as the democratization of Taylor’s principles.”
This view of SW as a social/technical set of practices to engage people, form productive teams, and capture knowledge is why Ohno believed in standards as the basis for kaizen. His very first move when becoming manager of the machining shop at Toyota was to introduce standardized work:
Finally, a great quote from Kaizen Express summing up the purpose of standardized work: “There is no ultimate solution in kaizen. Leaders should always try to respect their team members as humans, to design the work with them, and to continuously revise their standardized work through kaizen at their workplaces.”
Deeper Dive
For more on standard work…
This excellent roundup from Mark Graban cites terrific evidence from a wide range of examples and resources, and shares several key points:
- It’s created by the people who do the work
- It’s not always a detailed procedure
- It’s not restrictive or limiting
- It’s not permanent:
Mark cites the use of checklists in healthcare and beyond as a powerful use of standards, and cites the work of Atul Gawande as evidence; one could do no better than reading his book The Checklist Manifesto, which highlights the power of standard work in health care, aviation, construction, and a wealth of other areas.
Also, props to Michel Baudin for a great overview of the existing material on SW, chock full of links to exhibits and videos, as well as a lengthy and fruitful LinkedIn discussion that he launched.
And finally, chapter 10 of Kiyoshi Suzaki’s The New Manufacturing Challenge shares one of the pithiest summaries of the why and how of standard work to be found anywhere. A great starting point!
Building a Lean Operating and Management System
Gain the in-depth understanding of lean principles, thinking, and practices.