- Adversaries that need to be outwitted or strong-armed.
- Dupes to be tricked into accepting something that they shouldn’t.
- Interlopers who try to interfere with the company’s business.
- Unreasonable, unknowable strangers (usually Japanese customers).
Monday, August 15, 2011
The Customer is Calling
Tuesday, July 26, 2011
Lean Six Sigma Revisited Part 2
This post is the second part of a two part series about revisiting lean manufacturing and six sigma in the 21st century. Before reading this post, I encourage you to read the post immediately below which is part one in the series. In this post I will discuss six sigma and my recommendations for management.
Six Sigma
Six Sigma™ as a brand is simply the repackaging of several statistical tools that have been developed over decades; the only difference being the sequence with which they are deployed. The marketing of six sigma over the past fifteen years has been phenomenal. Huge companies like GE and Motorola trumpeted their success with six sigma and the business world scrambled for it. Books were written by the truckload, consultants hired and people trained by the boatload and a huge revolution in improvement was started. At least that's the story that most people want to believe and most consultants and authors sell. There are several problems with this story; I'll highlight two big ones: the deployment and the results.
Deployment
Six sigma is typically deployed in a company in the following way:
l Hire a consultant to do training
l Train people as follows:
n Upper management - introduction only, maybe two hours.
n Middle management - Champion training, maybe four hours.
n Master Black Belts/Black Belts (MMBs/BBs) - full-blown 6+ weeks of training in all of the details of six sigma, including leading projects and mentoring other "belts".
n Green Belts (GBs) - 2-4 weeks of training, not as involved as MBB/BB but still pretty deep.
n White Belts/Yellow Belts - some exposure, maybe the same as introduction or Champion training but meant for the remainder of the workforce.
l Define some projects (usually done in parallel with the training so that the trainees have a "real-world" application during their learning)
l Track the projects
l Complete the projects and start counting the money
This deployment plan leads to several problems; let's look at some of them.
Capacity
BBs and MBBs are dedicated full-time to implementing six sigma and leading projects. GBs and Champions are expected to dedicate a certain amount of their existing work time for their projects. This is the first problem with the deployment of six sigma: GBs and Champions are expected to take time to work on six sigma but there is no subsequent increase in overall resources. The thinking is: "they can take 10% of their time and work on six sigma projects" but that translates into an additional half-day of work per week (or more). For someone who is already working in a downsized department this 10% more work can be a deal breaker. Something has to give and it's usually the six sigma project, especially if their manager is interested in something else.
Knowledge Gaps
And that's the second problem with the deployment: the Champions do not have the same level of knowledge about six sigma as their GBs (fours hours of training vs. four weeks of training). In the worst case, the manager is unaware of the importance of this activity (due to poor top-down communication) and doggedly assigns the GB to work on other things, like their "real" job. Who can effectively mentor GBs?
Unclear Direction
The BBs/MBBs can mentor GBs but their main work is leading multiple six sigma projects per year (usually in parallel). They are measured by the number of projects completed and the amount of cost savings that they "produce", not the number of GB hands that they hold. This means that they are more focused on doing their main job and less on mentoring other people.
What does all of this mean? Unlike lean manufacturing, where there may be only one dedicated person and no part-timers, almost everyone is expected to participate in six sigma. Lean likes to have "Kaizen events" where they recruit some people, do an activity and then let the people get back to work. Six sigma, on the other hand, must have a virtual army of specialists available for any and all projects all of the time. This thinking causes the biggest burden of implementation to fall on the GBs and their Champions, already adding to their workload. And when (if) the projects are completed, what are the actual results?
Results of Deployment
Most companies are able to actually complete several six sigma projects; especially if they've hired several top gun BBs/MBBs to support their deployment. They get all of the way through the DMAIC process, get approval from their Champion and close the project. What happens after that? It all falls apart. The "C" at the end of DMAIC stands for "Control". In this phase of six sigma, the improvements made during the project are documented, stabilized and handed over to the owners of the process. Out of all of the phases of six sigma, I think that this one is the weakest (followed closely by the Define phase). I think that it's the weakest because from my own experience, and the experience of other BBs, I know that many projects soon fail after being handed over to the process owners. This may be for several reasons but most of the time the owners don't really understand what the GB/BB did to their process and revert to old methods. This leads to the interesting phenomenon of multiple projects for the same problem. I don't know how many times I've heard "oh, we had a six sigma project on that last year" when discussing some significant manufacturing problem. What is so wrong with a philosophy/method/system that can allow so much effort to simply evaporate within a short time period? Obviously, measuring immediate cost savings or other metrics and then walking away is not the answer.
Recommendations and Conclusion
So what can management do to really make lasting improvement in their company? I have to admit that there are many valuable tools embedded in lean six sigma and the manager who wishes to ignore them in their entirety places his/her company at an extreme competitive disadvantage. It's not the tools themselves that are the problem; it's the mindset that tries to implement them. I think that companies that are truly successful with lean six sigma are simply successful companies in general. Their management had the correct mindset for improvement, lean six sigma just happened to be the vehicle that they used to implement their thinking. And that's the key: the mindset of the management. Is the direction to cut costs or, even worse, pretend to cut costs by playing with numbers? Or is the direction to be competitive in a global marketplace? And how do these lean six sigma tools help with that direction?
I believe that the core lean tools (pull, kanban, jidoka, poka-yoke, SMED, TPM, etc.) should be taught to all of the manufacturing engineers and manufacturing supervisors. The manufacturing engineers are responsible for planning and installing the manufacturing process. Their understanding of lean tools is crucial so that they can set up a production line using the best methods available, from the beginning. Why set up a line, run for a few years and then decide to do a kaizen event to streamline it? Just set it up that way in the first place. The supervisors face the daily challenges of pulling everything together, they have to manage and use the tools given to them from the engineers to create value for the company. Their understanding of lean tools, equal to the engineers, will guarantee that they will properly supervise the manufacturing operation. As for the existing lean group, make them a manufacturing engineer, manufacturing supervisor or manufacturing manager. Take the knowledge that they have and allow them to implement it every day, instead of when there is a kaizen event.
Six sigma also offers a lot of valuable tools that can aid in manufacturing. Like lean, the tools should be trained to a more general audience such as the quality engineers and manufacturing engineers. Don't bother with Define and Control; just teach the core tools in Measure, Analyze and Improve. Make a "six sigma project" out of one of your new product development activities. Just like lean, use the tools to analyze and improve the manufacturing process before it even exists. You have plenty of time and resources, that's what APQP is all about. And as for your existing BBs and MBBs: quality engineers and manufacturing engineers. Their deep knowledge of statistics and analysis will be invaluable in those roles.
In conclusion, you need to embed the core improvement tools of lean six sigma into your company; don't separate them into a special group with colorful job titles and ambiguous responsibilities. Dispense with internal marketing and exhortations for change. Change yourself and lead others by example. And let your competitors chase the end of the lean six sigma rainbow.
Thursday, July 21, 2011
Lean Six Sigma revisited, part 1
Sunday, July 17, 2011
Quality, Strategy, Execution
So how do we develop a quality culture at a company, in an overall fashion? Quality is about strategy and execution, just like every other important aspect of an organization. That's right, quality must be a strategy, a way to differentiate an organization from its competitors (speaking about for-profit organizations). That's the first step. If quality is not a strategy, discussed at the top of the company, then further discussions are almost pointless. It is a main strategy, but not the only strategy, various market-related and technology-related strategies are just as important (quality isn't everything in any organization). However, for quality, if you lose it, one of your competitors will pass you and they will beat you. Cost-cutting is not a way to grow a company, it is not a way to compete. Focusing on the "bottom line" is pointless if you do not focus on your "top line". Quality grows the top line through customer satisfaction. Quality also helps with the bottom line, but that is secondary to its main purpose of satisfying the customer. So, quality must be a STRATEGY.
The second question is that even if we have defined quality as a strategy, how do we implement it? The other key activity of business, EXECUTION, is just as important as strategy. Top management must communicate the strategy (all of it) to all layers of the company all of the time. The people at lower levels of the organization are responsible to implement it. But if they don't know what it is or how it relates to their job, how can they do that? Especially the "lowest" people in the company as they are often (surprisingly) the main interface to the customer. Think about it. If you work in a manufacturing company the people actually making the parts are probably at the "lowest" level of the organization but their activities directly impact your customer, every minute of every day. How important is it that those people fully understand and can implement the strategy of the company? It's the MOST IMPORTANT thing. The function of management, starting with the first-level supervisor up to the CEO, is to support THEM. Communicate the strategy and give them the tools to implement it, all the way down the org chart. That is the key to EXECUTION. Without that, you can start down a slippery slope and not even realize it, especially if you only focus on costs.
To close, quality must be a key strategy for an organization, one of the best examples is shown in a motto from Newport News shipyards: "We shall build good ships here. At a profit - if we can. At a loss - if we must. But always good ships." This is a clear statement of quality as a strategy. However, strategy is not enough, execution must be done with the proper mindset from management. Together, this overall culture of quality can lead to higher customer satisfaction and business success.
Wednesday, June 15, 2011
Head of Quality and...?
While the questions and answers were interesting in themselves I was more curious about Mr. Fowler's role at Ford, and similar roles at other companies. I noted above that Mr. Fowler was the Group VP of Quality and blah blah blah. Why, oh why, do so many companies feel that if they have a high-level person in Quality (and many don't even have an executive or higher level position with "Quality" in the title at all) that they have to make them in charge of Quality and something else? Isn't Quality enough of a job to have an executive level position responsible for it and only it? In my experience the highest "Quality only" role that I've seen is some kind of regional role. Anything higher (Director, Executive Director, Senior Executive Director, VP, Group VP, etc.) is always Quality AND New Product Launch or Quality AND Program Management or Quality AND Health, Safety, and Environment (!!!). WHY? Why is Quality always delegated to share a seat with some other function in a company? How can Quality remain relevant in this way?
I propose that companies that are serious about Quality create a C-level position dedicated to Quality in their organization. A Chief Quality Officer, responsible only for Quality, would be a strong message in any industry but in particular in the automotive industry. Toyota comes close (of course) with their regional Chief Quality Officers but I would like to see someone sitting at a table of a major, global company (preferably automotive) who has the title and responsibility and authority of Chief Quality Officer for the company. Until that happens, how can Quality ever rise above the status of "Head of Quality and....."?
Sunday, June 5, 2011
Why I Let My ASQ Certs Expire
Credentialism
In their book The Puritan Gift the brothers Hopper trace the history of American managerial culture from the Puritans up to the mid-2000's. They also chart its decline since the early 70's due to the "Cult of the (So-called) Expert" and the resulting devastation in society. Their perspective is masterfully explained in a cartoon on the subject of "Domain Knowledge", one of the main subjects of the book (WATCH IT).
One of the damning aspects of the Cult as defined in their book is the concept of "Credentialism." This idea is based on someone's qualifications for a position being based partly, or solely, on their possession of specific credentials. These credentials, whether they be an MBA, a PhD or a CSSBB mask a potential lack of actual knowledge of the industry/company (Domain Knowledge) and lead to a false belief that a person is qualified for a certain position based on specious knowledge. When the position in question is an executive position in a company, or as a consultant advising executives, the results are devastating for a company. Multiply that by hundreds of companies, many of them very large, simmer for three decades and the results are the Great Recession and subsequent slow growth/possible double-dip of the following years. I believe that these ASQ certifications promote this idea of credentialism.
Applicability
Besides the above objection, based on principle, I believe that there is a real problem with the certification process itself. I took the CSSBB exam in 2005 but in the following six years I have not retained much of what I knew at that time. My job changed from full-time Black Belt to Quality Manager and then Quality Director. I still remember enough statistical knowledge to evaluate the work of others but I could not sit down and, using pen and paper, complete a correlation study as required in the exam. So, obviously my level of knowledge has diminished over the years. However, like in 2008, due to my recertification units (RUs) I could easily re-apply and be re-certified as a SSBB this year. I would then start another three year cycle where I would have to remain employed full-time, take some classes and do some ASQ activities and I could accumulate enough RUs to re-certify again. This cycle can continue ad infinitum as long as I remain a dues-paying member and pay the re-certification fee each year.
In this sense my CSSBB is literally misleading if shown on my resume and public profile. I could not sit down today and pass that exam, even if my life depended on it. So why should I be allowed to have the appearance of having knowledge that I don't actually have? Because I work full-time, take some classes and pay my dues? This "applicability" issue is a part of the overall issue directly related to ASQ's certifications. Of course, ASQ is not alone, I believe that many professional societies that offer certifications follow the same path but I do applaud ASQ for at least requiring an examination for their certifications. This gives more weight to their program than the ones in other societies. This strength is also the solution to this issue: do away with RUs and require people to sit for the exam again to be re-certified. How else to prove that they still possess the knowledge that they had to get the certification in the first place? How else to be honest and have an ASQ certification carry real weight in the marketplace?
Because of these two topics, I will allow my certifications to expire this year and I will not sit for another certification in the future. For the first reason, this is a very big problem and the Hopper brothers offer some solutions in their book. For the second reason, ASQ can and should take my advice and do away with RUs and require people to sit for the exam every time. To do otherwise is to perpetuate a false picture of competence and knowledge in the business world.
Tuesday, May 24, 2011
Innovation and Company Culture
Rather than take a broad swipe at the topics in the study, I would like to focus my attention on the topic that I think is the most critical for the future of the world economy: innovation. My favorite definition of innovation being the practical application of invention, which is itself the result of creativity. It is in the realm of creativity that the engineer and the poet, the researcher and the composer, the manager and the sculptor exist in the same space and breathe the same air. What causes this spark of creativity which leads down the path to invention and innovation? What can organizations do to cultivate this spark?
I think that a company that wants to engender creativity, invention and innovation must be a company that has a stable and predictable company culture. Note that I did not say "good" company culture. A good company culture is truly in the eye of the beholder. There are as many company cultures as there are people and just like the personality of every person is different, the culture of every company is different. The key issue is the stability and predictability of the culture. Just like no one wants to be married to someone who is happy one minute, sad the next, responsible the next and then irresponsible nobody wants to work for a company that cannot maintain a consistent culture. Acquisitions (usually without the requisite planning and integration periods), frequent senior management changes ("frequent" meaning less than two years) and conflicting internal structures (multiple reporting lines, different departments with different mandates) lead to a culture of uncertainty and insecurity. People who are in such a culture are more concerned with their basic career survival rather than being creative. Just like Maslow's hierarchy of needs they are not at all concerned with the higher levels of actualization in the company.
Innovation is a fact of life for business going forward. Companies that do not recognize this are doomed to failure as a lack of innovation is the quickest way to lose market share. Cost-cutting does not win customers, innovation does. Companies that are serious about innovation will do whatever they can to create and sustain a predictable company culture. "Good" company cultures abound in the business world and the majority of them would be considered "stable". As Quality professionals we can lead the discussion of what constitutes a stable company culture in our own companies. We cannot afford to do otherwise.