{domain:"www.qualitydigest.com",server:"169.47.211.87"} Skip to main content

User account menu
Main navigation
  • Topics
    • Customer Care
    • FDA Compliance
    • Healthcare
    • Innovation
    • Lean
    • Management
    • Metrology
    • Operations
    • Risk Management
    • Six Sigma
    • Standards
    • Statistics
    • Supply Chain
    • Sustainability
    • Training
  • Videos/Webinars
    • All videos
    • Product Demos
    • Webinars
  • Advertise
    • Advertise
    • Submit B2B Press Release
    • Write for us
  • Metrology Hub
  • Training
  • Subscribe
  • Log in
Mobile Menu
  • Home
  • Topics
    • 3D Metrology-CMSC
    • Customer Care
    • FDA Compliance
    • Healthcare
    • Innovation
    • Lean
    • Management
    • Metrology
    • Operations
    • Risk Management
    • Six Sigma
    • Standards
    • Statistics
    • Supply Chain
    • Sustainability
    • Training
  • Login / Subscribe
  • More...
    • All Features
    • All News
    • All Videos
    • Contact
    • Training

Don’t Design the Experiment Until You Research the Process

Applied research the smart way

Steven Ouellette
Tue, 06/14/2011 - 05:30
  • Comment
  • RSS

Social Sharing block

  • Print
  • Add new comment
Body

Although we may use the define, measure, analyze, improve, control (DMAIC) mnemonic to help guide us through our problem solving, that doesn’t really give us a lot of specific direction (as I bemoan in my Top 10 Stupid Six Sigma Tricks No. 4). Good experimental design technique is critical to being able to turn problems into solutions, and in my experience Black Belts have not been introduced to a good process to do this. If you know someone whose first thought is, “Let’s go collect some data to see what is going on,” then read on to avoid losing millions of dollars in experimental mistakes.

 …

Want to continue?
Log in or create a FREE account.
Enter your username or email address
Enter the password that accompanies your username.
By logging in you agree to receive communication from Quality Digest. Privacy Policy.
Create a FREE account
Forgot My Password

Comments

Submitted by dvanputten on Tue, 06/14/2011 - 11:19

What is you defintion of "data?"

What is you definition of "data?" Does the process of observation result in data?

  • Reply

Submitted by Steven Ouellette on Thu, 06/16/2011 - 13:04

In reply to What is you defintion of "data?" by dvanputten

A very good question!

(Bullets used to separate paragraphs...)

  • This is actually a really good question, and the answer is maybe not obvious.
  • The way I define data is "numbers that are related by a measurement system to an event of interest."
  • So a list of random numbers is not data since it is unrelated to an event.  Importantly, this definition also implies that your measurement system links to the event somehow, highlighting the importance of good measurement system analysis.
  • So, the process of observation can result in data, but without understanding the relationship your observations have back to the property of interest (as determined by your measurement system), observation does not necessarily result in data.
  • Any measurement system (discrete or continuous) needs to be assessed for stability through time (control), agreement between systems (operator/machine etc), and agreement with a standard.
  • Say a process generates discrete data (say a 1-10 rating on surface quality)  You would need to analyze the measurement system that generates that number. (Do the four inspectors using the Mark I Eyeball generating the rating agree with each other?  Do they agree with a standard?  Are these ratings repeatable through time?)
  • I have seen measurement systems that themselves were not much better than random number generators, or whose measurements changed with time.  Those numbers were not data, even though they might have come from multi-million dollar instruments with digital readouts to four decimal places!
  • Oh, as an aside, the relationship that the numbers (data) have with the event of interest as recorded by the measurement system dictates the measurement level the data are (nominal, ordinal, interval, ratio, absolute), which in turn determines what you are allowed to do with the data statistically.   So it is critical that you understand that relationship!

<edited to correct ambiguities>

  • Reply

Submitted by thenson on Wed, 06/22/2011 - 11:19

In reply to What is you defintion of "data?" by dvanputten

Understanding the Process...

 

 

I'm sure that as in everything, the quality of the Six Sigma BB training varies dramatically. I have been to several DOE training classes and many other statistical related classes. But the Six Sigma training I received through the Whirlpool Corporate Training Center was a phenomenal, mind-blowing experience.

 

The basic premise that the entire 5 weeks of training was centered around the following saying, "Practical, Graphical and Analytical".

It is my belief that if the project planning is done properly and at a level of detail befitting a "Black Belt", that many of the problems could be solved by using the "Practical" aspect of the Black Belt approach without spending wasted time with ineffective DOE's. But that depends on the level of the detail done as part of investigation into the process. If done properly, the BB will have identified, not just the inputs, transformations and outputs, but the interactions, interdependencies, controllable variables and the noise variables. If a process mapping approach is used, then the known’s and unknown’s will also be identified. This also includes a detailed investigation into what the perceived problem or project really is. I believe that if this phase is done correctly, the scope of the project or even what problem is being address might change some from the initial starting point.

 

I also believe that another common mistake is that organizations are convinced that a single DOE will provide a magical answer or the absolute perfect process. One of the first things I learned in the Whirlpool training program was that doing a DOE was a process. An iterative process that might only give you a hint of the direction you need to head, and rarely the optimal answer on the first DOE.

Too many times I have seen people quick to run a DOE to solve a problem they didn't even fully understand. Then when the analytical aspect of the DOE did not yield and magical solution, they would become skeptical of DOE's in general.

 

To me, the Black Belt training I received would still be well worth the effort if we had spend almost no time on the Analytical aspect of the training program. The planning, the understanding of the process, the critical thinking involved in a well done thought map has benefited me almost on a daily basis. The statistical and analytical knowledge I gained has been extremely helpful, but the initial aspects of approaching a problem and the planning and process investigation has forever change the way I approach things on a daily basis.

 

I'm not trying to negate the value of the analytical aspect but so many times, the use of the analytical tools only will not of much value without the initial part of the process.

 

thanks,

Terry A. Henson

 

  • Reply

Submitted by Steven Ouellette on Wed, 06/22/2011 - 15:00

In reply to Understanding the Process... by thenson

Necessary, but Sometimes not Sufficient

  • Terry, that should be a really important part of the training - you are absolutely correct, as I think I have written about in a number of other articles.
  • I think you will see as we go forward through this process that what it is consisent with what you have described.
  • The "seven basic tools" by themselves can find huge savings in areas that have not typically been thought of as a process before - support processes, service provision, transactional industries, etc.  In my training I refer to this as not "low-hanging fruit" but "fruit that we are tripping over!"  Now nothing in this process precludes using just those - it is applicable to every investigation.  But I caution you - if you skip any of these steps you are opening yourself up for trouble.  There are a lot of words there, but I am confident that you will agree you probably do at least some of this already no matter how limited in scope the investigation is.  My point is that as a discipline, something like this research process should be used at all times.  Really, it is nothing more than the Scientific Method once again.  And you will see me raise the point (probably in the next article) that DOE (as we commonly refer to it) and "experiment" or "study" are not equal.
  • Also, you will note that the process I present is a PDSA *cycle* - you may have to go through it more than once to acheive your objective.
  • At some point though the seven basic tools are not enough.  Even confirming that a simple process is affected by a two-way interaction is impossible without the use of ANOVA (and damn hard to spot in a column of data or as you run a process).  So for the short-term, those basic graphical and quasi-analytical tools will work, but at some point the company will need more advanced tools (well I suppose one *could* keep messing up your process so it is always straightforward to fix, but hopefully most organizations learn better than that!).
  • Anyway, I think we agree.  I am just intending to give you a discipline that will serve you well for any investigation, whether it is a DOE or not.
  • Let me know if I accomplish that!
  • Reply

Add new comment

Image CAPTCHA
Enter the characters shown in the image.
Please login to comment.
      

© 2025 Quality Digest. Copyright on content held by Quality Digest or by individual authors. Contact Quality Digest for reprint information.
“Quality Digest" is a trademark owned by Quality Circle Institute Inc.

footer
  • Home
  • Print QD: 1995-2008
  • Print QD: 2008-2009
  • Videos
  • Privacy Policy
  • Write for us
footer second menu
  • Subscribe to Quality Digest
  • About Us
  • Contact Us