Showing posts with label problem solving. Show all posts
Showing posts with label problem solving. Show all posts

28 August 2012

Does nothing wrong mean anything right?

A couple of interesting papers recently crossed my desktop that I'd like you to reflect upon.

The first was a 1994 paper by Dr. Juran (one of America's top quality gurus) titled "Quality Problems, Remedies and Nostrums" that focused on the Zero Defect (ZD) movement. In this paper, he states that "the results of the ZD movement are not very impressive" first, because failures greatly exceed successes and second, published results appeared more qualitative than quantitative as if their main purpose was to impress their customers.

The second document is an ISO related discussion on the difference between "corrective action" and "preventive action" to eliminate the causes of non-conformance. The paper explains that corrective action is about stability, and preventive action is about capability. For QFD practitioners, this explanation also demonstrates the difference between a problem solving approach using DMAIC, and a design approach using DMADV to understand true customer needs and assure satisfaction.

Neither paper answers this critical QFD question, however: "Does nothing wrong mean anything is right?" 

image - "nothing wrong" may not be "anything right"
We ask this question at the start of every QFD Green Belt® course in order to provoke students to go beyond fixing and preventing negative quality, and to search for positive quality.

In other words, customers don't buy a product or service because the product is problem-free; they buy a product because it helps them, the customer, become problem-free. This means you must understand what outcomes the customer truly wants in their life and work.

 
Unfortunately customers are not always good at explaining themselves. After all, few suppliers ever bother to ask, so customers are not practiced at describing their problems or unfulfilled opportunities.

This is why VOC tools such as the gemba visits, Customer Process model, and Customer Voice table are essential to good QFD. These tools help customers use words and actions to show us what "success" means to them and why they are failing. Through these tools, customers can explain their biggest headaches and missed opportunities. 

With this knowledge, a QFD team can then identify solutions that are capable of delighting the customer better than the competitors. This is how QFD differs from other quality initiatives.

If you find this topic helpful, you might be also interested in reading "Finding Customer Delights Using QFD" in the 2006 Symposium Transactions. Better yet, plan to join us this fall in the 24th Symposium on QFD in St. Augustine, Florida, to learn more about these modern tools.

    22 August 2012

    Romney PDCA

    Mr. Newt Gingrich, in his 2006 book "Saving Lives and Saving Money", expounded on his decade-long fascination with Total Quality Management (TQM), six sigma, and lean thinking. Perhaps he could share his library with U.S. Republican Party presidential candidate Mr. Mitt Romney.

    According to Romney advisor Beth Meyers who worked also on his 2003 Massachusetts governor transition team, Mr. Romney has his own brand of "problem solving" that might interest others in the quality field.

    In an August 16, 2012 article in the New York Times, "Campaigning Aside, Team Plans a Romney Presidency" by Ashley Parker, Ms. Meyers is quoted:
    “With Mitt, his approach to problem solving is first to identify the problem, make sure you’re solving for the problem actually there; second, look at best practices; third, apply best practices to the problem at hand; and fourth, execute on it.”

    While Mr. Romney's four steps resemble Dr. Shewhart's and later Dr. W. E. Deming's "Plan-Do-Check-Act" approach to problem solving, it deserves some examination -- especially if he wins the election and employs this technique in government.

    Let's compare the two approaches.


    image - QFD is a PDCA approach
    QFD is a PDCA approach.
    SHEWHART / DEMING
    • PLAN. Define the problem. This means to identify an undesirable state (problem) or a desired state (opportunity). How important is this problem relative to other problems. This requires deep analysis including:
    1. Prioritization of problems and opportunities so that people, time, and money can be focused where they will do the most good. And by what criteria will "good" be defined? Is the problem due to common causes of variation or special causes?
    2. Set a measurable target or outcome (how much must the problem be mitigated to be acceptable or how much opportunity must be realized).
    3. What is the current state of the problem or opportunity.
    4. What is preventing the current state from achieving the target. That is, what is the root cause(s) of the problem or missed opportunity. If there are many root causes, which has the greatest impact or correlation.
    5. In order to address the root causes with the greatest impact, define what a good solution must do or be, independent of a solution.
    6. Use creativity and innovation to propose solutions that will do or be what is defined in 5.
    7. Define a way to test the solutions for efficacy.
    8. Select the best solutions relative to efficacy, time, cost, and other considerations.
    • DO. Test the best solutions to see how well they work in real application. Measure both the inputs of the solution as well as the outputs of the solution to determine if the results achieve statistical stability and not just luck.
    • CHECK (also referred to as Study). Check the results of the solutions against the targets set in the Plan phase. Are they acceptable and sustainable? If not, search for new solutions or as a last resort, lower the targets (and be able to justify why, and when they will be raised again).
    • ACT. Roll out the solution and standardize the improvements by issuing/training new operating procedures in order to prevent recurrence. Measure inputs periodically to assure that the procedures and systems are being followed. Measure outputs periodically to assure the improved process remains stable and predictable. Determine when the process will be reviewed for further improvement, or begin work on the next priority problem.
      There are many variations on the above, including DMAIC, but this will work for our discussion.

    ROMNEY
    • "Identify identify the problem, make sure you’re solving for the problem actually there." This sounds like good advice to make sure the problem is actually real. But, where is the analysis of the cause of the problem, the current state, the desired state?
    • "Look at best practices." It is interesting that Deming did not care for benchmarking best practices, ridiculing the process as “the last stage of civilization.” His argument was that if your company is the same as others, why would your customers buy from you and not the others. Unique conditions require unique solutions. Where in this approach is creativity and innovation? (See our previous post "Benchmarking – the fatal flaw in modern quality thinking")
    • "Apply best practices to the problem at hand." Where is the testing to see if the solutions are delivering the desired results? Where is the refinement?
    • "Execute on it." This sounds like a repeat of "Apply best practices" so it is not clear if this adds anything to the process. Where is follow up to see if the solution continues to work?


    Remember, that QFD is also a PDCA approach. Plan includes all the modern Blitz QFD® tools up to and including parts of the Maximum Value table.

    House of Quality matrix actually starts at the end of the Plan stage -- which is why it should be preceded with Blitz QFD® anyway. Do is the design, development and prototyping. Check is the testing, and market validation phase. Act is the roll out, commercialization, product maintenance, and product retirement phase.