What is the difference between standard work and procedures?
Dear Gemba Coach,
What is the difference between standard work and procedures?
(During The Way to Lean, a free webinar on the “lean trilogy” approach to deeply understanding and applying kaizen daily, we received the above question plus dozens more that we didn't answer before running out of time. Presenter Michael Ballé will answer them, including the response below, in the Gemba Coach column he writes for LEI. -Ed.)
Same – but different. This is one of these tricky areas where both things might look the same but their intent (and therefore use) is really different. Let’s see if we can untangle this.
Have you ever sat on an airplane next to an emergency exit? The flight attendant probably came to you to ask you whether you speak English and then:
- Place your belongings in the overhead compartment for take-off and landing.
- Read the safety brochure to familiarize yourself with the operation of the emergency door.
- In case of an emergency wait for airline staff’s direction and then turn lever one and lever two to open the door.
- Do NOT do so unless expressly directed by airline staff.
- Read the safety card again to see how the doors open.
Or something similar to that. If you’re anything like me at this point, you’re thinking that thankfully chances of having to open this door are ridiculously small because if you ever had to do it, you’d be in bad, bad trouble. The procedure is perfectly clear but not much use in a real situation.
To my mind, the main difference between a procedure and standard work is:
- A procedure tells you what to do in a given situation.
- Standard work tells you what you need to know to get the job done right first time.
Three Elements of Standard work
Procedures are written by experts. They assume that if you just would stop thinking about it and follow the procedure step by step, the right process will guarantee the right outcome. This is of course much better than no procedure at all, but not much help when you hit a snag.
What about standard work? In his book on The Toyota Production System, Ohno describes standard work as a special kind of procedure that lists three core elements which had been used by Toyota since before WWII in loom manufacturing:
Ohno is assuming many things, such as the fact that all parts are assumed good and so on, but we can see that this differs from a procedure (as in “a series of actions conducted in a certain order or manner”) in important ways:
First, there’s a criteria for success: the work must be done correctly in a certain amount of time. This is very important because it states the difference between doing a good job or a bad job (rework, for instance, will lengthen the Cycle time and be revealed).
Second it focuses on work sequence, not actions or activities. This is not nitpicking on words, but very specific. “Open the door” is a high-level instruction typically found in a procedure, whereas “turn lever A from clockwise with left hand and then turn lever B counter-clockwise with right hand” would be closer to standard work. Standard work is about the work itself.
Third, standard work specifies what you need at hand to get the job done (and what you don’t need in the case of having more inventory than immediately needed), which looks to the conditions you need to be in in order to do the work properly.
Focusing on the Outcome
To look at standard work in a broader sense we need to place it back in the context of just-in-time and jidoka. In order to keep up with takt time, the work must take place within a target Cycle time and with minimum inventory, and in order to build in quality:
- The necessary conditions to produce good quality must be known and controlled in the process
- Clear judgment criteria must allow employees to make judgments about their own quality with confidence.
Standard work should cover:
- The job’s objectives from customers’ expectations perspective.
- The break-down into work elements, in manageable steps.
- The necessary conditions in terms of components, equipment, tools, capability and other inputs.
- Constant clarification of judgment criteria to make confident decisions about work completion (probably involving documentation and training by supervisor).
- On-going confirmation, instruction, and improvement.
Standard work goes beyond procedures in terms of focusing on the outcome of the job, the impact doing the job this way or that way has on safety, quality, cycle-time and lead-time and is expressed at a much greater level of detail about work, to the point where it touches the basic skills needed to carry out successfully the work at each step of the job.
Break the Standard
In practice, standard work starts where the procedure ends. Standard work is the result of the effort the supervisor puts into mastering the procedure (usually written by engineering or another expert department) and turning it into specific work habits to do the job right and on time confidently, every time. Beyond standard work, standardized work actually describes the very steps (eye movement, hand movement, feet movement) one can follow to do the job with the minimum waste.
The supervisor’s aim is to have eight hours of standardized work for every employee in her team. The team leader’s aim is to “break” the standard by suggesting with team members new, better ways of doing the job – and hence kaizen. Without standard work, it’s very difficult to see what to kaizen. Without kaizen, standard work soon falls into disuses and reverts to … procedure.
In the end, the difference lies in the intention of the procedure. Lean’s arrow is clear and simple: is management’s intent to make work easier for employees so they can succeed at their jobs and for customers? Or is it about bringing back control of what people do towards more management input and decisions? Are we getting closer to the final process of work and customer satisfaction? Or back to management meetings and action plans. Standard work’s main purpose is to turn procedures into actionable knowledge to make it easier for each employee to succeed for their customers and in their job.
Lean Lessons from Cobra Kai(zen) and the Karate Kid
The unexpected wake-up call of the modest perfection of the original Karate Kid movie was that we need to move beyond defending this or that method of work and look to highlight opportunities of improving things beyond monetization, says Michael Balle in this reflection on the meaning of this classic movie.
How Using Kanban Builds Trust
Kanban functions as a trust machine because everyone using it must understand what they have to do and why, says Michael Balle: "Our purpose here is to share our ideas on what we believe is important in lean thinking."
The Sanity of Just-in-Time
Path dependence is the worst enemy of smart resolution, argue the authors, who suggest greater "frame control" with enabling tools such as just-in-time to respect people on the frontline and respect the facts they share about what is happening to them. "Mastering the path as opposed to being led by it, means looking up frequently to reevaluate both destination and way as new information comes to light."