May 11 2017
Not statistically significant does NOT mean insignificant | Rebecca A. Morgan | AME Target
“My fully-loaded 2012 Audi A6 had an intermittent frustrating problem since the day I bought it. No diagnostic codes indicated a problem. Escalation to German engineering had me ready to move back to Lexus. Their response was ‘it must not really be happening. Our codes would indicate if it were.’ That obnoxious response was based on the assumption they had thought of every cause of failure in developing the diagnostic codes. FMEA is not 100% and never will be. Do you have customer data that you’re not actively using to improve your product Four years after I first reported the issue, Audi issued an urgent safety recall for the problem that I had been experiencing. Why the delay?”
Sourced through AME Target
Michel Baudin‘s comments: I am sure many have had similar experiences to Becky’s with customer service in many companies. They tell you their product is used by millions and it’s the first time anyone reports this problem. You are probably using it wrong, or misreading its output,… This being said, it’s not really related to the concept of statistical significance.
May 21 2017
Driving Improvement Through Systems Thinking | Gregg Stocker
“[…] When starting an improvement effort, I usually ask about the minimum target the team is attempting to achieve. The answer is often something made up on the spot or a generalization, like as much as possible. Improvement efforts should generally be driven by the actual requirements of the business. For example, if a company determines that the time between a customer placing an order and receiving the product is too long, it should determine an improvement target based on what the business needs. If it currently takes 42 days and customers expect to receive the product in 22 days because of their needs or what competitors are offering, the minimum improvement needed is 20 days.[…]”
Sourced through Lessons in Lean
Michel Baudin‘s comments:
Gregg Stocker illustrates abstract principles with concrete examples, which makes his meaning clear and unambiguous. The above excerpt is meant to show the need for employees and managers to understand the consequences of local actions on the organization as a whole. As he points out in the rest of his post, it’s not always easy.
Share this:
Like this:
By Michel Baudin • Blog clippings 1 • Tags: Continuous improvement, Cost-of-Quality, Improvement, Kaizen, Takt