<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pyzdek Institute &#187; statistical technique</title>
	<atom:link href="http://www.sixsigmatraining.org/tag/statistical-technique/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sixsigmatraining.org</link>
	<description>Lean Six Sigma Training and Information</description>
	<lastBuildDate>Wed, 08 Feb 2012 18:11:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Jumping to Statistical Conclusions</title>
		<link>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/jumping-to-statistical-conclusions.html?source=rss</link>
		<comments>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/jumping-to-statistical-conclusions.html#comments</comments>
		<pubDate>Tue, 08 Sep 2009 07:00:08 +0000</pubDate>
		<dc:creator>Thomas Pyzdek</dc:creator>
				<category><![CDATA[Six Sigma Tools]]></category>
		<category><![CDATA[Statistical Tools for Six Sigma]]></category>
		<category><![CDATA[assumptions]]></category>
		<category><![CDATA[black belt]]></category>
		<category><![CDATA[bottom line improvement]]></category>
		<category><![CDATA[graphical evaluation]]></category>
		<category><![CDATA[numerical analysis]]></category>
		<category><![CDATA[poor decisions]]></category>
		<category><![CDATA[sales organization]]></category>
		<category><![CDATA[six-sigma]]></category>
		<category><![CDATA[statistical technique]]></category>

		<guid isPermaLink="false">http://www.sixsigmatraining.org/?p=1758</guid>
		<description><![CDATA[Using the Six Sigma approach, the information can be converted to knowledge, the knowledge to action, and the action to an improved bottom line. It's more work than the old standby, the bar chart, but it's worth it.]]></description>
			<content:encoded><![CDATA[<p><em><span style="color: #ff0000;">Have you attributed your results to the right base data?</span></em></p>
<table border="0" cellspacing="0" cellpadding="0" width="488">
<tbody>
<tr align="left" valign="top">
<td width="488" height="4"><img border="0" alt="" width="488" height="1" /></td>
</tr>
<tr align="left" valign="top">
<td width="488">
<table border="0" cellspacing="0" cellpadding="6" width="488">
<tbody>
<tr>
<td>
<p align="left"><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica; font-size: small;">I</span></strong>t may come as a surprise that the biggest challenge facing black belts and master black belts is usually not in selecting the best statistical technique for analyzing a particular data set. Most statistical techniques work fairly well even if the underlying assumptions are not precisely correct. If a black belt supplements the numerical analysis with graphical evaluation, the chance of making grossly erroneous decisions is negligible.</p>
<p align="left">A mistake that is far more serious&#8211;but far more common&#8211;is comparing the results of a study to the wrong base data. These &#8220;apples to oranges&#8221; comparisons often lead to poor decisions and, worse still, to inaccurate beliefs that can derail faith in the Six Sigma approach itself. A recent incident with a client brought this point home for me.</p>
<p align="left">The situation involved a project in the sales organization of a software company. The company had several sales teams and wanted to know if a new approach to closing the sale would improve the rate of closing sales. The company didn&#8217;t have a Six Sigma program, and the project was planned and carried out without black belts. The results were presented to management in a classic form: a bar chart (see Figure 1). The team had declared victory, and management&#8211;convinced by the &#8220;data&#8221;&#8211;prepared to revamp the sales training to incorporate the new approach companywide. All of the leaders looked forward to the bottom-line improvement they&#8217;d see from a 29-percent improvement in the sales closing rate.</p>
<p align="center"><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica;">Figure 1: Sales Closing Rate Improved by New Approach</span></strong></p>
<div>
<table border="0" cellspacing="0" cellpadding="0" width="360">
<tbody>
<tr>
<td><img id="Picture151" src="http://www.sixsigmatraining.org/2009/07/sales-rate-improved-by-new-approach.gif" border="0" alt="" width="360" height="227" /></td>
</tr>
</tbody>
</table>
</div>
<div><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica;"> </span></strong></div>
<p align="left">All of the leaders, that is, except Lorraine. She&#8217;d received green belt training from her previous employer, and she&#8217;d seen enough black belt presentations to know that the analysis of the sales team was seriously flawed. It was undeniable that the project team&#8217;s sales close rate was 2.53 percent higher than the sales close rate for the rest of the sales department during the 16 weeks of the test, and, yes, the 2.53 percent did represent a 29-percent improvement over the 8.83-percent rate for the rest of the team. Despite these &#8220;facts&#8221; and the air of scientific objectivity surrounding the analysis, Lorraine had many unanswered questions. She asked management to delay any decision until she could explore these questions with a Six Sigma consultant. That&#8217;s where things stood when I entered the picture.</p>
<table border="0" cellspacing="4" cellpadding="0" width="214" align="right">
<tbody>
<tr>
<td>
<table style="height: 315px;" border="0" cellspacing="0" cellpadding="0" width="206">
<tbody>
<tr align="left" valign="top">
<td>
<table border="0" cellspacing="0" cellpadding="0" width="206">
<tbody>
<tr align="left" valign="top">
<td height="7"></td>
</tr>
<tr align="left" valign="top">
<td width="206">
<p align="center"><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica;">Table 1: Old vs.<br />
New Closing Rates</span></strong></td>
</tr>
<tr align="left" valign="top">
<td width="206" height="276" align="left" valign="top"><img id="Picture148" src="http://www.sixsigmatraining.org/2009/07/old-vs-new-closing-rates.gif" border="0" alt="" width="206" height="276" /></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p align="left">Lorraine viewed the analysis as important because it would demonstrate that the Six Sigma approach could be applied in this service company, something that skeptical managers didn&#8217;t believe. In a meeting with the sales team leader, I was presented with the data shown in Table 1. As often happens, this summary data was all that was available; for a variety of reasons (but chiefly due to a time constraint) the number of sales calls used to compute these rates could not be obtained.</p>
<p align="left">If you are a black belt or master black belt, or just statistically inclined, please take a couple of minutes before reading the remainder of this column to think about the data and jot down how you&#8217;d proceed from here.</p>
<p align="left">When dealing with the data in Table 1, it&#8217;s tempting to apply a statistical technique such as a paired t-test to it. Using Microsoft Excel, it&#8217;s a simple matter to compute the t-statistic, which is 4.55, a highly significant result. Statistical purists would ask if the data are approximately normal and an endless variety of other technical questions about the data. I would argue, however, that all of this is premature and, ultimately, beside the point. The first order of business is to determine if we are comparing apples to apples.</p>
<p><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica;">Table 2: Apples-to-Apples Comparison</span></strong></p>
<table border="0" cellspacing="0" cellpadding="0" width="429">
<tbody>
<tr>
<td><img id="Picture149" src="http://www.sixsigmatraining.org/2009/07/apples-to-apples-comparison.gif" border="1" alt="" width="427" height="110" /></td>
</tr>
</tbody>
</table>
<p align="left">
<p align="left">
<p align="left">Further discussion revealed that the company had not two but nine sales teams, all of the same size. A further complication was that the teams sold different products. More probing uncovered the fact that four of the eight other teams sold a product mix similar to that of the team using the new closing method. At this point it appeared that, to make an apples-to-apples comparison, you would assess the results of these five teams for the 16-week project. Descriptive statistics are shown in Table 2.</p>
<table border="0" cellspacing="4" cellpadding="0" width="216" align="right">
<tbody>
<tr>
<td>
<table style="height: 119px;" border="0" cellspacing="0" cellpadding="0" width="208">
<tbody>
<tr align="left" valign="top">
<td>
<table border="0" cellspacing="0" cellpadding="0" width="208">
<tbody>
<tr align="left" valign="top">
<td width="175"><strong><span style="font-family: Tahoma,Verdana,Arial,Helvetica;">Table 3: Data Groups</span></strong></td>
<td width="33"><img src="http://www.sixsigmatraining.org/2009/07/data-groups.gif" border="0" alt="" width="33" height="1" /></td>
</tr>
<tr align="left" valign="top">
<td colspan="2" height="6"></td>
</tr>
<tr align="left" valign="top">
<td colspan="2" width="208" height="97" align="left" valign="top"><img id="Picture150" src="http://www.qualitydigest.com/may00/assets/images/pyzdek-fig3.gif" border="1" alt="" width="206" height="95" /></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<p align="left">Further analysis using nonparametric methods indicated that there are three distinct groups in these data (see Table 3).</p>
<p align="left">Table 3 presents a decidedly different picture than was originally given to management. The new closing method now appears to be no better than normal. Still, there are bright spots. Assuming that teams 5 and 8 aren&#8217;t oranges being compared to apples, potential gains should be possible from discovering why team 5 performs under the norm, and why team 8 outperforms the norm. More information might also be obtained by plotting the 16 weeks over time to identify trends and other patterns. Using the Six Sigma approach, the information can be converted to knowledge, the knowledge to action, and the action to an improved bottom line. It&#8217;s more work than the old standby, the bar chart, but it&#8217;s worth it.</p>
<p align="left">The complete data file used in this article is posted at <a href="http://www.pyzdek.com/2000-05.xls"><em> www.pyzdek.com/2000-05.xls</em></a><em> .</em> The challenge is to analyze the data in a number of different ways to determine how the different analyses would affect management decisions. Send your results to me for inclusion in a future column.</p>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/jumping-to-statistical-conclusions.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Thinking Outside the Box</title>
		<link>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/thinking-outside-the-box.html?source=rss</link>
		<comments>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/thinking-outside-the-box.html#comments</comments>
		<pubDate>Sun, 07 Jun 2009 07:54:16 +0000</pubDate>
		<dc:creator>Thomas Pyzdek</dc:creator>
				<category><![CDATA[Six Sigma Tools]]></category>
		<category><![CDATA[Statistical Tools for Six Sigma]]></category>
		<category><![CDATA[assortment]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[choices]]></category>
		<category><![CDATA[control charts]]></category>
		<category><![CDATA[diagonals]]></category>
		<category><![CDATA[dozens]]></category>
		<category><![CDATA[electronics products]]></category>
		<category><![CDATA[figure 1]]></category>
		<category><![CDATA[holes]]></category>
		<category><![CDATA[linear combinations]]></category>
		<category><![CDATA[many things]]></category>
		<category><![CDATA[measurements]]></category>
		<category><![CDATA[microchips]]></category>
		<category><![CDATA[Principal-Components-Analysis]]></category>
		<category><![CDATA[spc]]></category>
		<category><![CDATA[statistical approach]]></category>
		<category><![CDATA[statistical software packages]]></category>
		<category><![CDATA[statistical technique]]></category>
		<category><![CDATA[transistors]]></category>
		<category><![CDATA[variation]]></category>

		<guid isPermaLink="false">http://www.sixsigmatraining.org/?p=1341</guid>
		<description><![CDATA[The &#8220;P&#8221; in SPC stands for process, not product. A common problem with SPC is that the world appears too complicated for a statistical approach to work. In complex electronics products, for example, circuit boards may have thousands of holes and microchips may have millions of transistors. Plotting control charts of each and every dimension [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #ff0000;"><em>The &#8220;P&#8221; in SPC stands for process, not product.</em></span></p>
<p><strong><span style="font-family: Tahoma,Verdana,Helvetica; font-size: small;">A</span></strong> common problem with SPC is that the world appears too complicated for a statistical approach to work. In complex electronics products, for example, circuit boards may have thousands of holes and microchips may have millions of transistors. Plotting control charts of each and every dimension is clearly not feasible. What can be done?</p>
<p style="text-align: left;">To answer this question, consider a simple product: the box in Figure 1. How many things could we measure on this box? It turns out, a great many. Length, width and height are obvious choices. But we could also measure the diagonals on all six sides, interior diagonals front-to-back and back-to-front, linear combinations of these measurements and a great many more. We could conceivably come up with dozens of measurements on this simple box.</p>
<p><a href="http://www.sixsigmatraining.org/images/spc2.gif?source=rss"><img class="float-right" title="Figure 1" src="http://www.sixsigmatraining.org/images/spc2.gif" alt="" width="201" height="175" /></a></p>
</p>
<p>But&#8211;and this is critical&#8211;we don&#8217;t need these measurements to control the box <em>process</em>. The &#8220;P&#8221; in SPC stands for process, not product. When we focus on the product, we lose sight of the fact that we&#8217;re not trying to control the product. Control of the box process may be a great deal more simple than controlling the product. And if we control the process properly, the product will take care of itself.</p>
<p>The statistical technique known as principle components analysis can help us determine just what is important and what is not. Most statistical software packages can perform PCA. To illustrate the approach, I measured an assortment of boxes (see figure 2). The measurements I obtained are shown (in inches) in Table 1.</p>
<p><a href="http://www.sixsigmatraining.org/images/spc3.gif?source=rss"><img alt="" src="http://www.sixsigmatraining.org/images/spc3.gif" title="Figure 2" class="float-right" width="205" height="184" /></a></p>
<p>When these data are crunched through PCA, we find that three principle components explain 99 percent of the variation in the data set: Component No. 1 explains 76.9 percent of the variation, component No. 2 explains 14.1 percent, and component No. 3 explains 8 percent. The PCA clearly shows that these three components are associated with A, B and C respectively. Thus, the &#8220;box process&#8221; can be characterized almost entirely by controlling these three characteristics. If we do that, the other dimensions will be OK, too.</p>
<p>When these data are crunched through PCA, we find that three principle components explain 99 percent of the variation in the data set: Component No. 1 explains 76.9 percent of the variation, component No. 2 explains 14.1 percent, and component No. 3 explains 8 percent. The PCA clearly shows that these three components are associated with A, B and C respectively. Thus, the &#8220;box process&#8221; can be characterized almost entirely by controlling these three characteristics. If we do that, the other dimensions will be OK, too.</p>
<p><a href="http://www.sixsigmatraining.org/images/spc_table1.gif?source=rss"><img alt="" src="http://www.sixsigmatraining.org/images/spc_table1.gif" title="Figure 2" class="float-right" width="420" height="177" /></a></p>
<p>An example of using this approach in the real world involves CNC machining. A defense plant machined parts for use in guided missiles. The parts were extremely complex, with thousands of holes, cutouts, etc. on each. However, when the data were analyzed using PCA, it was determined that four principle components accounted for nearly all of the process variation. Further study showed which measurements were correlated with each principle component.</p>
<p>From this, the engineers determined that, for all the apparent complexity, the machining process was, in fact, quite simple. The four principle components corresponded with the machining center&#8217;s four axes of movement: X, Y and Z movement of the bed, and the rotation of the table on which the parts were mounted. SPC could be accomplished by selecting those features most difficult to position in each axis of movement. Often, a single feature could measure more than one axis; for example, a hole furthest from the &#8220;home&#8221; position in both the X and Y axes. The result: One or two control charts suffice for the control of a process placing thousands of features.</p>
<p>Note that the features selected for SPC may be of little or no importance to the product itself. In fact, some parts were designed with &#8220;process control features&#8221; that were later removed from the part entirely. This makes sense when remembering that P stands for <em>process</em>, not product. If you keep that in mind, the complexity you face might just evaporate before your eyes.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sixsigmatraining.org/statistical-tools-for-six-sigma/thinking-outside-the-box.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

