Six Sigma is a quantitative approach to problem solving - to solve certain types of problems. At the root of Six Sigma is an improvement methodology that can be described by the acronym DMAIC: define, measure, analyze, improve, and control . Those interested in reading up on Six Sigma might consider the book for dummies, which I found fairly succinct. Those wondering what I mean by "certain types of problems" should consider how to apply the approach to their own business circumstances. I don't mean to the general business but specific problems troubling the business. For me, it is quite easy to identify some conceptual design issues, which I will be discussing in this blog.
Long before the math is reached, there is an issue of problem recognition, which occurs at "D" - design. The presumption is that people who enabled, contributed, or caused the problem have the ability to recognize it in a manner that leads to its resolution. If this is true, then I agree the quantitative analysis might provide some useful insights, assuming the problem can be quantified and handled in a quantitative manner. If the assumption is false - and it probably is - then the ensuing calculations would be pointless. I don't believe statisticians necessarily appreciate my observation: just because there is a problem to solve doesn't mean it's the same problem that needs a solution. Consequently, the solution gained might not solve the underlying problem.
Consider an obvious question: "Why aren't people buying our products?" Now, I don't know exactly how a team of analysts would pose this question in a manner that can be addressed quantitatively. However, I want to emphasize that corporate overlords are probably interested in tangible results. As such, there is a limit to the extent to which performance failure can be obscured by the haze of analysis. "We have increased clicks to these buttons by at least 500 percent!" Yet if revenues still aren't being generated by the website, it would seem that the analysts forged a narrative that in reality is faulty: that revenues were being impaired by lack of web traffic to specific links. The question is, why aren't people "buying" the products.
The methodology in Six Sigma is primarily a matter of definition rather than discovery. Six Sigma is a fairly scientific approach: a person discovers by testing whether assertions are correct. I realize that for those without alternatives, such an approach might seem like the only reasonable way. In the case of discovery, the narrative is formed by the client. I notice that more effort is being made for businesses to interact with the client's narrative rather than the one imposed by researchers. However, there are methodological hurdles in terms of dealing with the unstructured nature of client data. I have addressed this issue using a method of codified narrative called BERLIN: Behavioural Event Reconstruction Linguistic Interface for Narratives. Those interested in reading more should search Google. Interestingly, I seem to have gained ownership over the topic.
Sometimes it is not practical to ask clients directly for their perspective. So I just want to mention that for certain businesses, it is necessarily to gain knowledge by inference: scientists might try adjusting the lighting, background music, smell in the isles, attire of sales people, product arrangements, painting of walls, hand soap in washrooms, toilet paper in washrooms, placement of shopping carts, and so forth. This isn't actually an exercise in discovery but rather behavioural modification. Now, a scientific approach to multifarious events seems problematic in that the data is fundamentally non-quantitative. If scientists tried to pose the problem as quantitative anyways, it would be a never-ending process of defining and postulating. I am suggesting that Six Sigma represents a poor tool for inferring relationships extending from routine events.
On the other hand, I created a tool that is specifically designed to deal with multifarious events: the Crosswave Differential Algorithm. (Again check Google for more details.) In this case, no quantities are needed. I am merely pointing out that alternatives exist not just to Six Sigma but the entire rationale behind its methodology. In closing, I find it necessary to caution people about operating a business from a string of assertions potentially far disassociated from reality. I know that the status quo might seem perfectly normal. The entire discourse surrounding decentralization brings to light the problems of central control. However, the fact that an operation might be decentralized doesn't necessarily mean that it is operating in a decentralized manner. Just to confuse the issue, I would even say that a centralized operation does not necessarily have to operate in a centralized manner. Decentralization is premised on the need for increased interaction with the client narrative. An organization hardly comes any closer to that narrative by substituting it - imposing its own.
 Craig Gygi, Bruce Williams, and Neil DeCarlo. Six Sigma for Dummies, 2nd ed. (Hoboken, New Jersey: John Wiley & Sons, Inc., 2012), 44.