Tuesday, June 5, 2007

Six Sigma not for R&D

Have you read the Business Week article recently on 3M's implementation of Six Sigma? This is a good example of how enterprise wide quality changes are not always good for the enterprise. Just like many quality initiatives, you must use the right tool for the right job. Six Sigma is beneficial when a product is already created, and you want to become more cost efficient. DMAIC, Six Sigma's problem solving tool, is best used when you have something to improve. It provides a structure to identify where changes will provide the greatest cost benefit. It starts with the theory of improvement.

But innovation is about creating something new that doesn't yet exist. R&D depends on mistakes, failures and ah ha moments. There are many famous every day items that were mistakes. I once worked at a company whose researchers were investigating the properties of the various creatures of the sea to see what benefits these properties could have. I was fascinated. Was the iPod really the solution to a problem of cost efficiency?

On the other hand, many companies have failed when the entire company continues run as if it is only an R&D shop, even though it is now in revenue production. Once you have brought something to market, you have an obligation to be as efficient and effective as possible in your production.

It's possible that in an industry such as banking or insurance, you could use Six Sigma throughout, because people aren't really that comfortable with radical changes in the way their money is managed.

But in any company that wants to experience growth through new ideas, one segment of the company must be left to develop utilizing a different methodology. It will be interesting to see if 3M maintains some of the process discipline of Six Sigma while re-introducing 'growth and innovation' into the company.

Monday, June 4, 2007

Thoughts on Quality Software

Software Quality and Quality Software aren't always the same thing. I wish it were true, but it's not. The purpose of this blog is to examine this difference and discuss what it will take for software, which has become so embedded in our world, to become quality software.