Have you attributed your results to the right base data?
|
||||||||||||||||
loading...
Get the Flash Player to see this player.
Have you attributed your results to the right base data?
|
||||||||||||||||
Who are they and what do they do?
I‘m often asked about the term “black belt” as it relates to six sigma. What, precisely, is a black belt? Where did the term originate? For that matter, where did the term “six sigma” originate? And, while we’re on the subject, what’s a green belt or master black belt?
Let’s start with the term “six sigma.” In a conversation with Ed Bales of Motorola University, I learned that Motorola coined the term in 1986. As those who have worked in quality for a while know, this term has statistical roots in the technique known as process capability analysis. Prior to the Japanese industrial invasion of U.S. markets, quality practitioners were happy with three sigma quality, which translates to about three errors or defects per 1,000 items for processes in a state of statistical control. Motorola discovered that its processes weren’t in statistical control–estimates based on field failure data indicated that Motorola’s processes apparently drifted by an average of 1.5 standard deviations. In a conversation with ex-Motorola trainer Mikel Harry, I learned that he considers the Cpk index–which measures short-term process variability under statistical control–worthless. Harry prefers the Ppk index, which measures actual performance rather than process capability. (Note that many experts, including me, disagree strongly with Harry on this issue.) In any case, before computing expected process failures, Motorola adds this 1.5 standard deviation. Thus, when we hear that a six sigma process will produce 3.4 parts-per-million (PPM) failures, we find that this PPM corresponds to the area in the tail beyond 4.5 standard deviations above the mean for a normal distribution.
Motorola also adopted the terms “black belt” and “green belt.” For my book The Six Sigma Handbook, I did extensive research into what employers expect of people with these titles. Here is a summary of these various responsibilities:
Six sigma technical leaders work to extract actionable knowledge from an organization’s information warehouse. Successful candidates should understand one or more operating systems, spreadsheets, database managers, presentation programs and word processors. As part of their training they will be required to become proficient in the use of one or more advanced statistical analysis software packages.
Although the martial arts terms described above are common, they are by no means universal. Companies and consulting firms often create their own titles to describe the work done by these technical leaders.
For some reason that I can’t fathom, Six Sigma gets dissed not for what it can do, but for what it doesn’t do well. For example, there are many articles that knock Six Sigma because a company that uses the approach sees its stock price decline. Another common knock is that some companies that use Six Sigma are perceived as less innovative, a debatable perception in any event, but why should Six Sigma take the rap for this?
I once had a Black Belt student who had difficulty with the concept of mistake proofing, or poka yoke. When given an assignment to identify the type of mistake proofing exemplified by the cord which keeps the gas cap fastened to the vehicle he just couldn’t see that this was a prevention mechanism. “It doesn’t prevent the person from not putting the gas cap back on.” He argued. “And it doesn’t keep them from over-filling the tank either.” True, I conceded. It also doesn’t prevent bad breath. But it does prevent the person from leaving the gas cap on the pump or the top of the vehicle and driving off without it. That’s what it is supposed to do, and it does it quite well. Six Sigma also has its place, but it’s not the only thing a company needs to do to be successful. That doesn’t make it any less valuable when used properly.
One of my most popular articles is 101 Things a Six Sigma Black Belt Should Know. Of course, the list is primarily a list of technical tools and skills needed, but anyone who has worked as a change agent knows that there’s more to it than that. Soft skills are at least as important, if not more so. Some of the soft skills are people skills, others are intuition about a change project’s chances of success, and still others involve an understanding of the organization. When I teach Six Sigma classes I have several lessons and assignments around these topics. I thought it would be fun to see how long a list of soft skills I could come up with. Even more fun would be to see how many readers of this post could add to the list. So, here we go:
This is all I have time for at the moment. I’m sure there are many other skills not on this list. Can we come up with a full 101 things? Your input is required!
Copyright © 2003
by Thomas Pyzdek, all rights reserved
Resources for Six Sigma |
|
Introduction to Six Sigma |
Six Sigma Projects |
Six Sigma Tools |
Six Sigma Statistics |
Six Sigma Videos (Requires QuickTime) |
Leading Six Sigma |
Healthcare Quality |
Process Excellence Podcasts |
Other Useful LinksGood books on Six Sigma and other topics |
|
|
|