Tag Archives: standard work

Leader Standard Waste: Part One

leader standard wasteThree years ago I wrote a post entitled “The Emperor’s New Huddle Boards,” in which I expressed concern about the trappings of improvement without actual improvement.  Since then, my concern about the application of Leader Standard Work and Gemba Walks has deepened as these potentially valuable practices have too often degenerated into obligatory scripted play acting.

Ten years ago, when I first heard David Mann presenting these concepts, I thought to myself, “Hmm, it’s about time that someone gives thought to the best use of manager’s time in support of kaizen.”

Most managers, in my opinion, needed some guidelines in this regard.  A hesitancy to go to the floor for direct observation was a pervasive manager shortfall.  Many persons who have viewed GBMP’s video, Toast Kaizen, may not know that in fact, its genesis was in trying to persuade senior managers to get out of their offices and go to the floor to observe.  So the idea of establishing a standard that included visits to the Gemba was appealing to me.

Unfortunately, good ideas are sometimes unintentionally abstracted to the point that they become pointless.   For each of the three parts of David Mann’s model, I have observed a proliferation of shortcomings that invalidate the intended Lean management system.   For the next three weeks, I’ll cover these one-by-one.

Today it’s Visual Controls:

Call me old school, but I grew up in a factory where visual controls mainly meant building visual information directly into the work.  For example:

  • A standardized work chart posted at the workstation so an observer could compare the actual process with the standard.
  • A production-activity log in the production cell, updated on each work cycle with particular emphasis on problems that occurred so that problems could be fixed instantly.
  • A visualization of standard work in process, for example, a chute that held only four pieces – no more or less – to clarify the balance of operations.
  • An Andon that, if flashing, signaled an immediate need for production support.

When I was a kid, the opportunities like these to build information directly into the process in a low-tech way seemed endless.  They provided excellent opportunities for workers to share information about their work, and a manager who understood these visual devices could understand the health of the process at glance.

Today I see far less visual information at the point of use.   It’s been replaced by ubiquitous huddle boards and kiosks and video displays, often situated on a wall far from the actual work.  The ideal of “frequent focus on the process” has been become an infrequent focus on visual displays updated once per day just before the huddle meeting.  The ability to visually compare actual to standard has been lost.  Recently, in fact, I visited an organization that proudly announced they were replacing all manual huddle boards with digital displays that could be viewed remotely.  I’m sorry if this seems harsh, but when these types of standalone visual devices become the sole standard for visual controls, managers learn little or nothing about the Gemba.  “Grasping the current condition” is replaced by counting the red and green dots.  One manager announced to me that he could tell the condition of the factory merely by glancing at the huddle board for several seconds.  “No,” I responded, “you can only tell the condition of the huddle board.”

One final rhetorical question regarding the red and green dots:  In an environment where reviewing a huddle board is understood to be going to the Gemba, how many red dots would you expect to see?   A colleague related to me a comment he received from a shop floor employee.  “Have you heard of the color watermelon?” the employee asked, and then answered.  “We have watermelon dots on our huddle board.  They’re green on the outside, but red on the inside.”

In fact, I do think huddle boards and kiosk displays can be an impactful part of a visual factory or office; but they are only a piece, and probably not the most important piece.  And as stand-alones, they create an additive activity that makes management’s visits to the floor a standardized waste of time and an insult to the front line.

O.L.D. 

PS Did this get you hot under the collar?  Then please add a comment.  And watch for the continuation of this post next week when I’ll be sharing some concerns about the second part of the Lean Management System: Accountability.

BTW For a terrific story from one senior leader who understands management’s role to create a transparent workplace that incorporates visualization of the work, I recommend Jim Lancaster’s The Work of Management.  Or better still, sign up for our 14th Annual Northeast Lean Conference to be held in Providence on October 10-11, 2018 and hear Jim Lancaster’s Lantech story directly from him at his October 11 conference keynote.

 

Mistake-Proofing Mistakes

mistakeproofingThere is a popular lore provided by Shigeo Shingo, that the original name for mistake-proofing (Poka-Yoke) was “fool-proofing” (Baka-Yoke). Shingo chided managers at Panasonic for using the latter term, as it was disrespectful to workers, essentially calling them fools. Shingo substituted the word “mistake” for “fool”, because, as he aptly noted, making mistakes is part of humanity. “Mistakes are inevitable,” he said, “but the defects that arise from them are not.”

Notwithstanding Mr. Shingo’s admonitions, however, I still hear the term “fool-proofing” used regularly, and occasionally with a little more venom, “idiot-proofing.”   No doubt, these derogatory terms, along with others like ‘screw-up’ and its less gentile derivatives, have given a bad name to one of the most energizing, empowering and creative tools from the TPS toolbox. Many organizations never even get out the blocks with this technique because of an overt insulting, blame environment. Who wants to report a mistake, when the reward is blame and ridicule? Like Mr. T, managers tend to blurt out the wrong words when mistakes occur. Bad habits die hard.

But even for more enlightened managers there are still some common hurdles to creating a really powerful Poka-Yoke system. A few weeks ago I gave a short Webinar for AME on Poka-Yoke, and was asked this question by a viewer:

“How do I ensure the effectiveness in use of the Poka-Yoke device? People usually don’t want to continue using it.”

Here, with a few embellishments, was my response:

“The general answer to this question from today’s Webinar is that if people don’t find a particular tool purposeful, they don’t use it.  More specifically for poka-yoke, there are seven reasons that the tool is not seen to purposeful by team members:

  1. Sometimes to assure quality, an additional step is added to the operation to prevent or detect the defect, but this step is not considered in the standardized work, i.e., no additional time is allowed.   If the device or method requires an extra step that takes more time (e.g. use of a check list or matching parts to a template) then employees will feel rushed and pressured to choose between rate and quality.
  2. A corollary to the lack of standardized work is the lack of communication to team members, team leaders and managers. An undocumented and untrained standard is not a standard.
  3. If the device or method causes strain to the employee it won’t last. Substituting Muri for Muda is not a good trade off.
  4. For detect-type poka-yoke devices (i.e., a defect is created, but is detected before it can pass to the next operation), the concept involves swarming the defect when it’s trapped in order to understand its root cause. I see many cases where defects are trapped, but there is no follow up. Defects pile up, or they are picked up occasionally by engineering or quality, and no feedback goes back to the production line.  When problems don’t get fixed, this promotes cynicism.  It’s not poka-yoke, just a scrap sorter.
  5. Sometimes, as suggested in the question above, a device is put in place, but the defect persists. This could mean the device isn’t used by the team member, but it can also mean the device just doesn’t work.  More PCDA is needed.   If the device doesn’t work, team members will be the first to know.   Telling them to use something that doesn’t work is disrespectful and disengaging.
  6. The term Poka-Yoke is used too broadly to describe countermeasures that have nothing to do with human error, but relate more to providing proper tooling and fixturing to team members. For example, if a particular job requires super human sensor capability to complete (more Muri), creating fixturing to make the job doable is not a Poka-Yoke solution.   My father, who was a machinist by trade and an artist by avocation, could draw a straight line freehand around an entire room. Most of the rest of us would want a straight edge and a level to complete that task.   The point is when we refer to such countermeasures as “mistake-proofing”, we’re once again disrespecting team members.
  7. Most importantly, if the employee who uses the device is not included in the solution, there is typically little commitment to use it, especially if any of points 1 through 6 apply.

That’s the long-winded answer to the short question.  The short answer to that question is that the “technical” portion of poka-yoke doesn’t work if it is not grounded by a quality culture.”

Perhaps you can think of some other common mistake-proofing mistakes to share with our readers. Please let me hear from you.

O.L.D.

By the way, a few years ago, GBMP made a Lean Training DVD about poka-yoke called “Achieving Zero Defects By Respecting Human Nature“. If you’d like to learn more about poka-yoke and how to apply it in your organization, check it out here where you can read about it, view a clip from the video and purchase it if you’d like.

Senior Moments

sr momentsI was speaking last week with, Jen, a senior manager at a large manufacturer, and she commented to me, “I know it’s important for me to get to the floor, but the time involved for me and my staff to regularly visit two dozen different departments makes this seem like an impossible task.”   She was alluding to the scheduled Gemba walks, which were a component of her and her reports manager standard work.

“I understand the challenge, “ I responded, having faced that myself in my last job. I continued, “As a senior manager it’s important for you to be present both to observe, and also to show your commitment to improvement. Spend whatever time you can, but make sure you use the time well.”

Sometimes I worry about the scripted Gemba walks. Even with the script, they often look like a management posse. And one thoughtless comment or even a thoughtless gesture by the senior visitors can create exactly the opposite effect of what is intended. In fact, managers can make a very positive impact on employee engagement in just moments. It’s the quality of the interaction not the duration that’s telling. About ten years ago, GBMP produced a DVD, Moments of Truth, to demonstrate how short encounters, either deliberate or inadvertent, between managers and employees, can have a powerful impact. A short clip from that video, starring GBMP staff members, demonstrates (with a little humor of course) how important a single moment can be.

Of course, the moments of truth could just as well be positive. An employee at a large insurance company related to me recently that, after a short time on the job, he found a note on his desk from a senior vice president whom he’d never met, welcoming him and stating “I’m hearing from your manager that you’re already making terrific contributions to our improvement program. Thanks.” That note set the tone for employee’s career. It didn’t require a structured Gemba walk and probably took about 10 seconds to write — literally moments. But it showed commitment from the highest level of the organization, both to the new employee and to his direct supervisor.

I related that story to Jen and she smiled. “I can think of a few of those moments, both good and bad, that I had when I was on the front line.”

How about you? Are you watching for those moments of truth?   Gemba walks are important, but a manager’s impact can be expressed in seconds.   Please share a story about your “moments of truth”.

O.L.D.

PS Hope to see you at the International Shingo Conference in Provo, Utah next week.

PPS And don’t miss our next Shingo Institute courses (DISCOVER Excellence followed by Continuous IMPROVEMENT – attend one or both, it’s up to you) coming up in the week of May 11 at Vibco, Inc., in Richmond, Rhode Island. Register online here.

BTW: The GBMP lean training DVD Moments of Truth can be purchased at www.shopgbmp.org. Use code “MOT20” by May 8, 2015 to get 20% of the regular price.